From: Andrew Volkov <Andrew.Volkov@transas.com>
To: Andreas Schwab <schwab@suse.de>
Cc: gdb-patches@sources.redhat.com
Subject: RE: [patch/rfc] h8300 Change literal reg numbers to REGNUM macros
Date: Wed, 15 May 2002 06:59:00 -0000 [thread overview]
Message-ID: <2E74F312D6980D459F3A05492BA40F8DDA42E7@clue.transas.com> (raw)
Andreas,
I think difference of c99 and ANSI is offtopic here.
Are you have any suggestions about patch?
Andrey
> -----Original Message-----
> From: Andreas Schwab [mailto:schwab@suse.de]
> Sent: Wednesday, May 15, 2002 5:21 PM
> To: Richard.Earnshaw@arm.com
> Cc: gdb-patches@sources.redhat.com
> Subject: Re: [patch/rfc] h8300 Change literal reg numbers to
> REGNUM macros
>
>
> Richard Earnshaw <rearnsha@arm.com> writes:
>
> |> Further, it's general to talk about 'ISO' when referring
> to c99. I said
> |> 'ANSI', which is usually taken to refer to the original standard.
>
> I'm pretty sure that ANSI has adopted C99 too. And C89 (well, C90
> actually) was an ISO standard as well.
>
> |> And anyway, the important point here is that GDB is not
> being coded to c99.
>
> No sweat.
>
> Andreas.
>
> --
> Andreas Schwab, SuSE Labs, schwab@suse.de
> SuSE GmbH, Deutschherrnstr. 15-19, D-90429 Nürnberg
> Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
> "And now for something completely different."
>
next reply other threads:[~2002-05-15 13:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-15 6:59 Andrew Volkov [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-05-15 6:02 Andrew Volkov
2002-05-15 4:32 Andrew Volkov
2002-05-15 5:04 ` Richard Earnshaw
2002-05-15 5:33 ` Andreas Schwab
2002-05-15 5:39 ` Richard Earnshaw
2002-05-15 5:49 ` Andreas Schwab
2002-05-15 5:57 ` Richard Earnshaw
2002-05-15 6:21 ` Andreas Schwab
2002-05-15 9:56 ` Andrew Cagney
2002-05-15 10:05 ` Richard Earnshaw
2002-05-18 14:20 ` Andrew Cagney
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=2E74F312D6980D459F3A05492BA40F8DDA42E7@clue.transas.com \
--to=andrew.volkov@transas.com \
--cc=gdb-patches@sources.redhat.com \
--cc=schwab@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