This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: __HAVE_BUILTIN_SETJMP__: why?


Fergus Henderson <fjh@cs.mu.OZ.AU> writes:

|> You could use something like
|> 
|> 	#if (__GNUC__ > 2 || (__GNUC__ == 2 && __GNUC_MINOR__ >= 8))
|> 
|> instead of
|> 	
|> 	#ifdef __HAVE_BUILTIN_SETJMP__
|> 
|> so it is not strictly necessary, but the definition of __HAVE_BUILTIN_SETJMP__
|> is pretty harmless, so personally I would leave it in to avoid breaking any
|> existing code which relies on it.

Any code that relies on an undocumented identifier that is in the
implementation's name space is broken by design.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE GmbH, Deutschherrnstr. 15-19, D-90429 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]