public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Martin Michlmayr <tbm@cyrius.com>
To: binutils@sourceware.org
Subject: Test suite results for alphaev68-unknown-linux-gnu (2.16.93)
Date: Wed, 17 May 2006 23:29:00 -0000	[thread overview]
Message-ID: <20060517220321.GA13581@deprecation.cyrius.com> (raw)

Test Run By tbm on Wed May 17 21:30:46 2006
Native configuration is alphaev68-unknown-linux-gnu

		=== binutils tests ===

Schedule of variations:
    unix

		=== binutils Summary ===

# of expected passes		35

		=== gas tests ===

Schedule of variations:
    unix

		=== gas Summary ===

# of expected passes		106
# of expected failures		1

		=== ld tests ===

Schedule of variations:
    unix

FAIL: TLS -fpic -shared [?]
FAIL: TLS -fpic and -fno-pic exec [?]
FAIL: TLS -fpic and -fno-pic exec -relax [?]
FAIL: ld-elf/64ksec
FAIL: vers24a [?]
FAIL: vers24b [?]
FAIL: vers24c [?]
FAIL: vers30
FAIL: vers31

		=== ld Summary ===

# of expected passes		217
# of unexpected failures	9
# of expected failures		32

Errors:

Running /home/tbm/src/binutils-2.16.93/ld/testsuite/ld-elf/sec64k.exp ...
failed with: <tmpdir/dump0.o: In function `foo_1':
(.foo.1+0x0): relocation truncated to fit: REFLONG against symbol `foo_0' defined in .text section in tmpdir/dump0.o
tmpdir/dump0.o: In function `bar_1':
(.foo.1+0x4): relocation truncated to fit: REFLONG against `.foo.1'
tmpdir/dump0.o: In function `foo_2':
(.foo.2+0x0): relocation truncated to fit: REFLONG against symbol `foo_1' defined in .foo.1 section in tmpdir/dump0.o
tmpdir/dump0.o: In function `bar_2':
(.foo.2+0x4): relocation truncated to fit: REFLONG against `.foo.2'
tmpdir/dump0.o: In function `foo_3':
(.foo.3+0x0): relocation truncated to fit: REFLONG against symbol `foo_2' defined in .foo.2 section in tmpdir/dump0.o
tmpdir/dump0.o: In function `bar_3':
(.foo.3+0x4): relocation truncated to fit: REFLONG against `.foo.3'
tmpdir/dump0.o: In function `foo_4':
(.foo.4+0x0): relocation truncated to fit: REFLONG against symbol `foo_3' defined in .foo.3 section in tmpdir/dump0.o
tmpdir/dump0.o: In function `bar_4':
(.foo.4+0x4): relocation truncated to fit: REFLONG against `.foo.4'
tmpdir/dump0.o: In function `foo_5':
(.foo.5+0x0): relocation truncated to fit: REFLONG against symbol `foo_4' defined in .foo.4 section in tmpdir/dump0.o
tmpdir/dump0.o: In function `bar_5':
(.foo.5+0x4): relocation truncated to fit: REFLONG against `.foo.5'
tmpdir/dump0.o: In function `foo_6':
(.foo.6+0x0): additional relocation overflows omitted from the output>, expected: <>
FAIL: ld-elf/64ksec

/home/tbm/src/binutils-2.16.93/ld/../binutils/objdump --dynamic-syms tmpdir/vers30.so | sed -n /VERS/p\;/show/p | sort | uniq  > tmpdir/objdump.out
        tmpdir/objdump.out: 1: 00000000000002c0 g    DF .text   0000000000000004  VERS_30.0   0x80 global
FAIL: vers30

/home/tbm/src/binutils-2.16.93/ld/../binutils/objdump --dynamic-syms tmpdir/vers31.so | sed -n /VERS/p\;/show/p | sort | uniq  > tmpdir/objdump.out
        tmpdir/objdump.out: 1: 0000000000000310 g    DF .text   0000000000000004  VERS_31.0   0x80 _Z1fIA3_icEvPT_T0_
FAIL: vers31

-- 
Martin Michlmayr
http://www.cyrius.com/

             reply	other threads:[~2006-05-17 22:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-17 23:29 Martin Michlmayr [this message]
2006-05-18 21:54 ` Martin Michlmayr

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=20060517220321.GA13581@deprecation.cyrius.com \
    --to=tbm@cyrius.com \
    --cc=binutils@sourceware.org \
    /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).