From: Eric Botcazou <ebotcazou@libertysurf.fr>
To: Hans-Peter Nilsson <hp@bitrange.com>
Cc: binutils@sources.redhat.com,
Hans-Peter Nilsson <hans-peter.nilsson@axis.com>
Subject: Re: [RFA:] Trivial test for .gnu.warning.SYMBOL
Date: Sun, 13 Feb 2005 20:39:00 -0000 [thread overview]
Message-ID: <200502131637.35885.ebotcazou@libertysurf.fr> (raw)
In-Reply-To: <Pine.BSF.4.58.0502130838370.49231@dair.pair.com>
> Yes it does, at least for sparc64-linux-gnu cross from
> i686-pc-linux-gnu.
And? What do you think will happen on a 64-bit SPARC platform where the text
segment is not located in the lower 32-bit part of the address space?
> The truncation doesn't matter for the purpose of this test, as
> long as ld doesn't emit an error or warning message.
./ld-new -L/home/eric/cvs/binutils/ld/testsuite/ld-elf -o tmpdir/dump
tmpdir/dump0.o tmpdir/dump1.o tmpdir/dump2.o
failed with: <tmpdir/dump1.o:(.text+0x0): warning: witty one-liner
tmpdir/dump1.o:(.text+0x0): relocation truncated to fit: R_SPARC_32 against
symbol `symbol1' defined in .text section in tmpdir/dump2.o>, expected:
<^[^\\n]*\): warning: witty one-liner$>
tmpdir/dump1.o:(.text+0x0): warning: witty one-liner
tmpdir/dump1.o:(.text+0x0): relocation truncated to fit: R_SPARC_32 against
symbol `symbol1' defined in .text section in tmpdir/dump2.o
FAIL: ld-elf/warn1
This is on Solaris 64-bit.
> No need this time, but for future reference, look in
> ld/testsuite/ld-lib.exp:run_dump_test, where the big header
> comment provides all :-/ documentation. There's a specific
> directive to exclude targets.
Thanks.
--
Eric Botcazou
next prev parent reply other threads:[~2005-02-13 15:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-06 14:33 Hans-Peter Nilsson
2005-02-06 15:07 ` Ian Lance Taylor
2005-02-13 17:18 ` Eric Botcazou
2005-02-13 19:22 ` Hans-Peter Nilsson
2005-02-13 20:39 ` Eric Botcazou [this message]
2005-02-14 0:17 ` Hans-Peter Nilsson
2005-02-14 9:18 ` Eric Botcazou
2005-02-14 10:38 ` Hans-Peter Nilsson
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=200502131637.35885.ebotcazou@libertysurf.fr \
--to=ebotcazou@libertysurf.fr \
--cc=binutils@sources.redhat.com \
--cc=hans-peter.nilsson@axis.com \
--cc=hp@bitrange.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).