From: Tom Tromey <tom@tromey.com>
To: "Tomar, Sourabh Singh via Gdb-patches" <gdb-patches@sourceware.org>
Cc: "Tomar, Sourabh Singh" <SourabhSingh.Tomar@amd.com>,
"George, Jini Susan" <JiniSusan.George@amd.com>,
"Achra, Nitika" <Nitika.Achra@amd.com>,
"Sharma, Alok Kumar" <AlokKumar.Sharma@amd.com>,
"E, Nagajyothi" <Nagajyothi.E@amd.com>,
"Kumar N, Bhuvanendra" <Bhuvanendra.KumarN@amd.com>
Subject: Re: [PATCH] [gdb.base] Enable macro test for clang compiler
Date: Wed, 10 Mar 2021 12:10:19 -0700 [thread overview]
Message-ID: <878s6u965g.fsf@tromey.com> (raw)
In-Reply-To: <MW2PR12MB247400C9B2479BA21262B6C39D919@MW2PR12MB2474.namprd12.prod.outlook.com> (Sourabh Singh via Gdb-patches Tomar's message of "Wed, 10 Mar 2021 15:45:54 +0000")
>>>>> ">" == Tomar, Sourabh Singh via Gdb-patches <gdb-patches@sourceware.org> writes:
>> Requesting review on this patch, Please have a look.
Thank you.
>> * gdb.base/macscp.exp: Append -g3 to additional_flags for clang.
>> +2021-03-10 Sourabh Singh Tomar <SourabhSingh.Tomar@amd.com>
>> +
>> + * gdb.base/macscp.exp: Remove -g3 from additional_flags and
>> + append -fdebug-macro to additional_flags for clang.
>> +
This diff seems a little weird - there are newer ChangeLog entries
visible.
Maybe you have other patches after this one ... that's fine, but it's
good usually to make a new branch when submitting to avoid this kind of
thing.
>> get_compiler_info
>> -if { [test_compiler_info "gcc-*"] || [test_compiler_info "clang-*"] } {
>> +if { [test_compiler_info "gcc-*"] } {
>> lappend options additional_flags=-g3
>> }
>> +get_compiler_info
>> +if { [test_compiler_info "clang-*"] } {
>> + lappend options additional_flags=-fdebug-macro
>> +}
I suspect the second call to get_compiler_info isn't needed, and this
could be phrased as "else if { ... clang ... }".
Tom
next prev parent reply other threads:[~2021-03-10 19:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-10 15:45 Tomar, Sourabh Singh
2021-03-10 19:10 ` Tom Tromey [this message]
2021-03-12 5:38 ` Tomar, Sourabh Singh
2021-03-12 14:12 ` Tom Tromey
2021-03-15 5:47 ` Tomar, Sourabh Singh
2021-03-15 5:51 ` Tomar, Sourabh Singh
2021-03-15 19:40 ` Tom Tromey
2021-03-16 5:14 ` Tomar, Sourabh Singh
2021-03-19 5:43 ` Tomar, Sourabh Singh
2021-04-26 19:38 ` Simon Marchi
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=878s6u965g.fsf@tromey.com \
--to=tom@tromey.com \
--cc=AlokKumar.Sharma@amd.com \
--cc=Bhuvanendra.KumarN@amd.com \
--cc=JiniSusan.George@amd.com \
--cc=Nagajyothi.E@amd.com \
--cc=Nitika.Achra@amd.com \
--cc=SourabhSingh.Tomar@amd.com \
--cc=gdb-patches@sourceware.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).