public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Martin Liška" <mliska@suse.cz>
To: Tobias Burnus <tobias@codesourcery.com>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] Libsanitizer: merge from master.
Date: Mon, 19 Oct 2020 09:11:09 +0200	[thread overview]
Message-ID: <f47204eb-71e0-ca6f-cda2-5f6436c5ea62@suse.cz> (raw)
In-Reply-To: <79bd1d9d-c276-caa5-bfeb-85832c2d21fc@codesourcery.com>

On 10/19/20 9:04 AM, Tobias Burnus wrote:
> Hi Martin,

Hello.

> 
> this patch caused here a build fail:
> 
> gcc-mainline/libsanitizer/sanitizer_common/sanitizer_stoptheworld_linux_libcdep.cpp:490:39: error: 'NT_X86_XSTATE' was not declared in this scope
> 
> It turned out that the used GLIBC of the cross build is 2.11.1.
> And that one does not contain this #define in 'elf.h'.

Thanks for the heads up.


> 
> I wonder whether we should do something like the following – what do you think?
> 
> --- a/libsanitizer/sanitizer_common/sanitizer_stoptheworld_linux_libcdep.cpp
> +++ b/libsanitizer/sanitizer_common/sanitizer_stoptheworld_linux_libcdep.cpp
> @@ -490 +490,5 @@ typedef user_regs_struct regs_struct;
> -static constexpr uptr kExtraRegs[] = {NT_X86_XSTATE, NT_FPREGSET};
> +static constexpr uptr kExtraRegs[] = {
> +#ifdef NT_X86_XSTATE
> +                                     NT_X86_XSTATE,
> +#endif
> +                                     DNT_FPREGSET};
> 
> Tobias

The change was introduced in the upstream commit:
https://github.com/llvm/llvm-project/commit/5813fca1076089c835de737834955a0fe7eb3898

Please create a LLVM bugzilla entry where you can mention that and they will
hopefully merge the change. We usually upstream the changes first.

Thanks,
Martin

  reply	other threads:[~2020-10-19  7:11 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-02  6:00 Martin Liška
2020-06-06 19:47 ` Andreas Schwab
2020-06-08 14:53   ` [PATCH] libsanitizer: use gnu++14 Martin Liška
2020-06-09  8:09     ` Martin Liška
2020-06-09 16:32       ` Richard Biener
2020-06-09 19:16         ` Martin Liška
2020-06-10 10:47           ` Richard Biener
2020-10-16  8:59 ` [PATCH] Libsanitizer: merge from master Martin Liška
2020-10-19  7:04   ` Tobias Burnus
2020-10-19  7:11     ` Martin Liška [this message]
2020-10-19  7:39       ` Tobias Burnus
2020-10-20  8:09         ` Tobias Burnus
2020-10-20  9:16           ` Martin Liška
2021-05-13  7:28 [PATCH] libsanitizer: " Martin Liška
2021-05-13 15:54 ` H.J. Lu
2021-05-13 17:27   ` Martin Liška
2021-05-13 20:01     ` H.J. Lu
2021-05-13 20:11       ` H.J. Lu
2021-06-04  7:32 ` Hongtao Liu
2021-06-04  7:36   ` Martin Liška
2021-06-04  7:53     ` Hongtao Liu

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=f47204eb-71e0-ca6f-cda2-5f6436c5ea62@suse.cz \
    --to=mliska@suse.cz \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=tobias@codesourcery.com \
    /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).