search for: intptr

...L", /*CallingConvention = CallingConvention.Cdecl,*/ CharSet = CharSet.Ansi)] static extern void R_ReplDLLinit(); //- R SEXP management [DllImport("R.DLL", /*CallingConvention = CallingConvention.Cdecl,*/ CharSet = CharSet.Ansi)] static extern IntPtr Rf_mkString(string toConvert); [DllImport("R.DLL", /*CallingConvention = CallingConvention.Cdecl,*/ CharSet = CharSet.Ansi)] static extern IntPtr Rf_protect(IntPtr ptr); [DllImport("R.DLL", /*CallingConvention = CallingConvention.Cdecl,*/ CharSet = CharSe...

...L", /*CallingConvention = CallingConvention.Cdecl,*/ CharSet = CharSet.Ansi)] static extern void R_ReplDLLinit(); //- R SEXP management [DllImport("R.DLL", /*CallingConvention = CallingConvention.Cdecl,*/ CharSet = CharSet.Ansi)] static extern IntPtr Rf_mkString(string toConvert); [DllImport("R.DLL", /*CallingConvention = CallingConvention.Cdecl,*/ CharSet = CharSet.Ansi)] static extern IntPtr Rf_protect(IntPtr ptr); [DllImport("R.DLL", /*CallingConvention = CallingConvention.Cdecl,*/ CharSet = CharSe...

On Nov 12, 2009, at 7:35 PM, Talin wrote: > On Thu, Nov 12, 2009 at 5:58 PM, Chris Lattner <clattner at apple.com> > wrote: > > There is also the issue of how constants should be represented. > > For all current processors that I know of, an intptr will be either > 32 or 64 bits. However, there may be some future processor which > supports 128-bit pointers (although a system containing that much > RAM or even virtual address space is hard to imagine.) 8, 16, and 24-bit address spaces are also popular. > If we assume that i...

