On 11/29/18 8:34 AM, Martin Sebor wrote:
>
> GCC does disallow decreasing the function alignment -- but only
> for functions that were already declared with a more restrictive
> one. Like this:
>
> __attribute__ ((aligned (4))) void f (void);
>
> __attribute__ ((aligned (2))) void f (void);
On 11/28/18 9:07 PM, Jeff Law wrote:
On 11/27/18 11:57 AM, Martin Sebor wrote:
On 11/26/18 3:37 PM, Jeff Law wrote:
On 11/23/18 12:31 PM, Martin Sebor wrote:
GCC currently accepts the declaration of f0 below but ignores
the attribute. On aarch64 (and I presume on other targets with
a default
On 11/27/18 11:57 AM, Martin Sebor wrote:
> On 11/26/18 3:37 PM, Jeff Law wrote:
>> On 11/23/18 12:31 PM, Martin Sebor wrote:
>>> GCC currently accepts the declaration of f0 below but ignores
>>> the attribute. On aarch64 (and I presume on other targets with
>>> a default function alignment greate
On 11/28/18 6:04 AM, Florian Weimer wrote:
* Martin Sebor:
At the same time, the following passes on x86_64:
__attribute__ ((aligned (1))) void f1 (void) { }
_Static_assert (__alignof__ (f1) == 1); // wrong alignof result
__attribute__ ((aligned)) void f0 (void) { }
_Static_asse
* Martin Sebor:
> At the same time, the following passes on x86_64:
>
> __attribute__ ((aligned (1))) void f1 (void) { }
> _Static_assert (__alignof__ (f1) == 1); // wrong alignof result
>
> __attribute__ ((aligned)) void f0 (void) { }
> _Static_assert (__alignof__ (f0) == 16);
>
> __a
On 11/27/18 11:57 AM, Martin Sebor wrote:
On 11/26/18 3:37 PM, Jeff Law wrote:
On 11/23/18 12:31 PM, Martin Sebor wrote:
GCC currently accepts the declaration of f0 below but ignores
the attribute. On aarch64 (and I presume on other targets with
a default function alignment greater than 1), GC
On 11/26/18 3:37 PM, Jeff Law wrote:
On 11/23/18 12:31 PM, Martin Sebor wrote:
GCC currently accepts the declaration of f0 below but ignores
the attribute. On aarch64 (and I presume on other targets with
a default function alignment greater than 1), GCC rejects f1
with an error, even though it
On 11/23/18 12:31 PM, Martin Sebor wrote:
> GCC currently accepts the declaration of f0 below but ignores
> the attribute. On aarch64 (and I presume on other targets with
> a default function alignment greater than 1), GCC rejects f1
> with an error, even though it accepts -falign-functions=1
> wi
GCC currently accepts the declaration of f0 below but ignores
the attribute. On aarch64 (and I presume on other targets with
a default function alignment greater than 1), GCC rejects f1
with an error, even though it accepts -falign-functions=1
without as much as a warning.
Clang, on the other ha
