From: Simon Marchi <simon.marchi@ericsson.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Markus T Metzger <markus.t.metzger@intel.com>,
Simon Marchi <simon.marchi@polymtl.ca>,
Pedro Alves <palves@redhat.com>, GDB <gdb-patches@sourceware.org>
Subject: Re: Ping: [PATCH v2] x86-64: fix ZMM register state tracking
Date: Thu, 08 Nov 2018 16:24:00 -0000 [thread overview]
Message-ID: <6dc9e115-c71e-7146-bf50-4fe646c53e2e@ericsson.com> (raw)
In-Reply-To: <5BE41AE902000078001F993A@prv1-mh.provo.novell.com>
On 2018-11-08 6:15 a.m., Jan Beulich wrote:
> I'm afraid there's more broken here than just this one test.
> Log file attached. I hope you can make sense of it.
>
>> $ make check TESTS="gdb.arch/i386-avx512.exp" RUNTESTFLAGS="--target_board=native-extended-gdbserver"
>
> This produces effectively the same (bad) results.
Thanks I opened:
https://sourceware.org/bugzilla/show_bug.cgi?id=23873
Simon
prev parent reply other threads:[~2018-11-08 16:24 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-05 13:23 [PATCH] " Jan Beulich
2018-09-07 23:13 ` Simon Marchi
2018-09-10 6:25 ` Jan Beulich
2018-09-10 13:01 ` Simon Marchi
2018-09-18 13:38 ` Jan Beulich
2018-09-25 3:29 ` Simon Marchi
2018-09-25 15:04 ` Jan Beulich
2018-10-02 19:20 ` Simon Marchi
2018-10-03 14:30 ` Jan Beulich
2018-10-03 14:41 ` Simon Marchi
2018-09-11 10:34 ` Pedro Alves
2018-09-11 11:34 ` Jan Beulich
2018-09-24 17:19 ` Metzger, Markus T
2018-09-25 7:47 ` Jan Beulich
2018-10-10 15:12 ` [PATCH v2] " Jan Beulich
2018-10-29 10:31 ` Ping: " Jan Beulich
[not found] ` <8bafd220c79c3936de8ce3d6421a9c01@polymtl.ca>
2018-11-07 9:07 ` Metzger, Markus T
2018-11-07 9:12 ` Jan Beulich
2018-11-07 13:18 ` Metzger, Markus T
2018-11-07 13:25 ` Jan Beulich
2018-11-07 14:18 ` Simon Marchi
[not found] ` <5BE41AE902000078001F993A@prv1-mh.provo.novell.com>
2018-11-08 16:24 ` Simon Marchi [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=6dc9e115-c71e-7146-bf50-4fe646c53e2e@ericsson.com \
--to=simon.marchi@ericsson.com \
--cc=JBeulich@suse.com \
--cc=gdb-patches@sourceware.org \
--cc=markus.t.metzger@intel.com \
--cc=palves@redhat.com \
--cc=simon.marchi@polymtl.ca \
/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