Displaying 8 results from an estimated 8 matches for "2147483648ll".
2006 Sep 04
2
[LLVMdev] bug in llvm-gcc implementation of long long
> What does the preprocessed output of that function look like?
long long f4(void) {
return (long long)2147483647 + 1;
}
Using 2147483648LL directly causes the same problem.
> -Chris
Best Regards,
Rafael
2006 Sep 04
5
[LLVMdev] bug in llvm-gcc implementation of long long
Compiling the following C code
--------------------------------------------
long long f4(void) {
return (long long)INT_MAX + 1;
}
-------------------------------------------
produces
------------------------------------------
long %f4() {
entry:
ret long -2147483648
}
------------------------------------------
but in 64 bits, -2147483648 != 2147483648. As a result, the x86 output has
2006 Sep 04
0
[LLVMdev] bug in llvm-gcc implementation of long long
On Mon, 4 Sep 2006, [UTF-8] Rafael Esp?ndola wrote:
> Compiling the following C code
> ------------------------------------------
> long %f4() {
> entry:
> ret long -2147483648
> }
> ------------------------------------------
I get this:
long %f4() {
entry:
ret long 2147483648
}
What does the preprocessed output of that function look like?
-Chris
--
2006 Sep 04
0
[LLVMdev] bug in llvm-gcc implementation of long long
On Mon, 4 Sep 2006, [UTF-8] Rafael Esp?ndola wrote:
>> What does the preprocessed output of that function look like?
> long long f4(void) {
> return (long long)2147483647 + 1;
> }
>
> Using 2147483648LL directly causes the same problem.
What target triple?
-Chris
--
http://nondot.org/sabre/
http://llvm.org/
2013 Jul 24
1
QCONST16 cross compile inconsistency
...b,16)
-#define QCONST16(x,bits) ((opus_val16)(.5+(x)*(((opus_val32)1)<<(bits))))
-#define QCONST32(x,bits) ((opus_val32)(.5+(x)*(((opus_val32)1)<<(bits))))
-
#define VERIFY_SHORT(x) ((x)<=32767&&(x)>=-32768)
#define VERIFY_INT(x) ((x)<=2147483647LL&&(x)>=-2147483648LL)
#define VERIFY_UINT(x) ((x)<=(2147483647LLU<<1))
diff --git a/celt/fixed_generic.h b/celt/fixed_generic.h
index ac01a43..0b17563 100644
--- a/celt/fixed_generic.h
+++ b/celt/fixed_generic.h
@@ -48,12 +48,6 @@
/** 32x32 multiplication, followed by a 31-bit shift right. Results fits in 32...
2013 Aug 22
0
[LLVMdev] [RFC PATCH] X32 ABI support for Clang/compiler-rt (Clang patch)
...@@ -396,6 +396,7 @@
// PC-relative branch instead of loading the actual address. (This
is
// considerably shorter than the 64-bit immediate load already
there.)
// We assume here intptr_t is 64 bits.
+#if defined (__LP64__)
intptr_t diff = NewVal-RetAddr+7;
if (diff >= -2147483648LL && diff <= 2147483647LL) {
*(unsigned char*)(RetAddr-0xc) = 0xE9;
@@ -405,6 +406,11 @@
((unsigned char*)RetAddr)[0] = (2 | (4 << 3) | (3 << 6));
}
sys::ValgrindDiscardTranslations((void*)(RetAddr-0xc), 0xd);
+#else // If intptr_t is only 32 bits, alway...
2013 Aug 22
7
[LLVMdev] [RFC PATCH] X32 ABI support for Clang/compiler-rt
Hi,
I'm working on bringing up complete coverage for a Gentoo x32 "desktop"
system. I've been cooking up quite a few patches for various packages
to push upstream, but right now, the biggest blocker is the lack of
support for building with/codegen targeting x32 in llvm/clang. Since
the x32 patches were sent last year, I see support code has landed in
LLVM, and basic handling of
2013 Aug 22
3
[LLVMdev] [NEW PATCH] X32 ABI support for Clang/compiler-rt (Clang patch)
...@@ -396,6 +396,7 @@
// PC-relative branch instead of loading the actual address. (This
is
// considerably shorter than the 64-bit immediate load already
there.)
// We assume here intptr_t is 64 bits.
+#if defined (__LP64__)
intptr_t diff = NewVal-RetAddr+7;
if (diff >= -2147483648LL && diff <= 2147483647LL) {
*(unsigned char*)(RetAddr-0xc) = 0xE9;
@@ -405,6 +406,11 @@
((unsigned char*)RetAddr)[0] = (2 | (4 << 3) | (3 << 6));
}
sys::ValgrindDiscardTranslations((void*)(RetAddr-0xc), 0xd);
+#else // If intptr_t is only 32 bits, alway...