[PATCH] Introduce __BIGGEST_ALIGNMENT__ macro

[mats petersson]

So, should I do something more, or are what's happening now? Sorry if this
is something "I should know".

--
Mats

On 14 December 2014 at 16:46, Tim Northover <t.p.northover at gmail.com> wrote:

> > 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.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-commits/attachments/20141214/6f9401f2/attachment.html>