public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@adacore.com>
To: Luis Machado <luis.machado@linaro.org>
Cc: Tom Tromey <tromey@adacore.com>,  gdb-patches@sourceware.org
Subject: Re: [PATCH] Find tailcall frames before inline frames
Date: Thu, 05 Mar 2020 16:56:00 -0000	[thread overview]
Message-ID: <87y2se4u6k.fsf@tromey.com> (raw)
In-Reply-To: <665eda59-ae52-42f4-b3b2-e3a070036ca8@linaro.org> (Luis Machado's	message of "Thu, 5 Mar 2020 07:21:27 -0300")

Luis> This has caused quite a few failures in the following tests for
Luis> aarch64-linux:

Sorry about that.  I will take a look.

Tom

  reply	other threads:[~2020-03-05 16:56 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-20 15:58 Tom Tromey
2020-03-03 21:45 ` Tom Tromey
2020-03-05 10:21   ` Luis Machado
2020-03-05 16:56     ` Tom Tromey [this message]
2020-03-09 17:55     ` Luis Machado
2020-03-12 21:34     ` Tom Tromey
2020-03-13 13:31       ` Luis Machado
2020-03-24 21:24         ` Luis Machado
2020-03-26  1:59           ` Tom Tromey
2020-03-26  2:47             ` Luis Machado
2020-06-18 18:25 ` Andrew Burgess
2020-06-18 21:07   ` Tom Tromey

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=87y2se4u6k.fsf@tromey.com \
    --to=tromey@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=luis.machado@linaro.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).