Displaying 10 results from an estimated 10 matches for "compile_time_assert".
2004 Dec 16
0
[LLVMdev] LLVM & Large memory 64-bit systems
...blem
areas really is small, but again, they should definitely be fixed.
> p.s. which mailing list would be a better place to discuss such issues ?
llvmdev is the right list for this, I've cc'd it.
-Chris
> #include <stddef.h>
> #include <stdlib.h>
>
> #define COMPILE_TIME_ASSERT(e) {typedef int __cta_fail[1-2*!(e)];}
>
> /* B is a valid size_t constant on 64-bit machines */
> #define B ((size_t)1 << 33)
>
> struct Foo {
> char big[B];
> int dummy;
> };
>
> extern struct Foo foo;
>
> char* p(size_t n)
> {
> return &foo...
2007 Aug 18
1
[LLVMdev] Minor cleanup to prior APInt patch
...ion 41148)
+++ include/llvm/ADT/APInt.h (working copy)
@@ -19,9 +19,7 @@
#include <cassert>
#include <string>
-#define HOST_CHAR_BIT 8
-#define compileTimeAssert(cond) extern int CTAssert[(cond) ? 1 : -1]
-#define integerPartWidth (HOST_CHAR_BIT * sizeof(llvm::integerPart))
+#define COMPILE_TIME_ASSERT(cond) extern int CTAssert[(cond) ? 1 : -1]
namespace llvm {
@@ -29,6 +27,9 @@
bignum. */
typedef uint64_t integerPart;
+ const unsigned int host_char_bit = 8;
+ const unsigned int integerPartWidth = host_char_bit * sizeof(integerPart);
+
//===------------------------------------...
2016 Dec 23
2
3.9 regression with legacy static assert macros (bad type resolution)
3.9.0 and current release_39 (r90413) have issues with older static assertion macros like this one from an older libunwind:
#define COMPILE_TIME_ASSERT( expr ) \
extern int compile_time_assert_failed[ ( expr ) ? 1 : -1 ] __attribute__( ( unused ) );
I notice that the issue is fixed on current trunk. Does anyone know what revision introduced the fix? Can we get it cherry-picked into release_39? I know 3.9.1 final was just tagg...
2016 Dec 27
2
3.9 regression with legacy static assert macros (bad type resolution)
...016, at 9:36 PM, Jeremy Huddleston Sequoia via llvm-dev <llvm-dev at lists.llvm.org> wrote:
>>>>
>>>> 3.9.0 and current release_39 (r90413) have issues with older static assertion macros like this one from an older libunwind:
>>>>
>>>> #define COMPILE_TIME_ASSERT( expr ) \
>>>> extern int compile_time_assert_failed[ ( expr ) ? 1 : -1 ] __attribute__( ( unused ) );
>>>>
>>>> I notice that the issue is fixed on current trunk. Does anyone know what revision introduced the fix? Can we get it cherry-picked int...
2016 Dec 27
3
3.9 regression with legacy static assert macros (bad type resolution)
...Jeremy Huddleston Sequoia via llvm-dev <llvm-dev at lists.llvm.org> wrote:
>>>>>
>>>>> 3.9.0 and current release_39 (r90413) have issues with older static assertion macros like this one from an older libunwind:
>>>>>
>>>>> #define COMPILE_TIME_ASSERT( expr ) \
>>>>> extern int compile_time_assert_failed[ ( expr ) ? 1 : -1 ] __attribute__( ( unused ) );
>>>>>
>>>>> I notice that the issue is fixed on current trunk. Does anyone know what revision introduced the fix? Can we get it cherry...
2016 Dec 23
0
3.9 regression with legacy static assert macros (bad type resolution)
> On Dec 22, 2016, at 9:36 PM, Jeremy Huddleston Sequoia via llvm-dev <llvm-dev at lists.llvm.org> wrote:
>
> 3.9.0 and current release_39 (r90413) have issues with older static assertion macros like this one from an older libunwind:
>
> #define COMPILE_TIME_ASSERT( expr ) \
> extern int compile_time_assert_failed[ ( expr ) ? 1 : -1 ] __attribute__( ( unused ) );
>
> I notice that the issue is fixed on current trunk. Does anyone know what revision introduced the fix? Can we get it cherry-picked into release_39? I know 3.9.1 final...
2016 Dec 24
2
3.9 regression with legacy static assert macros (bad type resolution)
...gt;
>
>> On Dec 22, 2016, at 9:36 PM, Jeremy Huddleston Sequoia via llvm-dev <llvm-dev at lists.llvm.org> wrote:
>>
>> 3.9.0 and current release_39 (r90413) have issues with older static assertion macros like this one from an older libunwind:
>>
>> #define COMPILE_TIME_ASSERT( expr ) \
>> extern int compile_time_assert_failed[ ( expr ) ? 1 : -1 ] __attribute__( ( unused ) );
>>
>> I notice that the issue is fixed on current trunk. Does anyone know what revision introduced the fix? Can we get it cherry-picked into release_39? I know...
2016 Dec 27
0
3.9 regression with legacy static assert macros (bad type resolution)
...gt; On Dec 22, 2016, at 9:36 PM, Jeremy Huddleston Sequoia via llvm-dev <llvm-dev at lists.llvm.org> wrote:
>>>
>>> 3.9.0 and current release_39 (r90413) have issues with older static assertion macros like this one from an older libunwind:
>>>
>>> #define COMPILE_TIME_ASSERT( expr ) \
>>> extern int compile_time_assert_failed[ ( expr ) ? 1 : -1 ] __attribute__( ( unused ) );
>>>
>>> I notice that the issue is fixed on current trunk. Does anyone know what revision introduced the fix? Can we get it cherry-picked into release_3...
2017 Jan 23
2
3.9 regression with legacy static assert macros (bad type resolution)
...llvm-dev <llvm-dev at lists.llvm.org> wrote:
>>>>>>>
>>>>>>> 3.9.0 and current release_39 (r90413) have issues with older static assertion macros like this one from an older libunwind:
>>>>>>>
>>>>>>> #define COMPILE_TIME_ASSERT( expr ) \
>>>>>>> extern int compile_time_assert_failed[ ( expr ) ? 1 : -1 ] __attribute__( ( unused ) );
>>>>>>>
>>>>>>> I notice that the issue is fixed on current trunk. Does anyone know what revision introduced the fix...
2007 Aug 18
1
[LLVMdev] Soft floating point support
This patch supplies software IEEE floating point support.
The comment from the patch reproduced below says all there is
to say.
This patch contains the prior "cleanup" patch; please don't apply
that one.
Please let me know of any bugs. It is tested reasonably well,
but until I put together random tests it's hard to have 100%
confidence.
Neil.
/* A self-contained host- and