From: "Eli Zaretskii" <eliz@is.elta.co.il>
To: mec@shout.net
Cc: msnyder@redhat.com, gdb-patches@sources.redhat.com
Subject: Re: [RFA] nuke CONST_PTR
Date: Wed, 13 Feb 2002 11:43:00 -0000 [thread overview]
Message-ID: <3099-Wed13Feb2002214133+0200-eliz@is.elta.co.il> (raw)
In-Reply-To: <200202131706.g1DH6k124943@duracef.shout.net> (message from Michael Elizabeth Chastain on Wed, 13 Feb 2002 11:06:46 -0600)
> Date: Wed, 13 Feb 2002 11:06:46 -0600
> From: Michael Elizabeth Chastain <mec@shout.net>
>
> ms> OTOH, do we ever build with Microsoft C any more?
> ms> Is there any reason to support it? Cygwin and Djgcc
> ms> are both self-hosting, aren't they?
>
> I don't know about Microsoft C. I do know that I build Cygwin gdb
> using Cygwin gcc. I don't know about djgpp.
Yes, DJGPP is self-hosting. But I don't see how is that relevant
here, since the compiler is GCC, and GCC supports `const' since time
immemoriam.
I also find it hard to believe that MSC doesn't support `const' these
days; and on top of that, as others said, we removed all MSC ifdefs.
So I think the change is safe.
next prev parent reply other threads:[~2002-02-13 19:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-13 9:06 Michael Elizabeth Chastain
2002-02-13 11:43 ` Eli Zaretskii [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-02-13 10:49 Michael Elizabeth Chastain
2002-02-13 6:44 Michael Elizabeth Chastain
2002-02-13 7:19 ` Kevin Buettner
2002-02-13 8:15 ` Michael Snyder
2002-02-13 9:30 ` Andrew Cagney
2002-02-13 10:04 ` Michael Snyder
2002-02-13 10:56 ` Christopher Faylor
2002-02-13 11:05 ` Andrew Cagney
2002-02-13 11:08 ` Christopher Faylor
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=3099-Wed13Feb2002214133+0200-eliz@is.elta.co.il \
--to=eliz@is.elta.co.il \
--cc=gdb-patches@sources.redhat.com \
--cc=mec@shout.net \
--cc=msnyder@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