From: "Jan Beulich" <JBeulich@novell.com>
To: "Nick Clifton" <nickc@redhat.com>
Cc: <binutils@sourceware.org>
Subject: Re: [PATCH] improve equate handling
Date: Wed, 12 Oct 2005 07:35:00 -0000 [thread overview]
Message-ID: <434CD93B.76F0.0078.0@novell.com> (raw)
In-Reply-To: <434BED7A.1020807@redhat.com>
>>>the BFD_RELOC_8 and so fail some of the new tests. I updated the
>
>> I'm surprised about this. I believe my list of targets is pretty
>> complete (it includes arc for example), and I didn't find the
problem
>> because even the reference build (i.e. prior to my changes) for
many
>> targets doesn't succeed. Perhaps, while I used a 64-bit one, you
tested
>> on a 32-bit host? I just verified that the build there fails due to
>> -Werror.
>
>I was using a 32-bit host (or strictly speaking a 64-bit machine
running
>in 32-bit emulation mode). I based my comment about some extra
targets
>not support 8-bit relocs on the error messages in the various gas.log
>files. For example the xtensa-elf port complained about BFD_RELOC_8
>being unsupported, and the pdp11-aout port generates an error about an
>unsupported case value (which if you track it down, turns out to be a
>lack of support for 8-bit values).
>
>Still if you feel my additions to the xfail list are wrong then please
>feel free to remove them. Even better would be to fix the offending
>ports so that they pass the new tests.
No, I didn't mean to complain about anything. Rather I wanted to
understand why I missed some things you found. As it turns out, xtensa
wasn't on my list of target to build/check, nor is pdp11.
Jan
next prev parent reply other threads:[~2005-10-12 7:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-30 15:50 Jan Beulich
2005-10-11 11:19 ` Nick Clifton
2005-10-11 12:31 ` Jan Beulich
2005-10-11 15:14 ` Jan Beulich
2005-10-11 16:40 ` Nick Clifton
2005-10-12 7:35 ` Jan Beulich [this message]
2005-10-12 9:07 ` Nick Clifton
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=434CD93B.76F0.0078.0@novell.com \
--to=jbeulich@novell.com \
--cc=binutils@sourceware.org \
--cc=nickc@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).