LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Dave Hansen <dave.hansen@linux.intel.com>,
	Ingo Molnar <mingo@kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Borislav Petkov <bp@alien8.de>
Subject: [RFD] x86: The future of MPX
Date: Fri, 27 Apr 2018 21:37:30 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.21.1804272122390.1596@nanos.tec.linutronix.de> (raw)

Dave,

I've got the following MPX related information:

 .... But they [Intel] certainly haven't maintained the whole MPX support
 in GCC at all since two or three years (e.g. bootstrap with MPX was broken
 since forever), so now it's gone from GCC. ....

and I know that GCC is discussing MPX removal since May last year at least.
To the best of my knowledge clang does not support it either.

So what's the state of this stuff? If we don't have a compiler supporting
it how on earth is that useful or even testable for anyone who does not
have access to some magic Intel internal compiler version?

If that's the sad state of affairs, then we just should move the whole
stuff into staging or simply queue it for removal in 4.18.

Thanks,

	tglx

             reply	other threads:[~2018-04-27 19:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-27 19:37 Thomas Gleixner [this message]
2018-04-28  9:18 ` Ingo Molnar
2018-04-28 16:36   ` Linus Torvalds
2018-04-28 16:44     ` Linus Torvalds
2018-04-30  4:44       ` Dave Hansen
2018-05-02 14:00         ` Borislav Petkov
2018-05-03 16:23           ` Eric W. Biederman
2018-04-28 17:50     ` Ingo Molnar
2018-04-29  4:46       ` Eric W. Biederman

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=alpine.DEB.2.21.1804272122390.1596@nanos.tec.linutronix.de \
    --to=tglx@linutronix.de \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    --subject='Re: [RFD] x86: The future of MPX' \
    /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

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 NNTP newsgroup(s).