From: Nick Clifton <nickc@redhat.com>
To: Andrew STUBBS <andrew.stubbs@st.com>
Cc: binutils@sourceware.org
Subject: Re: [PATCH]: Set little endian flag when linking SH arch tests for little endian multilibs
Date: Mon, 24 Jul 2006 13:55:00 -0000 [thread overview]
Message-ID: <44C4D165.7000900@redhat.com> (raw)
In-Reply-To: <44C4A412.90200@st.com>
Hi Andrew,
>>> For reasons I do not understand I found that if I included the above
>>> part of the patch to arch.exp I ended up with *more* SH linker
>>> testsuite failures (for little endian multilibs) than without it.
>> Hmmm, did you use both parts of the patch?
Well I used my version of it, but essentially yes.
> Well, I did the tests with and without my two-part patch.
>
> Without:
> === ld Summary for sh-sim/-ml ===
>
> # of expected passes 133
> # of unexpected failures 357
> # of expected failures 1
> # of unresolved testcases 14
> # of untested testcases 378
> With:
> === ld Summary for sh-sim/-ml ===
>
> # of expected passes 797
> # of unexpected failures 80
> # of expected failures 1
> # of untested testcases 21
> So that's quite considerably better. I have not looked at what causes
> the 65 additional failures in little endian,
This is where I thought that the second part of the patch was giving
problems. Without it I get only 33 unexpected failures for the "-ml"
multilib... I suspect however that this was connected to the fact that
some architecture variants do not support little endian and the tests do
not current make allowances for this.
Anyway thanks very much for looking into this, and I am sure that at
some date somebody will finish off the work and fix the remaining failures.
Cheers
Nick
prev parent reply other threads:[~2006-07-24 13:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-21 9:55 Nick Clifton
2006-07-21 13:25 ` Andrew STUBBS
2006-07-23 14:25 ` Nick Clifton
2006-07-24 8:32 ` Andrew STUBBS
2006-07-24 10:42 ` Andrew STUBBS
2006-07-24 13:55 ` Nick Clifton [this message]
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=44C4D165.7000900@redhat.com \
--to=nickc@redhat.com \
--cc=andrew.stubbs@st.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).