From: Tom Tromey <tromey@adacore.com>
To: Carl Love <cel@linux.ibm.com>
Cc: Luis Machado <luis.machado@arm.com>,
Tom Tromey <tromey@adacore.com>,
gdb-patches@sourceware.org
Subject: Re: Ada compile with -fvar-tracking
Date: Thu, 16 Nov 2023 14:07:30 -0700 [thread overview]
Message-ID: <87ttpll84t.fsf@tromey.com> (raw)
In-Reply-To: <1be655a8cfef2afbab409a5802a999785e01924b.camel@linux.ibm.com> (Carl Love's message of "Thu, 16 Nov 2023 08:11:31 -0800")
Carl> Tom, for your platform do you have to have all three options or not?
It seems that I don't.
I thought I did need them but I tried your patch just now and it seems fine.
Tom
prev parent reply other threads:[~2023-11-16 21:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-14 19:24 Carl Love
2023-11-14 19:40 ` Tom Tromey
2023-11-14 21:17 ` Carl Love
2023-11-14 22:03 ` Tom Tromey
2023-11-14 22:23 ` Carl Love
2023-11-15 15:04 ` Tom Tromey
2023-11-15 16:42 ` Carl Love
2023-11-15 17:02 ` Tom Tromey
2023-11-15 17:12 ` Carl Love
2023-11-15 17:23 ` Keith Seitz
2023-11-15 17:29 ` Carl Love
2023-11-15 22:59 ` Carl Love
2023-11-16 14:02 ` Luis Machado
2023-11-16 16:11 ` Carl Love
2023-11-16 21:07 ` Tom Tromey [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=87ttpll84t.fsf@tromey.com \
--to=tromey@adacore.com \
--cc=cel@linux.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=luis.machado@arm.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).