search for: 0x7fffffff

http://bugzilla.netfilter.org/show_bug.cgi?id=577 Summary: cannot set spi/reqid numbers higher than 0x7fffffff (policy match) Product: iptables Version: unspecified Platform: i386 OS/Version: All Status: NEW Severity: normal Priority: P1 Component: iptables AssignedTo: laforge at netfilter.org...

On 5/3/07, Erik de Castro Lopo <mle+la@mega-nerd.com> wrote: > Peter Grayson wrote: > > Personally I think universal binaries are a bad idea. They have obviously served some purpose, but I tend to agree that the concept does not seem to scale well once outside the Apple microcosm. > For one of my projects, libsndfile, endian issues is not the only > think that breaks in

...32 when the source float is outside the range of values that can be represented by the int32. For instance: float int32_ppc in32_x86 2147483649.0 2147483647 -2147483648 2147483648.0 2147483647 -2147483648 2147483647.0 2147483647 2147483647 (0x7fffffff) .... -2147483648.0 -2147483648 -2147483648 -2147483649.0 -2147483648 -2147483648 (0x80000000) -2147483650.0 -2147483648 -2147483648 As you can see out of range floats are correctly clipped on PPC, but only correctly clipped for negative floats on x86. libsndfi...

...range > of values that can be represented by the int32. > > For instance: > > float int32_ppc in32_x86 > 2147483649.0 2147483647 -2147483648 > 2147483648.0 2147483647 -2147483648 > 2147483647.0 2147483647 2147483647 (0x7fffffff) > .... > -2147483648.0 -2147483648 -2147483648 > -2147483649.0 -2147483648 -2147483648 (0x80000000) > -2147483650.0 -2147483648 -2147483648 > > As you can see out of range floats are correctly clipped on PPC, > but only correctly clipped fo...

I was flipping through the code recently and noticed that we still have the double whammy of allocating dir entry positions with parent_dir->counter++ and that weird setting of f_pos to 2^31-1. So after enough creates (and deletes :)) in a directory we end up with an entry item whose key is past that value. f_pos gets rewound instead of being set to that magical EOF. readdir() gets stuck

