From: Joseph Myers <joseph@codesourcery.com>
To: Steve Ellcey <sellcey@cavium.com>
Cc: Martin Sebor <msebor@gmail.com>,
Gcc Patch List <gcc-patches@gcc.gnu.org>,
Jonathan Wakely <jwakely@redhat.com>,
libstdc++ <libstdc++@gcc.gnu.org>
Subject: Re: [PATCH] detect incompatible aliases (PR c/81854)
Date: Wed, 20 Sep 2017 18:05:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.20.1709201801350.18346@digraph.polyomino.org.uk> (raw)
In-Reply-To: <1505929541.2286.115.camel@cavium.com>
[-- Attachment #1: Type: text/plain, Size: 1172 bytes --]
On Wed, 20 Sep 2017, Steve Ellcey wrote:
> > I'm not intimately familiar with the Glibc ifunc infrastructure
> > to suggest a good solution here, so assuming this works my only
> > idea is to suppress the warning for these builds.
> >
> > Joseph, do you have a better suggestion?
> >
> > Martin
>
> Now that I know building GCC with '--enable-gnu-indirect-function' lets
> me build GLIBC with IFUNCs maybe it is time for GLIBC to require this
> instead of just recommending it. Â Though I guess that is a discussion
> to take over to the libc-alpha mailing list.
We should not break builds with default GCC configurations, for any GCC
version supported for building glibc. The point to require that option is
the point where all GCC versions supported for building glibc default to
that option on all architectures for which IFUNCs are used in glibc (and
even then you'd have to allow for the case of --enable-multi-arch
defaulting to on because new binutils has IFUNC support and not break
builds with GCC predating that binutils version - really, the
architecture-specific default in GCC is very questionable).
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2017-09-20 18:05 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-18 8:10 Martin Sebor
2017-08-18 13:10 ` Joseph Myers
2017-08-18 13:57 ` Jonathan Wakely
2017-08-18 18:22 ` Martin Sebor
2017-08-18 18:37 ` Jonathan Wakely
2017-08-18 21:02 ` Martin Sebor
2017-09-02 22:50 ` [PING] " Martin Sebor
2017-09-12 16:17 ` Joseph Myers
2017-09-18 21:21 ` Martin Sebor
2017-09-18 21:44 ` Joseph Myers
2017-09-19 15:16 ` Martin Sebor
2017-09-20 15:37 ` Steve Ellcey
2017-09-20 16:17 ` Martin Sebor
2017-09-20 16:38 ` Steve Ellcey
2017-09-20 17:23 ` Steve Ellcey
2017-09-20 17:32 ` Martin Sebor
2017-09-20 17:45 ` Steve Ellcey
2017-09-20 18:05 ` Joseph Myers [this message]
2017-09-20 18:01 ` Joseph Myers
2017-09-20 18:08 ` Steve Ellcey
2017-09-20 18:14 ` Joseph Myers
2017-09-20 21:01 ` Joseph Myers
2017-09-20 21:32 ` Martin Sebor
2017-09-20 21:45 ` Joseph Myers
2017-10-02 19:49 ` Steve Ellcey
2017-10-02 19:53 ` Joseph Myers
2017-10-02 20:17 ` Martin Sebor
2017-10-03 21:41 ` Andreas Schwab
2017-10-03 23:43 ` Martin Sebor
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.20.1709201801350.18346@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jwakely@redhat.com \
--cc=libstdc++@gcc.gnu.org \
--cc=msebor@gmail.com \
--cc=sellcey@cavium.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).