From: Tom Tromey <tromey@adacore.com>
To: Simon Marchi <simark@simark.ca>
Cc: Tom Tromey <tromey@adacore.com>, gdb-patches@sourceware.org
Subject: Re: [pushed] Fix typo in sim/ppc/std-config.h
Date: Tue, 21 Apr 2026 13:43:21 -0600 [thread overview]
Message-ID: <87qzo8qeue.fsf@tromey.com> (raw)
In-Reply-To: <be1388aa-12fb-49f1-b200-1cbbee8134da@simark.ca> (Simon Marchi's message of "Tue, 21 Apr 2026 11:08:59 -0400")
>>>>> "Simon" == Simon Marchi <simark@simark.ca> writes:
>> -#ifndef IDECOCE_INLINE
>> +#ifndef IDECODE_INLINE
>> #define IDECODE_INLINE INLINE_LOCALS
>> #endif
Simon> It would be nice to use the gdb include guard checker for the sim
Simon> directory, if the sim maintainers are interested.
Yeah, though despite what the bug says, this is not actually an include
guard and wouldn't be caught by the checker.
Tom
prev parent reply other threads:[~2026-04-21 19:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-21 14:47 Tom Tromey
2026-04-21 15:08 ` Simon Marchi
2026-04-21 19:43 ` Tom Tromey [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=87qzo8qeue.fsf@tromey.com \
--to=tromey@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=simark@simark.ca \
/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