...ct.c: CIFS VFS: in cifs_mount as Xid: 30 with uid: 0 [528109.522292] fs/cifs/connect.c: Username: tech [528109.522295] fs/cifs/connect.c: UNC: \\172.16.0.8\tech ip: 172.16.0.8 [528109.522306] fs/cifs/connect.c: Socket created [528109.523047] fs/cifs/connect.c: sndbuf 16384 rcvbuf 87380 rcvtimeo 0x7fffffff [528109.523054] fs/cifs/transport.c: Sending smb of length 68 [528109.528073] fs/cifs/connect.c: Existing smb sess not found [528109.528086] fs/cifs/cifssmb.c: secFlags 0x7 [528109.528091] fs/cifs/transport.c: For smb_command 114 [528109.528094] fs/cifs/transport.c: Sending smb of length 78 [5...

...ustatus_addr, ustatus; + for (i = 0; i < 16; i++) { + if (!(units & (1 << i))) + continue; + if (dev_priv->chipset < 0xa0) + ustatus_addr = ustatus_old + (i << 12); + else + ustatus_addr = ustatus_new + (i << 11); + ustatus = nv_rd32(dev, ustatus_addr) & 0x7fffffff; + if (!ustatus) + continue; + tps++; + switch (type) { + case 6: /* texture error... unknown for now */ + nv50_pfb_vm_trap(dev, display, name); + if (display) { + NV_ERROR(dev, "magic set %d:\n", i); + for (r = ustatus_addr + 4; r <= ustatus_addr + 0x10; r += 4) +...

This will fix races between generated ctxprogs and interrupt handler. Signed-off-by: Marcin Ko?cielnicki <koriakin at 0x04.net> --- drivers/gpu/drm/nouveau/nv50_grctx.c | 5 +++++ 1 files changed, 5 insertions(+), 0 deletions(-) diff --git a/drivers/gpu/drm/nouveau/nv50_grctx.c b/drivers/gpu/drm/nouveau/nv50_grctx.c index d105fcd..9f909ab 100644 ---

Hi All, The PRE or GVNPRE is not effective for the below use case. int sum; int phi =30; void f (int i, int *a) { if ((a[i] << (1)) > -15) sum =(phi+ 0x7fffffffL )/ a[i]; if ((a[i] << (2)) > -15) sum =(phi + 0x7fffffffL) /a[i]; } respective asm (clang on trunk ) #clang -O3 -S test.c BB#0: # %entry pushl %edi pushl %esi movl 12(%esp), %esi movl 16(%esp), %edi mo...

There is a distinction between logical/arithmetic shift right, but why not for shift left? I'm also a bit confused by one example in the reference manual: <result> = lshr i8 -2, 1 ; yields {i8}:result = 0x7FFFFFFF Is this an error in the manual? The result is supposed to be an i8 yet a i32 is shown. -- edA-qa mort-ora-y -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- Sign: Please digitally sign your emails. Encrypt: I'm also happy to receive encrypted mail. -------------- next...

I''m using Xen 4.3, installed from source on Ubuntu 13.04. I''ve successfully installed a Windows 8 guest, and had Xen pass it an AMD FirePro W7000 GPU (technically 2 PCI devices - the second is for the sound), as well as the virtualised graphics adapter. Windows finds the card fine, and I''ve installed AMD''s drivers. Device Manager says that the card cannot

...;, "-0xf", OK, -15); + PARSE (int, "%d", "-010", OK, -8); + PARSE (int, "%d", "2147483647", OK, 2147483647); /* INT_MAX */ + PARSE (int, "%d", "-2147483648", OK, -2147483648); /* INT_MIN */ + PARSE (int, "%d", "0x7fffffff", OK, 0x7fffffff); + PARSE (int, "%d", "-0x80000000", OK, -0x80000000); + + /* Test basic error handling. */ + PARSE (int, "%d", "", BAD, 0); + PARSE (int, "%d", "-", BAD, 0); + PARSE (int, "%d", "+&qu...

...+ PARSE (int, "%d", "-010", OK, -8); > > + PARSE (int, "%d", "2147483647", OK, 2147483647); /* INT_MAX */ > > + PARSE (int, "%d", "-2147483648", OK, -2147483648); /* INT_MIN */ > > + PARSE (int, "%d", "0x7fffffff", OK, 0x7fffffff); > > + PARSE (int, "%d", "-0x80000000", OK, -0x80000000); > > Matches our earlier assumptions of twos-complement targets. > > > + > > + /* Test basic error handling. */ > > + PARSE (int, "%d", "",...

David/All, Just a quick question about NSW/NUW bits, if you've got a second. I noticed you've been doing a little work on this as of late. I have a bit of code that looks like the following: %indvars.iv.next = add nuw nsw i64 %indvars.iv, 1 %2 = add i64 %indvars.iv.next, -1 %tmp = trunc i64 %2 to i32 %cmp = icmp slt i32 %tmp, %0 br i1 %cmp, label %for.body, label

...preform the seek. Patch is against git commit 718a73d31011a7985365f4473e735b96791c7156. Thanks, Sean --- diff --git a/configure.ac b/configure.ac index 6a2bb05..92075a3 100644 --- a/configure.ac +++ b/configure.ac @@ -314,7 +314,7 @@ if test $SIZEOF_OGGZ_OFF_T = 4 ; then OGGZ_OFF_MAX="0x7FFFFFFF" PRI_OGGZ_OFF_T="l" elif test $SIZEOF_OGGZ_OFF_T = 8 ; then - PRI_OGGZ_OFF_T=PRId64 + PRI_OGGZ_OFF_T="ll" fi dnl The following configured variables are written into the public header diff --git a/src/liboggz/oggz_seek.c b/src/liboggz/oggz_seek.c index c46f0a...

...>>> I'm attaching the compiled code that I've been getting, both with >>> CodeGenOpt::Default and CodeGenOpt::None . The crash isn't occurring with >>> CodeGenOpt::None, but that seems to be because ECX isn't being used - it >>> still gets set to 0x7fffffff by one of the calls to 76719BA1 >>> >>> I notice that X86::SQRTPD[m|r] appear in X86InstrInfo::isHighLatencyDef. >>> I was thinking an optimization might be removing it, but I don't get the >>> sqrtpd instruction even if the createJIT optimization level turne...

...be nice. > + PARSE (int, "%d", "-010", OK, -8); > + PARSE (int, "%d", "2147483647", OK, 2147483647); /* INT_MAX */ > + PARSE (int, "%d", "-2147483648", OK, -2147483648); /* INT_MIN */ > + PARSE (int, "%d", "0x7fffffff", OK, 0x7fffffff); > + PARSE (int, "%d", "-0x80000000", OK, -0x80000000); Matches our earlier assumptions of twos-complement targets. > + > + /* Test basic error handling. */ > + PARSE (int, "%d", "", BAD, 0); > + PARSE (int,...

...; I'm attaching the compiled code that I've been getting, both with >>>> CodeGenOpt::Default and CodeGenOpt::None . The crash isn't occurring with >>>> CodeGenOpt::None, but that seems to be because ECX isn't being used - it >>>> still gets set to 0x7fffffff by one of the calls to 76719BA1 >>>> >>>> I notice that X86::SQRTPD[m|r] appear in >>>> X86InstrInfo::isHighLatencyDef. I was thinking an optimization might be >>>> removing it, but I don't get the sqrtpd instruction even if the createJIT >>...

...ng the compiled code that I've been getting, both >> with CodeGenOpt::Default and CodeGenOpt::None . The crash >> isn't occurring with CodeGenOpt::None, but that seems to be >> because ECX isn't being used - it still gets set to >> 0x7fffffff by one of the calls to 76719BA1 >> >> I notice that X86::SQRTPD[m|r] appear in >> X86InstrInfo::isHighLatencyDef. I was thinking an >> optimization might be removing it, but I don't get the sqrtpd >> instruction even if the createJIT...

...taching the compiled code that I've been getting, both with >>>>> CodeGenOpt::Default and CodeGenOpt::None . The crash isn't occurring with >>>>> CodeGenOpt::None, but that seems to be because ECX isn't being used - it >>>>> still gets set to 0x7fffffff by one of the calls to 76719BA1 >>>>> >>>>> I notice that X86::SQRTPD[m|r] appear in >>>>> X86InstrInfo::isHighLatencyDef. I was thinking an optimization might be >>>>> removing it, but I don't get the sqrtpd instruction even if the cr...