From: "Martin Liška" <mliska@suse.cz>
To: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: libsanitizer: merge from upstream
Date: Tue, 30 Aug 2022 12:53:23 +0200 [thread overview]
Message-ID: <10f0f307-2522-fa2f-ae66-e842c76a7f55@suse.cz> (raw)
In-Reply-To: <df41aa83-4958-477b-8c2e-49f6ba381c86@suse.cz>
On 5/4/22 10:59, Martin Liška wrote:
> Hello.
>
> I'm going to do merge from upstream.
>
> Patch can bootstrap on x86_64-linux-gnu and survives regression tests. I've also tested
> on ppc64le-linux-gnu and verified the ABI.
>
> The only real change is a small change in
> gcc/testsuite/c-c++-common/asan/alloca_loop_unpoisoning.c
> where we need --param=asan-use-after-return=0.
>
> I'm going to push the patches.
>
> Thanks,
> Martin
Hi.
I've just done one more merge from upstream.
Upstream revision: 84a71d5259c2682403cdbd8710592410a2f128ab.
Cheers,
Martin
next prev parent reply other threads:[~2022-08-30 10:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-04 8:59 Martin Liška
2022-05-04 23:07 ` [PATCH] libsanitizer: cherry-pick commit f52e365092aa " H.J. Lu
2022-05-05 11:24 ` Martin Liška
2022-05-05 16:21 ` H.J. Lu
2022-05-05 18:28 ` Martin Liška
2022-05-05 18:40 ` H.J. Lu
2022-08-30 10:53 ` Martin Liška [this message]
2022-09-04 19:50 ` libsanitizer: merge " Iain Sandoe
2022-09-05 7:31 ` Martin Liška
2022-09-05 7:44 ` Rainer Orth
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=10f0f307-2522-fa2f-ae66-e842c76a7f55@suse.cz \
--to=mliska@suse.cz \
--cc=gcc-patches@gcc.gnu.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).