[gimplefe] "Unknown tree: c_maybe_const_expr" error while parsing conditional expression

Hi, I am trying to replace c_parser_paren_condition (parser) in c_parser_gimple_if_stmt by c_parser_gimple_paren_condition (parser) as described in the patch I am trying test case void __GIMPLE () foo () { int a; bb_2: if (a == 2) goto bb_3; else goto bb_4; bb_3: a_2 = 4; bb_4:

Re: Two suggestions for gcc C compiler to extend C language (by WD Smith)

On 29/07/16 20:54, Warren D Smith wrote: > On 7/29/16, Jonathan Wakely wrote: >> Let's imagine we have a 4-bit type, called nibble. >> >> sizeof(nibble) == 1, because you can't have an object with a smaller size. >> >> nibble a[2]; >> sizeof(a) == 1; >> >> Because otherwise there isn't much benefi

Re: Potential bug about the order of destructors of static objects and atexit() callbacks in C++?

On 2016.08.01 at 18:16 +0800, lh mouse wrote: > Hello GCC developers, > > Reading the ISO C++ standard, > > 3.6.4 Termination [basic.start.term] > > 3 If the completion of the initialization of an object with > > static storage duration is sequenced before a call to std::atexit > > (see , 18.5), t

Potential bug about the order of destructors of static objects and atexit() callbacks in C++?

Hello GCC developers, Reading the ISO C++ standard, > 3.6.4 Termination [basic.start.term] > 3 If the completion of the initialization of an object with > static storage duration is sequenced before a call to std::atexit > (see , 18.5), the call to the function passed to std::atexit > is sequenced