From: Simon Marchi <simon.marchi@polymtl.ca>
To: gdb-patches@sourceware.org
Cc: Simon Marchi <simon.marchi@efficios.com>
Subject: Re: [PATCH] gdb/testsuite: add "macros" option to gdb_compile
Date: Wed, 6 Apr 2022 21:53:10 -0400 [thread overview]
Message-ID: <85c999ff-b78e-83bc-fffa-98e1d22d4179@polymtl.ca> (raw)
In-Reply-To: <20220406154433.1447101-1-simon.marchi@polymtl.ca>
On 2022-04-06 11:44, Simon Marchi via Gdb-patches wrote:
> From: Simon Marchi <simon.marchi@efficios.com>
>
> Make gdb_compile handle a new "macros" option, which makes it pass the
> appropriate flag to make the compiler include macro information in the
> debug info. This will help simplify tests using macros, reduce
> redundant code, and make it easier to add support for a new compiler.
>
> Right now it only handles clang specially (using -fdebug-macro) and
> falls back to -g3 otherwise (which works for gcc). Other compilers can
> be added as needed.
>
> Change-Id: I50cd6ab1bfbb478c1005486408e214b551364c9b
I integrated this patch in the following series:
https://sourceware.org/pipermail/gdb-patches/2022-April/187550.html
Simon
prev parent reply other threads:[~2022-04-07 1:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-06 15:44 Simon Marchi
2022-04-07 1:53 ` 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=85c999ff-b78e-83bc-fffa-98e1d22d4179@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@efficios.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).