From: "H. J. Lu" <hjl@lucon.org>
To: rittle@labs.mot.com
Cc: binutils@sources.redhat.com, gcc-bugs@gcc.gnu.org
Subject: Re: GCC testsuite run before and after ~2.12.1 upgraded to pre-2.13
Date: Thu, 25 Jul 2002 22:09:00 -0000 [thread overview]
Message-ID: <20020725213939.A1054@lucon.org> (raw)
In-Reply-To: <200207260430.g6Q4UOSi002790@latour.rsch.comm.mot.com>; from rittle@latour.rsch.comm.mot.com on Thu, Jul 25, 2002 at 11:30:24PM -0500
On Thu, Jul 25, 2002 at 11:30:24PM -0500, Loren James Rittle wrote:
> (Based upon the analysis below, I am CCing gcc-bugs RE PR 7171. The
> version numbers in the subject line refer to binutils. Quick
> summary: More C++ test cases fail with binutils pre-2.13 than failed
> with binutils ~2.12.1. This behavior has been spotted on a wide
> variety of platforms.)
>
> Thank you Jason R Thorpe, Alan Modra and Ian Lance Taylor for the
> discussion you held last week on this topic. Here is what I see when
> I build "element_access.exe" on i386-unknown-freebsd4.6 (a newly
> failing C++ libstdc++-v3 test case, upon binutils upgrade to pre-2.13
> with full rebootstrap of gcc) with -Map:
>
> [...]
> .rodata 0x08048e80 0x14d
> *(.rodata .rodata.* .gnu.linkonce.r.*)
> .rodata 0x08048e80 0x1 /usr/lib/crt1.o
> *fill* 0x08048e81 0x1f 00
> .rodata 0x08048ea0 0x10f /var/tmp//ccAEn9wX.o
> *fill* 0x08048faf 0x1 00
> .gnu.linkonce.r._ZTISt12out_of_range
> 0x08048fb0 0xc /var/tmp//ccAEn9wX.o
> 0x08048fb0 _ZTISt12out_of_range
> .gnu.linkonce.r._ZTSSt12out_of_range
> 0x08048fbc 0x11 /var/tmp//ccAEn9wX.o
> 0x08048fbc _ZTSSt12out_of_range
> [...]
>
> Tracing back, I see these entries in "element_access.o":
>
> [16] .gnu.linkonce.r._ PROGBITS 00000000 008f2c 00000c 00 WA 0 0 4
> [18] .gnu.linkonce.r._ PROGBITS 00000000 008f38 000011 00 A 0 0 1
>
> Based on size of element, it appears that _ZTISt12out_of_range (AKA
> ``typeinfo for std::out_of_range'') is of interest. Tracing back from
> here, I see this in the g++-produced asm:
>
> .section .gnu.linkonce.r._ZTISt12out_of_range,"aw",@progbits
>
FWIW, on Linux/x86, I got
.section .gnu.linkonce.d._ZTISt12out_of_range,"aw",@progbits
.section .gnu.linkonce.r._ZTSSt12out_of_range,"a",@progbits
.section .gnu.linkonce.d._ZTISt11logic_error,"aw",@progbits
.section .gnu.linkonce.r._ZTSSt11logic_error,"a",@progbits
.section .gnu.linkonce.d._ZTISt9exception,"aw",@progbits
.section .gnu.linkonce.r._ZTSSt9exception,"a",@progbits
You may want to check out why BSDs are different.
H.J.
next prev parent reply other threads:[~2002-07-26 4:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-25 21:53 Loren James Rittle
2002-07-25 22:09 ` H. J. Lu [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-07-18 20:07 Loren James Rittle
2002-07-19 3:47 ` Alan Modra
2002-07-19 11:16 ` Jason R Thorpe
2002-07-19 17:29 ` Alan Modra
2002-07-19 18:21 ` Jason R Thorpe
2002-07-19 18:46 ` Alan Modra
2002-07-19 18:52 ` Jason R Thorpe
2002-07-19 19:43 ` Alan Modra
2002-07-19 21:14 ` Jason R Thorpe
2002-07-19 21:33 ` Ian Lance Taylor
2002-07-20 11:33 ` Alan Modra
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=20020725213939.A1054@lucon.org \
--to=hjl@lucon.org \
--cc=binutils@sources.redhat.com \
--cc=gcc-bugs@gcc.gnu.org \
--cc=rittle@labs.mot.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).