From: Alan Modra <amodra@gmail.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: "H.J. Lu" <hjl.tools@gmail.com>, Binutils <binutils@sourceware.org>
Subject: Re: gas: elf/bad-group testcase
Date: Fri, 6 May 2022 10:35:10 +0930 [thread overview]
Message-ID: <YnR0RqbIVPW+8DI/@squeak.grove.modra.org> (raw)
In-Reply-To: <ab9a7fef-af44-5e67-e29f-e3fd0dfa715a@suse.com>
On Thu, May 05, 2022 at 01:07:48PM +0200, Jan Beulich wrote:
> On 05.05.2022 12:48, Alan Modra wrote:
> > On Thu, May 05, 2022 at 10:48:47AM +0200, Jan Beulich wrote:
> >> Hello,
> >>
> >> I'm trying to understand what this testcase is actually testing.
> >
> > https://sourceware.org/pipermail/binutils/2011-August/073809.html
>
> Thanks. I read this to mean it's entirely uninteresting what kind of
> error there was.
Yes. I guess all we are really interested in is not getting a gas
segfault.
--
Alan Modra
Australia Development Lab, IBM
prev parent reply other threads:[~2022-05-06 1:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-05 8:48 Jan Beulich
2022-05-05 10:48 ` Alan Modra
2022-05-05 11:07 ` Jan Beulich
2022-05-06 1:05 ` Alan Modra [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=YnR0RqbIVPW+8DI/@squeak.grove.modra.org \
--to=amodra@gmail.com \
--cc=binutils@sourceware.org \
--cc=hjl.tools@gmail.com \
--cc=jbeulich@suse.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).