From: Paul Koning <paulkoning@comcast.net>
To: Nick Clifton <nickc@redhat.com>
Cc: Stephen Casner <casner@acm.org>, binutils@sourceware.org
Subject: Re: Proposed changes for pdp11 --*magic options
Date: Thu, 9 Apr 2020 19:47:16 -0400 [thread overview]
Message-ID: <AE66075C-0952-43BA-8410-2869BFBCBB4A@comcast.net> (raw)
In-Reply-To: <92659b6c-bc7b-6c60-4865-b60b39e934b0@redhat.com>
> On Apr 7, 2020, at 6:06 AM, Nick Clifton via Binutils <binutils@sourceware.org> wrote:
>
> ...
>> FAIL: ld-scripts/pr18963
>>
>> This one is more complicated. Starting with data.o consisting on only
>> a header and zero-length text, data and bss the linker script creates
>> sections that are each 0x10000 long with symbols corresponding to the
>> section addresses just to test whether addition is commutative using
>> those symbols. The output generated by that linker script is much
>> larger than indicated by the a.out header (and several times larger
>> than the 16-bit address space) making the format invalid, so nm gives
>> an error. Unless the test could be implemented with sections created
>> in the object file and just have the symbols defined in the linker
>> script based on those sections, this test is not supported for
>> pdp11-aout.
>
> This sounds like a reasonable case for an xfail, with a comment along
> the lines of "this test creates a binary that is too big for 16-bit architectures".
The GCC test machinery has notation that lets you mark a test case as not supported on 16 bit machines, so it is simply skilled there. Does binutils have that same mechanism, or something like it?
paul
next prev parent reply other threads:[~2020-04-09 23:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-25 0:14 Stephen Casner
2020-04-03 10:43 ` Nick Clifton
2020-04-03 23:40 ` Stephen Casner
2020-04-04 1:02 ` Stephen Casner
2020-04-07 1:56 ` Stephen Casner
2020-04-07 10:06 ` Nick Clifton
2020-04-09 23:47 ` Paul Koning [this message]
2020-04-10 2:53 ` Stephen Casner
2020-04-14 14:41 ` 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=AE66075C-0952-43BA-8410-2869BFBCBB4A@comcast.net \
--to=paulkoning@comcast.net \
--cc=binutils@sourceware.org \
--cc=casner@acm.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).