public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: "H . J . Lu" <hjl@lucon.org>
To: binutils@sourceware.cygnus.com
Subject: PATCH: Fix ld bootstrap test for ia64
Date: Sat, 29 Sep 2001 21:25:00 -0000	[thread overview]
Message-ID: <20010929212158.B7417@lucon.org> (raw)

It has been a while for me to check binutils on ia64. It looks like
we have to always rebuild tmpdir/ld2 with tmpdir/ld3 on ia64 like
Linux/mips. Could someone please verify it on ia64?


H.J.
----
2001-09-29  H.J. Lu  <hjl@gnu.org>

	* ld-bootstrap/bootstrap.exp: Always rebuild tmpdir/ld2 with
	tmpdir/ld3 on ia64.

Index: ld-bootstrap/bootstrap.exp
===================================================================
RCS file: /work/cvs/gnu/binutils/ld/testsuite/ld-bootstrap/bootstrap.exp,v
retrieving revision 1.5
diff -u -p -r1.5 bootstrap.exp
--- ld-bootstrap/bootstrap.exp	2001/06/06 22:10:34	1.5
+++ ld-bootstrap/bootstrap.exp	2001/09/30 04:17:20
@@ -104,26 +104,15 @@ foreach flags {"" "strip" "--static" "--
 	continue
     }
 
-    if {"$flags" == "--static"} {
-	if { [istarget ia64-*-elf*]
-	     || [istarget ia64-*-linux*] } {
-	    # On ia64, tmpdir/ld2 != tmpdir/ld3 is normal since they are
-	    # generated by different linkers, tmpdir/ld1 and tmpdir/ld2.
-	    # So we rebuild tmpdir/ld2 with tmpdir/ld3.
-	    if ![ld_link tmpdir/ld3 tmpdir/ld2 "$flags $OFILES $BFDLIB $LIBIBERTY"] {
-		fail $testname
-		continue
-	    }
-	}
-    } else {
-	if { [istarget mips*-*-linux*] } {
-	    # On Linux/mips, tmpdir/ld2 != tmpdir/ld3 is normal since
-	    # they are generated by different linkers, tmpdir/ld1 and
-	    # tmpdir/ld2. So we rebuild tmpdir/ld2 with tmpdir/ld3.
-	    if ![ld_link tmpdir/ld3 tmpdir/ld2 "$flags $OFILES $BFDLIB $LIBIBERTY"] {
-		fail $testname
-		continue
-	    }
+    if { [istarget ia64-*-elf*]
+	 || [istarget ia64-*-linux*]
+	 || [istarget mips*-*-linux*] } {
+	# On ia64 and Linux/mips, tmpdir/ld2 != tmpdir/ld3 is normal
+	# since they are generated by different linkers, tmpdir/ld1
+	# and tmpdir/ld2. So we rebuild tmpdir/ld2 with tmpdir/ld3.
+	if ![ld_link tmpdir/ld3 tmpdir/ld2 "$flags $OFILES $BFDLIB $LIBIBERTY"] {
+	    fail $testname
+	    continue
 	}
     }
 

             reply	other threads:[~2001-09-29 21:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-29 21:25 H . J . Lu [this message]
2001-10-01 17:13 Jim Wilson
2001-10-01 21:43 ` H . J . Lu
2001-10-02 10:11   ` H . J . Lu
2001-10-02 19:13     ` Jim Wilson
2001-10-02 20:00       ` Alan Modra
2001-10-02 21:07         ` Jim Wilson

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=20010929212158.B7417@lucon.org \
    --to=hjl@lucon.org \
    --cc=binutils@sourceware.cygnus.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).