From: Joseph Myers <joseph@codesourcery.com>
To: Tulio Magno Quites Machado Filho <tuliom@linux.vnet.ibm.com>
Cc: Segher Boessenkool <segher@kernel.crashing.org>,
Aaron Sawdey <acsawdey@linux.vnet.ibm.com>,
<gcc-patches@gcc.gnu.org>, David Edelsohn <dje.gcc@gmail.com>,
Bill Schmidt <wschmidt@linux.vnet.ibm.com>
Subject: Re: [PATCH] builtin expansion of strncmp for rs6000
Date: Fri, 13 Jan 2017 13:01:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.20.1701131257220.22001@digraph.polyomino.org.uk> (raw)
In-Reply-To: <877f5zjhzi.fsf@linux.vnet.ibm.com>
On Fri, 13 Jan 2017, Tulio Magno Quites Machado Filho wrote:
> > Tulio will look at fixing it in glibc tomorrow. Thanks for the report,
>
> Does this code affects a specific rs6000 build? i.e. powerpc64le -mcpu=power8.
> Or is it generic?
build-many-glibcs.py does not use any special configure options in GCC or
glibc to select a particular processor (which I think means a POWER8
default in GCC; I don't think powerpc glibc yet determines which sysdeps
directories to use based on compiler defaults, however, though we've
discussed that this approach, as used by the ARM port, is to be preferred
over --with-cpu).
--
Joseph S. Myers
joseph@codesourcery.com
prev parent reply other threads:[~2017-01-13 13:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-15 16:34 Aaron Sawdey
2016-12-16 23:57 ` Segher Boessenkool
2016-12-19 15:58 ` Aaron Sawdey
2016-12-19 17:32 ` Segher Boessenkool
2017-01-12 17:53 ` Joseph Myers
2017-01-12 21:54 ` Segher Boessenkool
2017-01-13 11:51 ` Tulio Magno Quites Machado Filho
2017-01-13 13:01 ` Joseph Myers [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=alpine.DEB.2.20.1701131257220.22001@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=acsawdey@linux.vnet.ibm.com \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=segher@kernel.crashing.org \
--cc=tuliom@linux.vnet.ibm.com \
--cc=wschmidt@linux.vnet.ibm.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).