From: Tom Tromey <tom@tromey.com>
To: Tom de Vries <tdevries@suse.de>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 1/2] [gdb/symtab] Add producer_is_gas
Date: Tue, 31 Oct 2023 13:30:13 -0600 [thread overview]
Message-ID: <87r0lak2t6.fsf@tromey.com> (raw)
In-Reply-To: <20231030081106.29898-1-tdevries@suse.de> (Tom de Vries's message of "Mon, 30 Oct 2023 09:11:05 +0100")
>>>>> "Tom" == Tom de Vries <tdevries@suse.de> writes:
Tom> Add producer_is_gas, a generic way to get the gas version from the
Tom> producer string.
Tom> Tested on x86_64-linux.
Tom> +int
Tom> +producer_is_gas (const char *producer, int *major, int *minor)
I'd suggest a bool return type for new code.
Tom
next prev parent reply other threads:[~2023-10-31 19:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-30 8:11 Tom de Vries
2023-10-30 8:11 ` [PATCH 2/2] [gdb/symtab] Work around gas PR28629 Tom de Vries
2023-10-31 19:31 ` Tom Tromey
2023-11-01 6:43 ` Tom de Vries
2023-11-02 21:04 ` Carl Love
2023-11-03 18:25 ` Tom Tromey
2023-11-05 20:14 ` Tom de Vries
2023-11-06 7:35 ` Tom de Vries
2023-10-31 19:30 ` Tom Tromey [this message]
2023-11-01 6:39 ` [PATCH 1/2] [gdb/symtab] Add producer_is_gas Tom de Vries
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=87r0lak2t6.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=tdevries@suse.de \
/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).