public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
* Why so many failures for Linux/sh64?
@ 2003-07-23  5:44 H. J. Lu
  2003-07-23  5:46 ` H. J. Lu
  0 siblings, 1 reply; 5+ messages in thread
From: H. J. Lu @ 2003-07-23  5:44 UTC (permalink / raw)
  To: joern.rennecke; +Cc: binutils

I got many

/export/build/linux/binutils/build-sh64-linux/gas/testsuite/../../binutils/objdump:
Matching formats: elf32-sh64big-linux elf32-sh64
FAIL: SH PIC constructs


H.J.

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: Why so many failures for Linux/sh64?
  2003-07-23  5:44 Why so many failures for Linux/sh64? H. J. Lu
@ 2003-07-23  5:46 ` H. J. Lu
  2003-07-23  6:08   ` kaz Kojima
  2003-07-23 14:19   ` H. J. Lu
  0 siblings, 2 replies; 5+ messages in thread
From: H. J. Lu @ 2003-07-23  5:46 UTC (permalink / raw)
  To: joern.rennecke; +Cc: binutils

On Tue, Jul 22, 2003 at 10:44:10PM -0700, H. J. Lu wrote:
> I got many
> 
> /export/build/linux/binutils/build-sh64-linux/gas/testsuite/../../binutils/objdump:
> Matching formats: elf32-sh64big-linux elf32-sh64
> FAIL: SH PIC constructs
> 

I also got

Running /export/linux/src/binutils/binutils/ld/testsuite/ld-sh/rd-sh.exp ...
/export/build/linux/binutils/build-sh64-linux/ld/../gas/as-new  -little  -o
tmpdir/dump0.o /export/linux/src/binutils/binutils/ld/testsuite/ld-sh/tlslib.s
/export/linux/src/binutils/binutils/ld/testsuite/ld-sh/tlslib.s: Assembler
messages:
/export/linux/src/binutils/binutils/ld/testsuite/ld-sh/tlslib.s:18: Error:
unknown opcode
FAIL: ld-sh/tlsbin-0-dso


H.J.

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: Why so many failures for Linux/sh64?
  2003-07-23  5:46 ` H. J. Lu
@ 2003-07-23  6:08   ` kaz Kojima
  2003-07-23 14:19   ` H. J. Lu
  1 sibling, 0 replies; 5+ messages in thread
From: kaz Kojima @ 2003-07-23  6:08 UTC (permalink / raw)
  To: hjl; +Cc: joern.rennecke, binutils

"H. J. Lu" <hjl@lucon.org> wrote:
> I also got
> 
> Running /export/linux/src/binutils/binutils/ld/testsuite/ld-sh/rd-sh.exp ...
> /export/build/linux/binutils/build-sh64-linux/ld/../gas/as-new  -little  -o
> tmpdir/dump0.o /export/linux/src/binutils/binutils/ld/testsuite/ld-sh/tlslib.s
> /export/linux/src/binutils/binutils/ld/testsuite/ld-sh/tlslib.s: Assembler
> messages:
> /export/linux/src/binutils/binutils/ld/testsuite/ld-sh/tlslib.s:18: Error:
> unknown opcode
> FAIL: ld-sh/tlsbin-0-dso

This is my bad. Does the patch below work for you?

Regards,
	kaz
--
diff -u3prN ORIG/src/ld/testsuite/ld-sh/rd-sh.exp LOCAL/src/ld/testsuite/ld-sh/rd-sh.exp
--- ORIG/src/ld/testsuite/ld-sh/rd-sh.exp	Thu Nov  7 07:28:55 2002
+++ LOCAL/src/ld/testsuite/ld-sh/rd-sh.exp	Mon Jul 21 13:38:45 2003
@@ -29,10 +29,17 @@ if ![istarget sh*-*-*] {
 }
 
 global ASFLAGS
+global LDFLAGS
 set asflags_save "$ASFLAGS"
+set ldflags_save "$LDFLAGS"
 
 if {[istarget sh64*-*-*] || [istarget sh5*-*-*]} then {
     set ASFLAGS "$ASFLAGS -isa=SHcompact"
+    if [istarget sh64*-*-linux*] {
+        set LDFLAGS "$LDFLAGS -mshlelf32_linux"
+    } else {
+        set LDFLAGS "$LDFLAGS -mshlelf32"
+    }
 }
 
 set rd_test_list [lsort [glob -nocomplain $srcdir/$subdir/*.d]]
@@ -52,3 +59,4 @@ foreach shtest $rd_test_list {
     }
 }
 set ASFLAGS "$asflags_save"
+set LDFLAGS "$ldflags_save"

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: Why so many failures for Linux/sh64?
  2003-07-23  5:46 ` H. J. Lu
  2003-07-23  6:08   ` kaz Kojima
@ 2003-07-23 14:19   ` H. J. Lu
  2003-07-23 17:26     ` Joern Rennecke
  1 sibling, 1 reply; 5+ messages in thread
From: H. J. Lu @ 2003-07-23 14:19 UTC (permalink / raw)
  To: joern.rennecke; +Cc: binutils

On Tue, Jul 22, 2003 at 10:46:06PM -0700, H. J. Lu wrote:
> On Tue, Jul 22, 2003 at 10:44:10PM -0700, H. J. Lu wrote:
> > I got many
> > 
> > /export/build/linux/binutils/build-sh64-linux/gas/testsuite/../../binutils/objdump:
> > Matching formats: elf32-sh64big-linux elf32-sh64
> > FAIL: SH PIC constructs
> > 

Why do we need so many elf32/sh64 targets? What are differences
between NetBSD/sh64 and Linux/sh64? Can't we set ELF_MAXPAGESIZE
and elf_symbol_leading_char based on target and share one elf32/sh64
target? They can have a default and we can change them from outside.


H.J.

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: Why so many failures for Linux/sh64?
  2003-07-23 14:19   ` H. J. Lu
@ 2003-07-23 17:26     ` Joern Rennecke
  0 siblings, 0 replies; 5+ messages in thread
From: Joern Rennecke @ 2003-07-23 17:26 UTC (permalink / raw)
  To: H. J. Lu; +Cc: joern.rennecke, binutils, Jason Thorpe

> > On Tue, Jul 22, 2003 at 10:44:10PM -0700, H. J. Lu wrote:
> > > I got many
> > > 
> > > /export/build/linux/binutils/build-sh64-linux/gas/testsuite/../../binutils/objdump:
> > > Matching formats: elf32-sh64big-linux elf32-sh64
> > > FAIL: SH PIC constructs
> > > 
> 
> Why do we need so many elf32/sh64 targets? What are differences
> between NetBSD/sh64 and Linux/sh64? Can't we set ELF_MAXPAGESIZE
> and elf_symbol_leading_char based on target and share one elf32/sh64
> target? They can have a default and we can change them from outside.

I don't know of any particular reason.  Jason, do you?

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2003-07-23 17:26 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-07-23  5:44 Why so many failures for Linux/sh64? H. J. Lu
2003-07-23  5:46 ` H. J. Lu
2003-07-23  6:08   ` kaz Kojima
2003-07-23 14:19   ` H. J. Lu
2003-07-23 17:26     ` Joern Rennecke

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).