[PATCH] Introduce __BIGGEST_ALIGNMENT__ macro

Tim Northover t.p.northover at gmail.com
Sun Dec 14 08:46:47 PST 2014


> But the other opinion is that since this information *is* already
> known, at compile-time, by the compiler, and exposed via language
> constructs, where's the harm in also exposing it via a preprocessor
> #define?  I don't think any arguments have really been given *against*
> the idea of a GCC-style __BIGGEST_ALIGNMENT__.

I agree with this. The information is already exposed to the language,
excluding it from use during preprocessing achieves nothing for
compatibility, but makes some tasks significantly harder.

Cheers.

Tim.



More information about the cfe-commits mailing list