public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: "H.J. Lu" <hjl.tools@gmail.com>
To: Hans-Peter Nilsson <hp@bitrange.com>, binutils@sourceware.org
Subject: Re: ld -z options
Date: Thu, 14 Jul 2011 17:16:00 -0000	[thread overview]
Message-ID: <CAMe9rOo4CR8dW2EF=WC-0GgMm4GVvgQuSUGgNyBSvaVt5w0+Zw@mail.gmail.com> (raw)
In-Reply-To: <20110714111802.GZ26365@bubble.grove.modra.org>

On Thu, Jul 14, 2011 at 4:18 AM, Alan Modra <amodra@gmail.com> wrote:
> On Thu, Jul 14, 2011 at 04:06:03AM -0400, Hans-Peter Nilsson wrote:
>> Talking to myself...
>>
>> On Thu, 14 Jul 2011, Hans-Peter Nilsson wrote:
>> > This caused several test-cases to go from PASS to UNRESOLVED for
>> > cris-axis-linux-gnu
>>
>> It seems this would happen for e.g. ia64-*-linux-gnu too.
>
> Yes.
>
>> > All preceded by a linker warning ".../ld-new: warning: -z relro
>> > ignored." in ld.log.  The UNRESOLVED status then cause the
>> > check-ld to return error.  According to the dejagnu docs, the
>> > UNRESOLVED is an indication of an error in the testsuite (likely
>> > the unexpected warning).
>>
>> That's a bug in ld-elf/binutils.exp or the new warning message;
>> binutils.exp tests [string match "*not supported*" $link_output]
>>              || [string match "*unrecognized option*" $link_output]
>> which doesn't match "warning: -z relro ignored.".
>>
>> Which one should be adjusted?
>
> Probably the new one.  Patch preapproved if you'd like to do it.

I checked in this:

diff --git a/ld/testsuite/ChangeLog b/ld/testsuite/ChangeLog
index ee6987f..bc01d77 100644
--- a/ld/testsuite/ChangeLog
+++ b/ld/testsuite/ChangeLog
@@ -1,3 +1,8 @@
+2011-07-14  H.J. Lu  <hongjiu.lu@intel.com>
+
+	* ld-elf/binutils.exp (binutils_test): Also check ignored
+	"-z relro".
+
 2011-07-14  Alan Modra  <amodra@gmail.com>

 	* ld-scripts/section-flags.exp: Pass --local-store 0:0 for
diff --git a/ld/testsuite/ld-elf/binutils.exp b/ld/testsuite/ld-elf/binutils.exp
index 380bd26..382d50f 100644
--- a/ld/testsuite/ld-elf/binutils.exp
+++ b/ld/testsuite/ld-elf/binutils.exp
@@ -53,7 +53,8 @@ proc binutils_test { prog_name ld_options test } {

     if { ![ld_simple_link $ld tmpdir/$test "$ld_options tmpdir/$test.o"] } {
 	if { [string match "*not supported*" $link_output]
-	     || [string match "*unrecognized option*" $link_output] } {
+	     || [string match "*unrecognized option*" $link_output]
+	     || [string match "*-z relro ignored*" $link_output] } {
 	    unsupported "$ld_options is not supported by this target"
 	} else {
 	    unresolved "$test_name"


-- 
H.J.

  reply	other threads:[~2011-07-14 14:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-13 18:20 Alan Modra
2011-07-14  0:36 ` Ian Lance Taylor
2011-07-14  3:29   ` Alan Modra
2011-07-14  8:06     ` Hans-Peter Nilsson
2011-07-14 11:14       ` Hans-Peter Nilsson
2011-07-14 12:41         ` Alan Modra
2011-07-14 17:16           ` H.J. Lu [this message]
2011-07-14 11:38       ` 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='CAMe9rOo4CR8dW2EF=WC-0GgMm4GVvgQuSUGgNyBSvaVt5w0+Zw@mail.gmail.com' \
    --to=hjl.tools@gmail.com \
    --cc=binutils@sourceware.org \
    --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).