From: "H.J. Lu" <hjl.tools@gmail.com>
To: "Martin Liška" <mliska@suse.cz>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] libsanitizer: cherry-pick commit 05551c658269 from upstream
Date: Thu, 27 Apr 2023 09:25:03 -0700 [thread overview]
Message-ID: <CAMe9rOpXafMAW+71zoGNpkboOOq1aP_OY_bHyvzwJrYpK8C_1Q@mail.gmail.com> (raw)
In-Reply-To: <b4aa7d56-b08e-c926-4ca7-d43b5274b11c@suse.cz>
On Thu, Apr 27, 2023 at 12:03 AM Martin Liška <mliska@suse.cz> wrote:
>
> On 4/27/23 04:32, H.J. Lu via Gcc-patches wrote:
> > cherry-pick:
>
> Can you please wait a few days before it? I'm going to merge again
> in the near future after https://reviews.llvm.org/D144073 got handled.
Sure.
> Martin
>
> >
> > 05551c658269 [sanitizer] Correct alignment of x32 __sanitizer_siginfo
> >
> > * sanitizer_common/sanitizer_platform_limits_posix.h
> > (__sanitizer_siginfo_pad): Use u64 to align x32
> > __sanitizer_siginfo to 8 bytes.
> > ---
> > .../sanitizer_common/sanitizer_platform_limits_posix.h | 5 +++++
> > 1 file changed, 5 insertions(+)
> >
> > diff --git a/libsanitizer/sanitizer_common/sanitizer_platform_limits_posix.h b/libsanitizer/sanitizer_common/sanitizer_platform_limits_posix.h
> > index cfca7bdedbe..e6f298c26e1 100644
> > --- a/libsanitizer/sanitizer_common/sanitizer_platform_limits_posix.h
> > +++ b/libsanitizer/sanitizer_common/sanitizer_platform_limits_posix.h
> > @@ -578,8 +578,13 @@ struct __sanitizer_sigset_t {
> > #endif
> >
> > struct __sanitizer_siginfo_pad {
> > +#if SANITIZER_X32
> > + // x32 siginfo_t is aligned to 8 bytes.
> > + u64 pad[128 / sizeof(u64)];
> > +#else
> > // Require uptr, because siginfo_t is always pointer-size aligned on Linux.
> > uptr pad[128 / sizeof(uptr)];
> > +#endif
> > };
> >
> > #if SANITIZER_LINUX
>
--
H.J.
prev parent reply other threads:[~2023-04-27 16:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-27 2:32 H.J. Lu
2023-04-27 7:03 ` Martin Liška
2023-04-27 16:25 ` H.J. Lu [this message]
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=CAMe9rOpXafMAW+71zoGNpkboOOq1aP_OY_bHyvzwJrYpK8C_1Q@mail.gmail.com \
--to=hjl.tools@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=mliska@suse.cz \
/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).