public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Hans-Peter Nilsson <hp@bitrange.com>
To: Stephen Clarke <stephen.clarke@earthling.net>
Cc: "H. J. Lu" <hjl@lucon.org>,  <binutils@sources.redhat.com>
Subject: Re: [Patch] sh64: Fix gas testsuite expected output
Date: Wed, 02 Oct 2002 17:00:00 -0000	[thread overview]
Message-ID: <Pine.BSF.4.44.0210021943060.34969-100000@dair.pair.com> (raw)
In-Reply-To: <002701c26a6a$88281100$6301a8c0@wren>

On Wed, 2 Oct 2002, Stephen Clarke wrote:

While I have your attention, can you please do some official
check regarding the TLS ELF reloc numbers that Kojima-san
proposed?

> From: "H. J. Lu"
> Sent: Wednesday, October 02, 2002 4:08 PM
>
>
> > Is sh64-linux a supported Linux target? If yes, I can add it to my
> > binutils test target. I already test sh-linux, adding sh64-linux won't
> > be a problem.
>
> Not yet ... there's a patch at
> http://sources.redhat.com/ml/binutils/2002-09/msg00048.html
> waiting to be reviewed.

That patch is ok.

> This would need sh64 gas and ld testsuite fixes too, see
> http://sources.redhat.com/ml/binutils/2002-09/msg00049.html

Ok.

> http://sources.redhat.com/ml/binutils/2002-09/msg00050.html

But for one thing (leading to some other changes), the patch is
ok:

Index: ld/testsuite/ld-sh/sh.exp
===================================================================
RCS file: /cvs/src/src/ld/testsuite/ld-sh/sh.exp,v
retrieving revision 1.8
diff -u -c -3 -p -r1.8 sh.exp
*** ld/testsuite/ld-sh/sh.exp   8 Feb 2002 06:49:55 -0000
1.8
--- ld/testsuite/ld-sh/sh.exp   30 Aug 2002 00:51:57 -0000
*************** if ![istarget sh*-*-*] {
*** 25,31 ****
      return
  }

! if [istarget sh64-*-elf] {
      # relaxing not supported on sh64 yet.
      return
  }
--- 25,32 ----
      return
  }

! if { ([istarget sh64-*-elf]
!       || [istarget sh64*-*-linux*])} {
      # relaxing not supported on sh64 yet.
      return
  }

I'd rather you tweak the target specifiers on the tests:
#targets: sh-*-* shl*-*-* shb*-*-*
in each *.d should suffice.

>
> I couldn't miss this opportunity to nag the maintainers could I :-)

Where's Joern these days?  Doesn't he work on SH stuff?

brgds, H-P

  reply	other threads:[~2002-10-03  0:00 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-02 16:00 Stephen Clarke
2002-10-02 16:05 ` Hans-Peter Nilsson
2002-10-02 16:08 ` H. J. Lu
2002-10-02 16:28   ` Stephen Clarke
2002-10-02 17:00     ` Hans-Peter Nilsson [this message]
2002-10-02 17:12       ` Hans-Peter Nilsson
2002-10-09 13:34       ` Stephen Clarke
2002-10-09 21:20         ` Hans-Peter Nilsson
2002-10-11 10:51           ` Stephen Clarke
2002-10-13 22:01             ` Hans-Peter Nilsson
2002-10-02 17:04     ` H. J. Lu
2002-10-14 21:14       ` Stephen Clarke
2002-10-14 21:38         ` H. J. Lu
2002-10-14 22:05           ` Stephen Clarke
2002-10-15 20:16 Stephen Clarke
2002-10-15 20:27 ` H. J. Lu
2002-10-15 21:39   ` Stephen Clarke
2002-10-15 22:32     ` H. J. Lu
2002-10-15 22:54       ` Stephen Clarke
2002-10-15 23:00         ` H. J. Lu
2002-10-15 23:39           ` H. J. Lu
2002-10-16  1:47             ` Alan Modra
2002-10-16  6:16               ` H. J. Lu
2002-10-16  8:03                 ` Alan Modra
2002-10-16  8:14                   ` H. J. Lu
2002-10-16  9:50                   ` Matt Thomas
2002-10-18  1:56                     ` Alan Modra
2002-10-18 10:22                       ` Ulrich Drepper
2002-10-18 10:38                         ` H. J. Lu
2002-10-18 11:21                           ` Jason R Thorpe
2002-10-18 11:27                             ` Jason R Thorpe
2002-10-18 12:33                         ` Hans-Peter Nilsson
2002-10-18 18:04                           ` Alan Modra
2002-10-18 18:46                             ` Hans-Peter Nilsson
2002-10-22  1:44                           ` kaz Kojima
2002-10-15 21:51 ` 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=Pine.BSF.4.44.0210021943060.34969-100000@dair.pair.com \
    --to=hp@bitrange.com \
    --cc=binutils@sources.redhat.com \
    --cc=hjl@lucon.org \
    --cc=stephen.clarke@earthling.net \
    /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).