From: Simon Marchi <simark@simark.ca>
To: Bruno Larsen <blarsen@redhat.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH v2] gdb: Fix issue with Clang CLI macros
Date: Mon, 17 Oct 2022 11:28:24 -0400 [thread overview]
Message-ID: <5b4c5930-62a3-21d0-6161-89fb3f6a85ef@simark.ca> (raw)
In-Reply-To: <6e4ad77c-1ef5-0512-d4c5-29947551b0ce@redhat.com>
On 2022-10-17 10:54, Bruno Larsen wrote:
> Hi Simon,
>
> thanks for the review. I've fixed everything else you mentioned, but:
>
> On 17/10/2022 14:32, Simon Marchi wrote:
>>> +#https://github.com/llvm/llvm-project/issues/54506
>>> +
>>> +load_lib dwarf.exp
>>> +
>>> +if {![dwarf2_support]} {
>>> + return 0
>>> +}
>>> +if {![test_compiler_info gcc-*-*]} {
>>> + untested "dwarf assembler needs GCC"
>>> +}
>>> +
>>> +standard_testfile .S
>>> +
>>> +set srcfile macro-source-path.c
>> copy-pasto. Actually, can you use:
>>
>> standard_testfile .c .S
>>
>> and then use $srcfile for the .c, and $srcfile2 (which you can reassign
>> to $asm_file for clarity) for the .S?
>>
> This isn't actually a copy-pasto problem. I am using macro-source-path.c because I only need a .c file with a main function and the label, so I decided to go with a file that was already there. Do you think I should have a .c file anyway, or should I just document this for v3?
I prefer not to share test files randomly between tests, for
consistency, clarity, and so there aren't surprises when you modify a
test.
Simon
next prev parent reply other threads:[~2022-10-17 15:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-17 10:26 Bruno Larsen
2022-10-17 12:32 ` Simon Marchi
2022-10-17 14:54 ` Bruno Larsen
2022-10-17 15:28 ` Simon Marchi [this message]
2022-10-17 13:22 ` Simon Marchi
2022-10-17 13:35 ` Bruno Larsen
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=5b4c5930-62a3-21d0-6161-89fb3f6a85ef@simark.ca \
--to=simark@simark.ca \
--cc=blarsen@redhat.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).