From: Jakub Jelinek <jakub@redhat.com>
To: "Martin Liška" <mliska@suse.cz>, "Jeff Law" <law@redhat.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] Remove MPX support
Date: Wed, 30 May 2018 18:47:00 -0000 [thread overview]
Message-ID: <20180530174011.GP14160@tucnak> (raw)
In-Reply-To: <fef388b9-5447-9751-4a23-4a666e2e08cb@redhat.com>
On Tue, May 01, 2018 at 11:28:13AM -0600, Jeff Law wrote:
> On 04/27/2018 05:00 AM, Martin Liška wrote:
> > I'm sending patch that removes MPX. It preserves all options -fcheck-pointer-bounds, -fchkp-* and -mmpx
> > target option. These options are now NOP. On the contrary following options were removed:
> > --static-libmpx -static-libmpxwrappers. Is it fine to remove them?
> >
> > Patch can bootstrap on x86_64-linux-gnu, ppc64le-linux-gnu and survives regression tests.
> > And the patch bootstraps also on aarch64-linux-gnu.
> >
> > Note that the patch is trim for files (some) that are removed. Doing that was necessary to
> > fit in 100K with bzip2 patch file.
> >
> > Ready to be installed after some time?
> Yes. Please coordinate with Jakub & Richi since this touches a fair
> amount of code and might interfere with attempts to backport changes
> from the trunk into the gcc-8 release branch.
>
> I wouldn't be surprised if we find bits of MPX code after the patch is
> installed. Changes to remove any stragglers are pre-approved as well.
Martin, any progress with this? I'm not worried about MPX removal making
backports much harder.
Jakub
next prev parent reply other threads:[~2018-05-30 17:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-27 11:28 Martin Liška
2018-05-01 17:28 ` Jeff Law
2018-05-30 18:47 ` Jakub Jelinek [this message]
2018-05-31 12:23 ` Martin Liška
2018-06-08 11:09 ` [PATCH] Come up with Deprecated option flag Martin Liška
2018-06-11 19:19 ` Jeff Law
2018-06-11 19:34 ` Paul Koning
2018-06-12 14:22 ` Martin Liška
2018-06-08 11:10 ` [PATCH] Use flags_from_decl_or_type in lto_symtab_merge_p (PR ipa/85248) Martin Liška
2018-06-13 11:22 ` Richard Biener
2018-06-20 8:05 ` Martin Liška
2018-06-20 8:35 ` Richard Biener
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=20180530174011.GP14160@tucnak \
--to=jakub@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=law@redhat.com \
--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).