From: Pedro Alves <pedro@palves.net>
To: gdb-patches@sourceware.org
Subject: [PATCH 0/2] Fix alignment issue flagged by Clang in nat/amd64-linux-siginfo.c
Date: Sat, 5 Jun 2021 01:14:25 +0100 [thread overview]
Message-ID: <20210605001427.3597687-1-pedro@palves.net> (raw)
Building GDB with current git Clang hits a number of problems. This
fixes one of them.
Pedro Alves (2):
nat/amd64-linux-siginfo.c: Move align attribute from typedef to struct
nat/amd64-linux-siginfo.c: Remove typedefs
gdb/nat/amd64-linux-siginfo.c | 28 ++++++++++++++--------------
1 file changed, 14 insertions(+), 14 deletions(-)
base-commit: 386de171cbffa86e804057030f3d64a404279f43
--
2.26.2
next reply other threads:[~2021-06-05 0:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-05 0:14 Pedro Alves [this message]
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
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=20210605001427.3597687-1-pedro@palves.net \
--to=pedro@palves.net \
--cc=gdb-patches@sourceware.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).