Displaying 7 results from an estimated 7 matches for "compile_time_assert_fail".
Did you mean:
compile_time_assert_failed
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 tagged, but having it on the branch will make it easier for distribu...
2016 Dec 27
2
3.9 regression with legacy static assert macros (bad type resolution)
...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 was just tagged, but having it on the branc...
2016 Dec 27
3
3.9 regression with legacy static assert macros (bad type resolution)
...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 was just tagged, but having it on t...
2016 Dec 23
0
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-picked into release_39? I know 3.9.1 final was just tagged, but having it on the branch will make it easier fo...
2016 Dec 24
2
3.9 regression with legacy static assert macros (bad type resolution)
...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 was just tagged, but having it on the branch will make it e...
2016 Dec 27
0
3.9 regression with legacy static assert macros (bad type resolution)
...ev <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 was just tagged, but having it on the branch will m...
2017 Jan 23
2
3.9 regression with legacy static assert macros (bad type resolution)
...t;>>>>>> 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 tagged, but...