public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Richard Sandiford <rsandifo@redhat.com>
To: binutils@sources.redhat.com
Subject: Re: TLS support for MIPS
Date: Thu, 03 Mar 2005 10:27:00 -0000	[thread overview]
Message-ID: <wvny8d5t47v.fsf@talisman.cambridge.redhat.com> (raw)
In-Reply-To: <20050224190217.GB8974@nevyn.them.org> (Daniel Jacobowitz's message of "Thu, 24 Feb 2005 14:02:17 -0500")

So, I was wondering why the number of gas tests suddenly went down
to 200 ;) and found it was because of:

> Index: binutils/gas/testsuite/gas/mips/mips.exp
> ===================================================================
> --- binutils.orig/gas/testsuite/gas/mips/mips.exp	2005-02-24 13:47:29.486308610 -0500
> +++ binutils/gas/testsuite/gas/mips/mips.exp	2005-02-24 13:48:45.022872138 -0500
> @@ -336,6 +336,11 @@ proc run_list_test_arches { name opts ar
>      foreach arch $arch_list {
>  	run_list_test_arch "$name" "$opts" "$arch"
>      }
> +
> +    if $elf {
> +	run_list_test "tls-ill" "-32"
> +	run_dump_test "tls-o32"
> +    }
>  }

which led to:

---------------------------------------------------------------------------
ERROR: can't read "elf": no such variable
    while executing
"if $elf {
        run_list_test "tls-ill" "-32"
        run_dump_test "tls-o32"
    }"
    (procedure "run_list_test_arches" line 6)
    invoked from within
"run_list_test_arches "branch-misc-2" "-32 -non_shared" [mips_arch_list_matching mips1]"
[...]
---------------------------------------------------------------------------

Why did you add these tests to run_list_test_arches?  Was it just
a merge error?  I was going to install the patch below as obvious
but thought I'd better check first.

Richard


Index: gas/testsuite/gas/mips/mips.exp
===================================================================
RCS file: /cvs/src/src/gas/testsuite/gas/mips/mips.exp,v
retrieving revision 1.102
diff -c -p -F^\([(a-zA-Z0-9_]\|#define\) -r1.102 mips.exp
*** gas/testsuite/gas/mips/mips.exp	2 Mar 2005 21:22:47 -0000	1.102
--- gas/testsuite/gas/mips/mips.exp	3 Mar 2005 10:24:17 -0000
*************** proc run_list_test_arches { name opts ar
*** 336,346 ****
      foreach arch $arch_list {
  	run_list_test_arch "$name" "$opts" "$arch"
      }
- 
-     if $elf {
- 	run_list_test "tls-ill" "-32"
- 	run_dump_test "tls-o32"
-     }
  }
  
  
--- 336,341 ----
*************** if { [istarget mips*-*-*] } then {
*** 690,695 ****
--- 685,693 ----
  	}
  	run_dump_test "elf-consthilo"
  	run_dump_test "expr1"
+ 
+ 	run_list_test "tls-ill" "-32"
+ 	run_dump_test "tls-o32"
      }
  
      if $has_newabi {

  parent reply	other threads:[~2005-03-03 10:27 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-08  9:30 Daniel Jacobowitz
2005-02-08 13:42 ` Alan Modra
2005-02-21 19:23   ` Daniel Jacobowitz
2005-02-22  9:23     ` Alan Modra
2005-02-08 16:26 ` Richard Sandiford
2005-02-08 18:04   ` Daniel Jacobowitz
2005-02-09  0:21     ` Eric Christopher
2005-02-09  7:07     ` Thiemo Seufer
2005-02-09  8:17 ` Thiemo Seufer
2005-02-24 21:56 ` Daniel Jacobowitz
2005-03-02  2:07   ` Thiemo Seufer
2005-03-03 10:27   ` Richard Sandiford [this message]
2005-03-03 14:28     ` Daniel Jacobowitz
2005-03-03 15:03       ` Richard Sandiford

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=wvny8d5t47v.fsf@talisman.cambridge.redhat.com \
    --to=rsandifo@redhat.com \
    --cc=binutils@sources.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).