From: Borislav Petkov <bp@suse.de>
To: Alan Modra <amodra@gmail.com>
Cc: binutils@sourceware.org
Subject: Re: x86: Do not dump DS/CS segment overrides for branch hints
Date: Wed, 2 Dec 2020 10:44:24 +0100 [thread overview]
Message-ID: <20201202094424.GA25881@zn.tnic> (raw)
In-Reply-To: <20201202071955.GJ22649@bubble.grove.modra.org>
Hi Alan,
On Wed, Dec 02, 2020 at 05:49:55PM +1030, Alan Modra wrote:
> i386-bsd +FAIL: i386 branch
> i386-darwin +FAIL: i386 branch
> i386-darwin +FAIL: x86-64 branch
> i386-msdos +FAIL: i386 branch
> x86_64-w64-mingw32 +FAIL: x86-64 branch
sorry about that ;-\ (and pls bear with me - I'm still learning the
ropes around here).
All "make check-*" runs pass here so I'd guess the fails above happen
when building some other targets. How do you trigger those failures, so
that I can reproduce and add to my patch testing in the future?
Thx.
--
Regards/Gruss,
Boris.
SUSE Software Solutions Germany GmbH, GF: Felix Imendörffer, HRB 36809, AG Nürnberg
next prev parent reply other threads:[~2020-12-02 9:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-02 7:19 Alan Modra
2020-12-02 9:44 ` Borislav Petkov [this message]
2020-12-02 10:45 ` Borislav Petkov
2020-12-02 11:10 ` Borislav Petkov
2020-12-07 14:15 ` Maciej W. Rozycki
2020-12-07 22:16 ` Alan Modra
2020-12-07 22:38 ` Borislav Petkov
2020-12-11 23:12 ` Borislav Petkov
2020-12-13 3:35 ` Alan Modra
2020-12-13 11:56 ` Borislav Petkov
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=20201202094424.GA25881@zn.tnic \
--to=bp@suse.de \
--cc=amodra@gmail.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).