From: "H.J. Lu" <hjl.tools@gmail.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: Nick Clifton <nickc@redhat.com>, "Cui, Lili" <lili.cui@intel.com>,
Binutils <binutils@sourceware.org>
Subject: Re: New (APX related) assembler testsuite failures
Date: Fri, 19 Jan 2024 06:46:14 -0800 [thread overview]
Message-ID: <CAMe9rOrREJPK2AvAcXBSZLQ73SU6+_OdOSRY65UD__fWcV5NyA@mail.gmail.com> (raw)
In-Reply-To: <aaeabd50-4168-4dfb-87a7-49d946b179ea@suse.com>
On Fri, Jan 19, 2024 at 6:35 AM Jan Beulich <jbeulich@suse.com> wrote:
>
> On 19.01.2024 15:32, Nick Clifton wrote:
> > Hi Cui, Hi Jan,
> >
> > I am seeing two new failures in the gas testsuite:
> >
> > FAIL: x86_64 APX_F EVEX-Promoted insns
> > FAIL: x86_64 APX_F EVEX-Promoted insns (Intel disassembly)
> >
> > These only occur in x86_64 toolchains configured for PE targets
> > (eg x86_64-pc-mingw64) and are happening because these targets
> > pad out code sections in order to allow for section alignment.
> > The testsuite log shows:
> >
> > extra lines in tmpdir/dump.out starting with "^ b8c: 90 nop$"
> > EOF from /work/sources/binutils/upstream/current/gas/testsuite/gas/i386/x86-64-apx-evex-promoted-intel.d
> >
> > Could you take a look and maybe tweak something please ?
>
> I'll deal with that on Monday. I'm surprised though, as I thought I
> had sorted such already. But it must have been some other testcase
> then ...
>
> Jan
I pushed the fix into master branch and backported it to
binutils-2_42-branch.
--
H.J.
next prev parent reply other threads:[~2024-01-19 14:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-19 14:32 Nick Clifton
2024-01-19 14:35 ` Jan Beulich
2024-01-19 14:46 ` H.J. Lu [this message]
2024-01-22 7:45 ` Jan Beulich
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=CAMe9rOrREJPK2AvAcXBSZLQ73SU6+_OdOSRY65UD__fWcV5NyA@mail.gmail.com \
--to=hjl.tools@gmail.com \
--cc=binutils@sourceware.org \
--cc=jbeulich@suse.com \
--cc=lili.cui@intel.com \
--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).