From: Andreas Jaeger <aj@suse.de>
To: Jakub Jelinek <jakub@redhat.com>
Cc: libc-hacker@sources.redhat.com, Roland McGrath <roland@redhat.com>
Subject: Re: Fix locale/weight.h with GCC 3.5
Date: Thu, 09 Sep 2004 09:20:00 -0000 [thread overview]
Message-ID: <hobrgfg5nl.fsf@reger.suse.de> (raw)
In-Reply-To: <20040909060047.GS30497@sunsite.ms.mff.cuni.cz> (Jakub Jelinek's message of "Thu, 9 Sep 2004 08:00:47 +0200")
[-- Attachment #1: Type: text/plain, Size: 1629 bytes --]
Jakub Jelinek <jakub@redhat.com> writes:
> On Wed, Sep 08, 2004 at 09:44:33PM +0200, Andreas Jaeger wrote:
>> Wait - this seems to be produced even with the current glibc without my
>> changes (glibc compiled by GCC 3.3):
>> nm /lib64/ld-linux-x86-64.so.2 |grep elf_machine_rela
>> 0000000000000d40 t elf_machine_rela.0
>> 0000000000007fa0 t elf_machine_rela.0
>> 000000000000d010 t elf_machine_rela.0
>> 0000000000000d70 t elf_machine_rela_relative.1
>> 0000000000008330 t elf_machine_rela_relative.1
>>
>> For reference, compile:
>> int
>> test (int j)
>> {
>>
>> static inline int
>> __attribute__ ((always_inline))
>> test_inline (int i)
>> {
>> return i++;
>> }
>>
>> return test_inline (j);
>> }
>>
>> I get with GCC 3.3:
>> gromit:/tmp:[0]$ gcc -Wall -c t.c -O2
>> gromit:/tmp:[0]$ nm t.o
>> 0000000000000010 T test
>> 0000000000000000 t test_inline.0
>
> You mean hammer branch GCC 3.3, right?
Yes, I do.
> Stock 3.3 should be ok. GCC 3.4 initially also emitted successfully inlined
> nested functions as separate functions too, but this was fixed in July this
> year, see PR middle-end/15345, c/16450.
That explains 3.4. But why do I get these also with GCC 3.5 with my
patch (nm elf/dl-reloc.o):
00000000000002a0 t elf_machine_lazy_rel.7373
00000000000002f0 t elf_machine_rela.7361
0000000000000110 t elf_machine_rela_relative.7369
Andreas
--
Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj
SUSE Linux AG, Maxfeldstr. 5, 90409 Nürnberg, Germany
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
[-- Attachment #2: Type: application/pgp-signature, Size: 188 bytes --]
next prev parent reply other threads:[~2004-09-09 9:20 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-06 18:52 Andreas Jaeger
2004-09-06 19:22 ` Andreas Jaeger
2004-09-06 21:21 ` Roland McGrath
2004-09-07 5:06 ` Andreas Jaeger
2004-09-07 8:02 ` Roland McGrath
2004-09-07 11:26 ` Andreas Jaeger
2004-09-07 18:09 ` Andreas Jaeger
2004-09-07 21:26 ` Roland McGrath
2004-09-08 4:57 ` Andreas Jaeger
2004-09-08 5:40 ` Andreas Jaeger
2004-09-08 17:01 ` Roland McGrath
2004-09-08 17:24 ` Andreas Jaeger
2004-09-08 17:46 ` Roland McGrath
2004-09-08 19:33 ` Andreas Jaeger
2004-09-08 19:44 ` Andreas Jaeger
2004-09-08 20:02 ` Roland McGrath
2004-09-09 8:19 ` Jakub Jelinek
2004-09-09 9:20 ` Andreas Jaeger [this message]
2004-09-21 7:19 ` Andreas Jaeger
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=hobrgfg5nl.fsf@reger.suse.de \
--to=aj@suse.de \
--cc=jakub@redhat.com \
--cc=libc-hacker@sources.redhat.com \
--cc=roland@redhat.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).