From: Ian Lance Taylor <iant@google.com>
To: DJ Delorie <dj@redhat.com>
Cc: "Joseph S. Myers" <joseph@codesourcery.com>, gcc@gcc.gnu.org
Subject: Re: 4.4 deprecation proposals
Date: Sun, 15 Jun 2008 22:12:00 -0000 [thread overview]
Message-ID: <m3zlpmmjpf.fsf@google.com> (raw)
In-Reply-To: <200806152158.m5FLwgYH020053@greed.delorie.com> (DJ Delorie's message of "Sun\, 15 Jun 2008 17\:58\:42 -0400")
DJ Delorie <dj@redhat.com> writes:
>> I thought DJGPP was i[34567]86-pc-msdosdjgpp*. I do not think
>> having generic CPU-*-OBJFMT triplets that really refer to a
>> particular OS is a good idea. It's only certain generic triplets
>> I'm proposing to deprecate.
>
> DJGPP is ix86-pc-msdosdjgpp, yes. However, it's based on the
> ix86-coff code (djgpp is coff-based) but not 100% binary compatible
> (mostly due to the dos stub, but also due to preprocessor defines,
> libraries, etc).
>
> Likewise, Cygwin and MinGW are based on the ix86-coff code but with PE
> stubs and support for DLLs and such.
My understanding is that Joseph is just talking about removing the
entries in config.gcc. He is not talking about removing the support
in the code, except perhaps for cases where there is no longer any
entry in config.gcc which requires that support.
Ian
next prev parent reply other threads:[~2008-06-15 22:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-14 18:54 Joseph S. Myers
2008-06-14 19:26 ` Manuel López-Ibáñez
2008-06-15 18:45 ` DJ Delorie
2008-06-15 19:09 ` Joseph S. Myers
2008-06-15 22:01 ` DJ Delorie
2008-06-15 22:12 ` Ian Lance Taylor [this message]
2008-06-15 22:25 ` Joseph S. Myers
2008-06-16 0:06 ` Ben Elliston
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=m3zlpmmjpf.fsf@google.com \
--to=iant@google.com \
--cc=dj@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=joseph@codesourcery.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).