public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeff Law <law@redhat.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Enable CET in cross compiler if possible
Date: Tue, 09 Jun 2020 13:43:16 -0600	[thread overview]
Message-ID: <eb4bc41d3acf3f46f55919b13294430cffd9720a.camel@redhat.com> (raw)
In-Reply-To: <CAMe9rOovxHj-63dHtE9gofLRVf+KVo+LhbB47qbQA5oOKhbGSw@mail.gmail.com>

On Fri, 2020-06-05 at 08:18 -0700, H.J. Lu wrote:
> On Tue, May 12, 2020 at 10:28 AM Jeff Law <law@redhat.com> wrote:
> > On Fri, 2020-05-08 at 06:11 -0700, H.J. Lu via Gcc-patches wrote:
> > > Don't perform CET run-time check for host when cross compiling.  Instead,
> > > enable CET in cross compiler if possible so that it will run on both CET
> > > and non-CET hosts.
> > > 
> > > config/
> > > 
> > >       PR bootstrap/94998
> > >       * cet.m4 (GCC_CET_HOST_FLAGS): Enable CET in cross compiler if
> > >       possible.
> > > 
> > > libiberty/
> > > 
> > >       PR bootstrap/94998
> > >       * configure: Regenerated.
> > > 
> > > lto-plugin/
> > > 
> > >       PR bootstrap/94998
> > >       * configure: Regenerated.
> > OK
> > jeff
> 
> OK for backport to GCC 10?
ISTM it doesn't meet the general criteria for backports, specifically it doesn't
fix a regression.  ISTM that the release managers would need to ACK for a
backport.

jeff


      reply	other threads:[~2020-06-09 19:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-08 13:11 H.J. Lu
2020-05-12 13:32 ` PING: " H.J. Lu
2020-05-12 17:28 ` Jeff Law
2020-06-05 15:18   ` H.J. Lu
2020-06-09 19:43     ` Jeff Law [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=eb4bc41d3acf3f46f55919b13294430cffd9720a.camel@redhat.com \
    --to=law@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=hjl.tools@gmail.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).