From: Jeff Law <law@redhat.com>
To: Dragan Mladjenovic <dmladjenovic@wavecomp.com>,
Richard Biener <rguenther@suse.de>
Cc: Joseph Myers <joseph@codesourcery.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
Jakub Jelinek <jakub@redhat.com>,
Matthew Fortune <mfortune@gmail.com>,
"Maciej W . Rozycki" <macro@linux-mips.org>,
Faraz Shahbazker <fshahbazker@wavecomp.com>,
Aurelien Jarno <aurelien@aurel32.net>
Subject: Re: [PATCH 2/2][MIPS][RFC] Emit .note.GNU-stack for hard-float linux targets.
Date: Thu, 23 Jan 2020 15:22:00 -0000 [thread overview]
Message-ID: <7f48a6eb238785417a678f91a98bb9913f1f126e.camel@redhat.com> (raw)
In-Reply-To: <5E297C2F.8050400@wavecomp.com>
On Thu, 2020-01-23 at 10:58 +0000, Dragan Mladjenovic wrote:
> On 07.12.2019. 19:33, Jeff Law wrote:
> > On Thu, 2019-11-07 at 17:05 +0000, Dragan Mladjenovic wrote:
> > > On 01.11.2019. 11:32, Dragan Mladjenovic wrote:
> > > > On 10.08.2019. 00:15, Joseph Myers wrote:
> > > > > On Fri, 9 Aug 2019, Jeff Law wrote:
> > > > >
> > > > > > > 2019-08-05 Dragan Mladjenovic <dmladjenovic@wavecomp.com>
> > > > > > >
> > > > > > > * config.in: Regenerated.
> > > > > > > * config/mips/linux.h (NEED_INDICATE_EXEC_STACK): Define
> > > > > > > to 1
> > > > > > > for TARGET_LIBC_GNUSTACK.
> > > > > > > * configure: Regenerated.
> > > > > > > * configure.ac: Define TARGET_LIBC_GNUSTACK if glibc
> > > > > > > version is
> > > > > > > found 2.31 or greater.
> > > > > > My only concern here is the configure bits. So for example,
> > > > > > will it do
> > > > > > the right thing if you're cross-compiling to a MIPS linux
> > > > > > target? If
> > > > > > so, how? If not, do we need to make it a first class configure
> > > > > > option
> > > > > > so that it can be specified when building cross MIPS linux
> > > > > > toolchains?
> > > > >
> > > > > The key point of using GCC_GLIBC_VERSION_GTE_IFELSE is that (a)
> > > > > it checks
> > > > > the target glibc headers if available when GCC is built and (b)
> > > > > if not
> > > > > available, you can still use --with-glibc-version when
> > > > > configuring
> > > > > GCC, to
> > > > > get the right configuration in a bootstrap compiler built before
> > > > > glibc is
> > > > > built (the latter is necessary on some architectures to get the
> > > > > right
> > > > > stack-protector configuration for bootstrapping glibc, but may be
> > > > > useful
> > > > > in other cases as well).
> > > > >
> > > > > My main concern about this patch is the one I gave in
> > > > > <https://sourceware.org/ml/libc-alpha/2019-08/msg00086.html>
> > > > > about what
> > > > > the configuration mechanism should be, on a whole-toolchain
> > > > > level, to say
> > > > > whether you are OK with a requirement for a 4.8 or later kernel.
> > > > >
> > > >
> > > > Sorry for the late reply.
> > > >
> > > > I was waiting to backport [1] to most of the glibc release branches
> > > > in
> > > > use, but I got sidetracked along the way.
> > > >
> > > > After this patch lands the preferred way to configure gcc would be
> > > > using
> > > > --with-glibc-version=2.31 and to use said glibc.
> > > > If the user/distribution can live with minimal kernel requirement
> > > > of 4.8
> > > > the glibc used should be configured with --enable-kernel=4.8.
> > > > I also plan to backport the [1] to limit the opportunity for
> > > > building
> > > > the possibly broken glibc with the gcc w/ enabled .note.GNU-stack.
> > > >
> > > > This is all tedious and user has to be aware of all of it to make
> > > > it
> > > > work, but hopefully over time the distributions will default to
> > > > --with-glibc-version=2.31 and --enable-kernel=4.8. I guess
> > > > providing the
> > > > detailed NEWS entry for this change would help a bit.
> > > >
> > > > Is there any objections to getting this on the trunk before the end
> > > > of
> > > > stage1?
> > > >
> > > > [1] https://sourceware.org/ml/libc-alpha/2019-08/msg00639.html
> > > >
> > >
> > > Small update and gentle ping. The glibc change was backported all
> > > the
> > > way back to 2.24.
> > I think this is fine. And yes, we'd like to get it mentioned in the
> > release notes since I suspect folks will want the GNU-stack ELF notes.
> >
> > jeff
> >
> >
>
> I left this to fall through the cracks once again. In light of [1], is
> there any leeway for me to push this now?
>
> [1] https://gcc.gnu.org/ml/gcc/2020-01/msg00199.html
We generally allow more leeway for the ports simply because getting
something wrong doesn't have as wide an impact. Additionally, you're
using a configure-time flag to turn on the new behavior which further
limits the impact if something were to go wrong.
So if you want to commit it now, go ahead
jeff
>
>
next prev parent reply other threads:[~2020-01-23 15:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-05 10:43 [PATCH 0/2] [MIPS] Emit .note.GNU-stack for " Dragan Mladjenovic
2019-08-05 10:48 ` [PATCH 1/2][MIPS] Emit .note.GNU-stack for soft-float " Dragan Mladjenovic
2019-08-09 21:36 ` Jeff Law
2019-08-12 16:34 ` [EXTERNAL]Re: " Dragan Mladjenovic
2019-08-20 7:26 ` Jeff Law
2019-08-05 10:49 ` [PATCH 2/2][MIPS][RFC] Emit .note.GNU-stack for hard-float " Dragan Mladjenovic
2019-08-09 21:38 ` Jeff Law
2019-08-09 23:13 ` Joseph Myers
2019-11-01 10:32 ` Dragan Mladjenovic
2019-11-07 17:05 ` Dragan Mladjenovic
2019-11-27 18:59 ` [PING] " Dragan Mladjenovic
2019-12-07 18:33 ` Jeff Law
2020-01-23 11:14 ` Dragan Mladjenovic
2020-01-23 15:22 ` Jeff Law [this message]
2020-01-29 12:20 ` Tobias Burnus
2020-01-30 0:14 ` [EXTERNAL]Re: " Dragan Mladjenovic
2020-01-30 9:20 ` Dragan Mladjenovic
2019-08-09 22:03 ` Maciej W. Rozycki
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=7f48a6eb238785417a678f91a98bb9913f1f126e.camel@redhat.com \
--to=law@redhat.com \
--cc=aurelien@aurel32.net \
--cc=dmladjenovic@wavecomp.com \
--cc=fshahbazker@wavecomp.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=joseph@codesourcery.com \
--cc=macro@linux-mips.org \
--cc=mfortune@gmail.com \
--cc=rguenther@suse.de \
/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).