From: Pedro Alves <pedro@codesourcery.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: RFA: fix macro expansion bug
Date: Thu, 11 Dec 2008 23:35:00 -0000 [thread overview]
Message-ID: <200812112335.15980.pedro@codesourcery.com> (raw)
In-Reply-To: <m3skoub8g3.fsf@fleche.redhat.com>
On Thursday 11 December 2008 23:25:48, Tom Tromey wrote:
> >>>>> "Pedro" == Pedro Alves <pedro@codesourcery.com> writes:
>
> Pedro> Though, I'm having a bit of trouble convincing myself that the logic to
> Pedro> handle 'pp-number e|E|p|P|. sign' below is 100% sane.
> [...]
> Pedro> It seems macro_is_identifier_nondigit will always eat any of "eEpP",
> Pedro> thus, say, when parsing "1e-" only "1e" will be identified as a pp
> Pedro> number, leaving "+" in the stream. Is this right?
>
> Yeah. Also, "." should not appear in the strchr argument.
>
> Here's a new patch. I'll regression-test it. I don't expect
> problems. Ok if it passes?
Certainly. Thanks.
> >> + "expands to: siginfo. fields.fault.si_addr" \
>
> Pedro> Just curious, as it's just a visual annoyance: do you know where
> Pedro> this space comes from? Do we store the definition with the space for
> Pedro> some reason? We don't get that extra space if the define came
> Pedro> from the code, instead of from a 'macro define'.
>
> Yes, it is a bug in "macro define".
> I'll fix shortly.
>
Thanks!
--
Pedro Alves
next prev parent reply other threads:[~2008-12-11 23:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-11 21:37 Tom Tromey
2008-12-11 23:05 ` Pedro Alves
2008-12-11 23:28 ` Tom Tromey
2008-12-11 23:35 ` Pedro Alves [this message]
2008-12-12 17:07 ` Tom Tromey
2008-12-11 23:31 ` Andreas Schwab
2008-12-11 23:41 ` Tom Tromey
2008-12-11 23:51 ` Pedro Alves
2008-12-11 23:58 ` Tom Tromey
2008-12-12 17:02 ` Tom Tromey
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=200812112335.15980.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@redhat.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