This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: Generating minimum libstdc++ symbols for a new platform
- From: David Edelsohn <dje dot gcc at gmail dot com>
- To: Bill Schmidt <wschmidt at linux dot vnet dot ibm dot com>, GCC Development <gcc at gcc dot gnu dot org>, David Edelsohn <dje dot gcc at gmail dot com>, Peter Bergner <bergner at vnet dot ibm dot com>, "libstdc++ at gcc dot gnu dot org" <libstdc++ at gcc dot gnu dot org>, Richard Sandiford <rdsandiford at googlemail dot com>
- Date: Tue, 28 Jan 2014 12:28:02 -0500
- Subject: Re: Generating minimum libstdc++ symbols for a new platform
- Authentication-results: sourceware.org; auth=none
- References: <1389285030 dot 4862 dot 6 dot camel at oc8801110288 dot ibm dot com> <877g9mk9hj dot fsf at talisman dot default>
On Sun, Jan 26, 2014 at 11:12 AM, Richard Sandiford
<rdsandiford@googlemail.com> wrote:
> [adding libstdc++@]
>
> Bill Schmidt <wschmidt@linux.vnet.ibm.com> writes:
>> It was recently pointed out to me that our new powerpc64le-linux-gnu
>> target does not yet have a corresponding directory in libstdc
>> ++-v3/config/abi/post/ to hold a baseline_symbols.txt for the platform.
>> I've been looking around and haven't found any documentation for how the
>> minimum baseline symbols file should be generated. Can someone please
>> enlighten me about the process?
>
> Yeah, I'd like to know this too. abi_check has been failing for
> mips*-linux-gnu for a long while but I was never sure what to do about it.
libstdc++/testsuite Makefile has a "new-abi-baseline" target.
# Use 'new-abi-baseline' to create an initial symbol file. Then run
# 'check-abi' to test for changes against that file.
- David