public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Jan Beulich <jbeulich@suse.com>
To: "Maciej W. Rozycki" <macro@orcam.me.uk>
Cc: Chenghua Xu <paul.hua.gm@gmail.com>, Binutils <binutils@sourceware.org>
Subject: Re: non-conformant ELF symbol table on MIPS?
Date: Fri, 28 Jul 2023 09:18:32 +0200	[thread overview]
Message-ID: <4798e910-f499-1934-b2a0-b44a1c8dc3e6@suse.com> (raw)
In-Reply-To: <b5cd724f-449e-8e8c-6bae-e93309b1d17c@suse.com>

On 28.07.2023 08:13, Jan Beulich wrote:
> On 27.07.2023 21:28, Maciej W. Rozycki wrote:
>>  Determining whether a MIPS target uses the IRIX emulation is complex, see 
>> e.g. how binutils/testsuite/binutils-all/mips/mips.exp sets `irixemul'.  
>> If you provide me with test case details (input and output), then I may be 
>> able to give you further advice,
> 
> I've provided you the input (see context above), and you'll be able to
> generate the object file from it yourself. But I don't see what this
> would bring, when you already indicate that this is "expected" behavior.
> 
>> but otherwise you may want to mark the 
>> test case with `notarget' or suchlike rather than `xfail', because that's 
>> not a bug with the backend that the symbol ordering varies.
> 
> I'm okay making mips*-*-irix* "notarget", but I don't view this as
> appropriate for e.g. mips*-unknown-elf.

Actually you're right, it needs to be notarget, or else we'd see
"unexpected successes" on the other mips*-*-* targets. I'll refer
to irixemul in the accompanying comment.

Jan


  reply	other threads:[~2023-07-28  7:18 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-27 14:27 Jan Beulich
2023-07-27 19:04 ` Ian Lance Taylor
2023-07-27 19:39   ` Maciej W. Rozycki
2023-07-28  6:16   ` Jan Beulich
2023-07-28 17:11     ` Ian Lance Taylor
2023-07-28 23:58       ` Alan Modra
2023-07-27 19:28 ` Maciej W. Rozycki
2023-07-28  6:13   ` Jan Beulich
2023-07-28  7:18     ` Jan Beulich [this message]
2023-07-28  6:18   ` Jan Beulich
2023-07-28  6:56     ` Maciej W. Rozycki

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=4798e910-f499-1934-b2a0-b44a1c8dc3e6@suse.com \
    --to=jbeulich@suse.com \
    --cc=binutils@sourceware.org \
    --cc=macro@orcam.me.uk \
    --cc=paul.hua.gm@gmail.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).