[Ecls-list] GCC's builtins

[Gabriel Dos Reis]

On Thu, Feb 4, 2010 at 10:11 AM, Juan Jose Garcia-Ripoll
<juanjose.garciaripoll at googlemail.com> wrote:

>>
>> BTW, GCC attributes can make codes very ugly to read.  I don't have
>> a general remedy for that, except adopting the style we use in GCC's own
>> source code.
>
> The expectations are the ugliest part. Attributes of functions can be
> constrained to headers and are not that harmful. By the way, are you
> familiar with the problem of __attribute__((noreturn)) and longjmp that I
> mentioned before? Is GCC >= 4.x safe in this respect?

I believe it is now.  Note that as GCC's middle end is getting clever, some
semantics aspects of GNU extensions not considered before are coming
to the fore -- this is not just for 'noreturn', but for many other GNUisms.

-- Gaby