public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Pedro Alves <pedro@palves.net>
To: John Baldwin <jhb@FreeBSD.org>, gdb-patches@sourceware.org
Subject: Re: [PATCH 1/2] nat/amd64-linux-siginfo.c: Move align attribute from typedef to struct
Date: Mon, 7 Jun 2021 23:20:35 +0100	[thread overview]
Message-ID: <00f901fb-b420-35e4-262f-65e4e3bacb3d@palves.net> (raw)
In-Reply-To: <31bde046-a86f-9995-545d-a03737cf493b@FreeBSD.org>

Hi John,

On 2021-06-05 10:20 p.m., John Baldwin wrote:
> On 6/4/21 5:14 PM, Pedro Alves wrote:
>> diff --git a/gdb/nat/amd64-linux-siginfo.c b/gdb/nat/amd64-linux-siginfo.c
>> index e2d2db6e112..9ff9361487a 100644
>> --- a/gdb/nat/amd64-linux-siginfo.c
>> +++ b/gdb/nat/amd64-linux-siginfo.c
>> @@ -206,7 +206,7 @@ typedef struct compat_siginfo
>>   /* For x32, clock_t in _sigchld is 64bit aligned at 4 bytes.  */
>>   typedef long __attribute__ ((__aligned__ (4))) compat_x32_clock_t;
>>   -typedef struct compat_x32_siginfo
>> +typedef struct __attribute__ ((__aligned__ (8))) compat_x32_siginfo
>>   {
>>     int si_signo;
>>     int si_errno;
>> @@ -263,7 +263,7 @@ typedef struct compat_x32_siginfo
>>         int _fd;
>>       } _sigpoll;
>>     } _sifields;
>> -} compat_x32_siginfo_t __attribute__ ((__aligned__ (8)));
>> +} compat_x32_siginfo_t;
>>     /* To simplify usage of siginfo fields.  */
> 
> Looks good to me.  Note that alignas() is part of C++11, so you could
> perhaps spell this a bit shorter as "alignas (8)" instead.
> 

That sounded like a good idea at first, however, if we were to do that,
I think we should do it to all __aligned__ attributes in the file.  But note
the one seen quoted above.  Here again:

  typedef long __attribute__ ((__aligned__ (4))) compat_x32_clock_t;

We can't use alignas for that, because alignas doesn't work with typedefs.  

GCC:

gdb/nat/amd64-linux-siginfo.c:207:14: error: attribute ignored [-Werror=attributes]
  207 | typedef long alignas (4) compat_x32_clock_t;
      |              ^~~~~~~

Clang:

gdb/nat/amd64-linux-siginfo.c:207:14: error: 'alignas' attribute cannot be applied to types
typedef long alignas (4) compat_x32_clock_t;
             ^

Clang attempt 2:

gdb/nat/amd64-linux-siginfo.c:207:33: error: 'alignas' attribute only applies to variables, data members and tag types
typedef long compat_x32_clock_t alignas (4);
                                ^


See answer 4 here:

 https://stackoverflow.com/questions/15788947/where-can-i-use-alignas-in-c11

  "These are the only places where the standard says an alignment-specifier (alignas(...)) may be applied. 
   Note that this does not include typedef declarations nor alias-declarations."

So for consistency I'm leaving the struct attribute as is too.

I'm going to merge the patches now.

Thanks,
Pedro Alves

  reply	other threads:[~2021-06-07 22:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-05  0:14 [PATCH 0/2] Fix alignment issue flagged by Clang in nat/amd64-linux-siginfo.c Pedro Alves
2021-06-05  0:14 ` [PATCH 1/2] nat/amd64-linux-siginfo.c: Move align attribute from typedef to struct Pedro Alves
2021-06-05 21:20   ` John Baldwin
2021-06-07 22:20     ` Pedro Alves [this message]
2021-06-07 22:42       ` John Baldwin
2021-06-05  0:14 ` [PATCH 2/2] nat/amd64-linux-siginfo.c: Remove typedefs Pedro Alves
2021-06-06 14:41 ` [PATCH 0/2] Fix alignment issue flagged by Clang in nat/amd64-linux-siginfo.c Simon Marchi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=00f901fb-b420-35e4-262f-65e4e3bacb3d@palves.net \
    --to=pedro@palves.net \
    --cc=gdb-patches@sourceware.org \
    --cc=jhb@FreeBSD.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).