From: "H.J. Lu" <hjl.tools@gmail.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Richard Sandiford <richard.sandiford@arm.com>,
GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [GCC 8] [PATCH] Ignore the clobbered stack pointer in asm statment
Date: Thu, 24 Sep 2020 10:39:34 -0700 [thread overview]
Message-ID: <CAMe9rOqmGp8BgCvxsKsgZmXcrcR1=B25a+sCPOu9QwBFBYbMsA@mail.gmail.com> (raw)
In-Reply-To: <CAMe9rOqoRkpKcS4wiKGoF3oX=R1=3zPHQVz2MUjMgbaT8yfZbQ@mail.gmail.com>
On Thu, Sep 24, 2020 at 9:48 AM H.J. Lu <hjl.tools@gmail.com> wrote:
>
> On Wed, Sep 16, 2020 at 4:47 AM Jakub Jelinek <jakub@redhat.com> wrote:
> >
> > On Wed, Sep 16, 2020 at 12:34:50PM +0100, Richard Sandiford wrote:
> > > Jakub Jelinek via Gcc-patches <gcc-patches@gcc.gnu.org> writes:
> > > > On Mon, Sep 14, 2020 at 08:57:18AM -0700, H.J. Lu via Gcc-patches wrote:
> > > >> Something like this for GCC 8 and 9.
> > > >
> > > > Guess my preference would be to do this everywhere and then let's discuss if
> > > > we change the warning into error there or keep it being deprecated.
> > >
> > > Agreed FWIW. On turning it into an error: I think it might be better
> > > to wait a bit longer if we can.
> >
> > Ok. The patch is ok for trunk and affected release branches after a week.
> >
>
> I cherry-picked it to GCC 9 and 10 branches. GCC 8 needs some
> changes. I am enclosing the backported patch for GCC 8. I will check
> it in if there are no regressions on Linux/x86-64.
>
No regression. I am checking it into GCC 8 branch.
--
H.J.
prev parent reply other threads:[~2020-09-24 17:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-12 17:11 H.J. Lu
2020-09-12 17:37 ` Florian Weimer
2020-09-12 17:47 ` H.J. Lu
2020-09-12 17:52 ` Jakub Jelinek
2020-09-12 17:57 ` Florian Weimer
2020-09-14 14:35 ` Jakub Jelinek
2020-09-14 15:12 ` H.J. Lu
2020-09-14 15:57 ` H.J. Lu
2020-09-14 17:04 ` Jakub Jelinek
2020-09-14 20:31 ` H.J. Lu
2020-09-16 11:34 ` Richard Sandiford
2020-09-16 11:47 ` Jakub Jelinek
2020-09-24 16:48 ` [GCC 8] " H.J. Lu
2020-09-24 17:39 ` 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='CAMe9rOqmGp8BgCvxsKsgZmXcrcR1=B25a+sCPOu9QwBFBYbMsA@mail.gmail.com' \
--to=hjl.tools@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=richard.sandiford@arm.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).