...tem.Runtime.InteropServices; using System.Security.Principal; namespace PingCastle.ADWS { internal class SambaSidResolver : IDisposable { const int SECURITY_MAX_SID_SIZE = 68; [DllImport("libsmbclient.so.0", CharSet = CharSet.Ansi)] static internal extern IntPtr _talloc_stackframe(string context); [DllImport("libsmbclient.so.0", CharSet = CharSet.Ansi)] internal static extern IntPtr user_auth_info_init(IntPtr mem_ctx); [DllImport("libsmbclient.so.0", CharSet = CharSet.Ansi)] internal static extern void...

Could people please test -current? We will be making a release fairly soon. -d -- | By convention there is color, \\ Damien Miller <djm at mindrot.org> | By convention sweetness, By convention bitterness, \\ www.mindrot.org | But in reality there are atoms and space - Democritus (c. 400 BCE)

...ote: >> On Thu, Nov 12, 2009 at 5:58 PM, Chris Lattner <clattner at apple.com >> <mailto:clattner at apple.com>> wrote: >> >> >> There is also the issue of how constants should be represented. >> >> For all current processors that I know of, an intptr will be either >> 32 or 64 bits. However, there may be some future processor which >> supports 128-bit pointers (although a system containing that much RAM >> or even virtual address space is hard to imagine.) > > 8, 16, and 24-bit address spaces are also popular. To be...

On Nov 12, 2009, at 11:29 AM, Talin wrote: > > Well, as far as intp goes (or iptr if you prefer - the naming > convention in LLVM is i<size>) How about "intptr". > here's what I would expect: > General rule #1: If an instruction accepts both i32 and i64, then it > should accept iptr as well. If it only accepts i32, then it can > continue to only accept i32. > General rule #2: It should support operations that are commonly used...

On Thu, Nov 12, 2009 at 5:58 PM, Chris Lattner <clattner at apple.com> wrote: > On Nov 12, 2009, at 11:29 AM, Talin wrote: > > > Well, as far as intp goes (or iptr if you prefer - the naming convention in > LLVM is i<size>) > > > How about "intptr". > > here's what I would expect: > > - General rule #1: If an instruction accepts both i32 and i64, then it > should accept iptr as well. If it only accepts i32, then it can continue to > only accept i32. > - General rule #2: It should support operations t...

...ze As Integer = 3 Public Const Speex_Set_Quality As Integer = 4 Public Const Speex_nb_Mode As Integer = 3 'create the structure that will hold the speexbits <StructLayout(LayoutKind.Sequential)> _ Public Structure SpeexBits Public chars As IntPtr ' "raw" data Public nbBits As Integer ' Total number of bits stored in thestream Public charPtr As Integer ' Position of the byte "cursor" Public bitPtr As Integer ' Position of the b...

Hello, I came across an interoperability problem in OpenSSH 3.0p1 and 3.0.1p1 concerning the AFS token forwarding. That means that the new versions are not able to exchange AFS tokens (and Kerberos TGTs) with older OpenSSH releases (including 2.9p2) and with the old SSH 1.2.2x. In my opinion this problem already existed in Openssh 2.9.9p1, but I have never used this version (I only looked at the

..."word" type along these >> lines. Would it be worth considering adding such a type to the IR, >> or is there a reason not to do so that I am failing to see? > > What would this be used for? How is it defined? How does > arithmetic work on it? Looking up the intptr type via TargetData is not a significant issue for me, but I can see the appeal, and how its absence could constitute a significant barrier to generating portable IR (provided, of course, a portable language). Regardless, it would allow me to hardcode a good deal more codegen if the LLVM IR...

...nnect" that can be used easily from libsmbclient >> >> > >> >> > Thinking about Smb_negox for example. I cannot just call >> structure->member >> >> > because I'll to translate all structure. >> >> > Working with pointer (IntPtr in c#) is much simpler. >> >> >> >> You can write a very simple C wrapper and call the wrapper from C#. >> >> >> >> So you would have: >> >> >> >> rpcwrapper.c: >> >> void* init_connection(const char *user, cons...

On Wed, 7 May 2008, Gordon Henriksen wrote: >> What would this be used for? How is it defined? How does >> arithmetic work on it? > > Looking up the intptr type via TargetData is not a significant issue > for me, but I can see the appeal, and how its absence could constitute > a significant barrier to generating portable IR (provided, of course, > a portable language). Regardless, it would allow me to hardcode a good > deal more codegen if...

On 2008-05-07, at 16:24, Chris Lattner wrote: > On Wed, 7 May 2008, Gordon Henriksen wrote: > >>> What would this be used for? How is it defined? How does >>> arithmetic work on it? >> >> Looking up the intptr type via TargetData is not a significant >> issue for me, but I can see the appeal, and how its absence could >> constitute a significant barrier to generating portable IR >> (provided, of course, a portable language). Regardless, it would >> allow me to hardcode a g...

...if we try to read past thevalid data */ public int buf_size; /* Allocated size for buffer */ public int reserved1; /* Reserved for future use */ public void *reserved2; /* Reserved for future use */ } [StructLayout(LayoutKind.Sequential)] public struct SpeexMode { public void *mode; public IntPtr query; public char *modename; public int modeid; public int bitstream_version; public IntPtr enc_init; public IntPtr enc_destroy; public IntPtr enc; public IntPtr dec_init; public IntPtr dec_destroy; public IntPtr dec; public IntPtr enc_ctl; public IntPtr dec_ctl; } #endregion #region...

...ed Align) { const Type *SBP = PointerType::get(Type::SByteTy); static Function *MemCpy = 0; - if (!MemCpy) - MemCpy = TheModule->getOrInsertFunction("llvm.memcpy", Type::VoidTy, SBP, - SBP, Type::UIntTy, Type::UIntTy, + const Type *IntPtr = TD.getIntPtrType(); + if (!MemCpy) { + const char *Name = IntPtr == Type::UIntTy ? + "llvm.memcpy.i32" : "llvm.memcpy.i64"; + MemCpy = TheModule->getOrInsertFunction(Name, Type::VoidTy, SBP, + SBP, Int...

Hello, we've run a coverity scan on the openssh sources and it found several issues. Although the scan was run on patched rhel sources, some results are applicable to vanilla sources too. * servconf.c:1458:dead_error_line ? Execution cannot reach this statement "*intptr = *intptr + 1;" --- a/servconf.c +++ b/servconf.c @@ -1451,12 +1451,8 @@ process_server_config_line(ServerOptions *options, char *line, if (!arg || *arg == '\0') fatal("%s line %d: missing file name.", filen...

...ot; /* @@ -237,7 +238,7 @@ return 0; /* Get the keyword. (Each line is supposed to begin with a keyword). */ - cp = strtok(cp, WHITESPACE); + cp = strtok(cp, WHITESPACE_EQ); opcode = parse_token(cp, filename, linenum); switch (opcode) { @@ -248,7 +249,7 @@ case oForwardAgent: intptr = &options->forward_agent; parse_flag: - cp = strtok(NULL, WHITESPACE); + cp = strtok(NULL, WHITESPACE_EQ); if (!cp) fatal("%.200s line %d: Missing yes/no argument.", filename, linenum); value = 0; /* To avoid compiler warning... */ @@ -330,7 +331,7 @@ case oStrict...

This patch series consists of minor fixes and cleanups I made during update to openssh V_4_6 branch. openssh/auth-pam.c | 9 ++++----- openssh/auth2.c | 2 -- openssh/readconf.c | 7 ++++--- openssh/servconf.c | 14 ++++++++------ openssh/sftp-server.c | 9 ++++++--- openssh/sshd.c | 2 +- 6 files changed, 23 insertions(+), 20 deletions(-) -- ldv

....rhosts_rsa_authentication) auth_mask |= 1 << SSH_AUTH_RHOSTS_RSA; if (options.rsa_authentication) auth_mask |= 1 << SSH_AUTH_RSA; Now, in servconf.c, options.rhosts_authentication is set to 0 if IgnoreRhosts is no: case sIgnoreRhosts: intptr = &options->ignore_rhosts; parse_flag: cp = strtok(NULL, WHITESPACE); fprintf(stderr, "sIgnoreRhosts triggered as %s\n", cp); if (!cp) { fprintf(stderr, "%s line %d: missing yes/no argument.\n", filename, linenum); exit(1);...