From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Tom Tromey <tom@tromey.com>
Cc: "Leszek Swirski via gdb-patches" <gdb-patches@sourceware.org>,
Leszek Swirski <leszeks@google.com>,
palves@redhat.com
Subject: Re: Regressions on gdb.base/call-{ar,rt}-st.exp on x86_64 native
Date: Wed, 24 Apr 2019 18:02:00 -0000 [thread overview]
Message-ID: <87bm0vgu3a.fsf@redhat.com> (raw)
In-Reply-To: <878svzgul7.fsf@tromey.com> (Tom Tromey's message of "Wed, 24 Apr 2019 11:51:32 -0600")
On Wednesday, April 24 2019, Tom Tromey wrote:
>>>>>> "Sergio" == Sergio Durigan Junior <sergiodj@redhat.com> writes:
>
> Sergio> I found that this patch has caused two testcase regressions when testing
> Sergio> on x86_64 native:
>
> FWIW I sent a patch for this: https://sourceware.org/ml/gdb-patches/2019-04/msg00273.html
>
> It's been a week now so I guess I'll land it.
Ah, great, I hadn't realized. Thanks, Tom!
--
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/
prev parent reply other threads:[~2019-04-24 18:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-14 13:35 [PATCH] [amd64] Fix AMD64 return value ABI in expression evaluation Leszek Swirski via gdb-patches
2019-02-14 14:28 ` Pedro Alves
2019-02-14 15:07 ` Leszek Swirski via gdb-patches
2019-02-14 15:16 ` [PATCH v2] " Leszek Swirski via gdb-patches
2019-02-14 15:18 ` [PATCH v3] " Leszek Swirski via gdb-patches
2019-02-14 15:26 ` Pedro Alves
2019-04-13 16:24 ` Leszek Swirski via gdb-patches
2019-04-16 16:39 ` Tom Tromey
2019-04-16 18:28 ` Tom Tromey
2019-04-24 18:03 ` Tom Tromey
2019-04-17 22:30 ` Tom de Vries
2019-04-18 17:54 ` Tom Tromey
2019-04-24 16:26 ` Regressions on gdb.base/call-{ar,rt}-st.exp on x86_64 native (was: Re: [PATCH v3] [amd64] Fix AMD64 return value ABI in expression evaluation) Sergio Durigan Junior
2019-04-24 17:51 ` Regressions on gdb.base/call-{ar,rt}-st.exp on x86_64 native Tom Tromey
2019-04-24 18:02 ` Sergio Durigan Junior [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=87bm0vgu3a.fsf@redhat.com \
--to=sergiodj@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=leszeks@google.com \
--cc=palves@redhat.com \
--cc=tom@tromey.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