From: David Edelsohn <dje.gcc@gmail.com>
To: Bill Schmidt <wschmidt@linux.vnet.ibm.com>,
Jakub Jelinek <jakub@redhat.com>,
Richard Biener <rguenther@suse.de>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
Jonathan Wakely <jwakely@redhat.com>
Subject: Re: [PATCH, rs6000, libstdc++] Add baseline_symbols.txt for powerpc64le-linux-gnu
Date: Tue, 07 Apr 2015 13:03:00 -0000 [thread overview]
Message-ID: <CAGWvnykfhh=PN4nwbT_+ha_rRS4Ne30_VAQw6NA4eFbdpQUVjQ@mail.gmail.com> (raw)
In-Reply-To: <1428368093.2816.51.camel@gnopaine>
On Mon, Apr 6, 2015 at 8:54 PM, Bill Schmidt
<wschmidt@linux.vnet.ibm.com> wrote:
> Hi,
>
> It was recently pointed out that we still don't have a separate
> baseline_symbols.txt for powerpc64le-linux-gnu. This patch modifies
> configure.host to create a new abi_baseline_pair for powerpc64le and
> provides the generated symbol file (from "make new-abi-baseline").
>
> Is this ok for stage4, or should I hold it until after 5.1 branches?
>
> Thanks,
> Bill
>
>
> 2015-04-06 Bill Schmidt <wschmidt@linux.vnet.ibm.com>
>
> * config/abi/post/powerpc64le-linux-gnu/baseline_symbols.txt: New
> baseline symbols file.
> * configure.host: Add separate case for powerpc64le.
It's okay with me, but it really is a question for the RMs.
Thanks, David
next parent reply other threads:[~2015-04-07 13:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1428368093.2816.51.camel@gnopaine>
2015-04-07 13:03 ` David Edelsohn [this message]
2015-04-07 13:41 ` Richard Biener
2015-04-07 2:31 Bill Schmidt
2015-04-07 13:09 ` Jakub Jelinek
2015-04-07 13:19 ` Jonathan Wakely
2015-04-07 13:40 ` Bill Schmidt
2015-04-07 13:45 ` Jakub Jelinek
2015-04-07 13:49 ` David Edelsohn
2015-04-07 13:54 ` Bill Schmidt
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='CAGWvnykfhh=PN4nwbT_+ha_rRS4Ne30_VAQw6NA4eFbdpQUVjQ@mail.gmail.com' \
--to=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=jwakely@redhat.com \
--cc=rguenther@suse.de \
--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).