From: Luis Machado <luis.machado@arm.com>
To: Carl Love <cel@linux.ibm.com>, Tom Tromey <tromey@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: Ada compile with -fvar-tracking
Date: Thu, 16 Nov 2023 14:02:11 +0000 [thread overview]
Message-ID: <cc34d88a-2db8-4de2-8bdf-466195ab868f@arm.com> (raw)
In-Reply-To: <fa24824130774c07514686efa55dc19bea4779fa.camel@linux.ibm.com>
On 11/14/23 21:17, Carl Love wrote:
> Tom:
>
> On Tue, 2023-11-14 at 12:40 -0700, Tom Tromey wrote:
>> set flags {debug additional_flags=-cargs additional_flags=-fvar-
>> tracking additional_flags=-margs}
>
> So I put that in as follows:
>
> set flags {debug additional_flags=-cargs additional_flags=-fvar-tracking additional_flags=-margs}
I guess one way to make the above slightly cleaner (debatable) is to append the additional flags on different lines:
set flags {"debug"}
lappend flags "additional_flags=-cargs"
lappend flags "additional_flags=-fvar-tracking"
lappend flags "additional_flags=-margs"
Slightly more verbose, but may make the additional flags more explicit/easier to read.
next prev parent reply other threads:[~2023-11-16 14:02 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 [this message]
2023-11-16 16:11 ` Carl Love
2023-11-16 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=cc34d88a-2db8-4de2-8bdf-466195ab868f@arm.com \
--to=luis.machado@arm.com \
--cc=cel@linux.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@adacore.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).