public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Zack Weinberg <zack@codesourcery.com>
To: Nitin Gupta <nitingccmail@yahoo.co.in>
Cc: joel.sherrill@OARcorp.com,  mark@codesourcery.com,
	 gcc@gcc.gnu.org, ngupta@globespanvirata.com
Subject: Re: Target deprecation list
Date: Wed, 23 Apr 2003 16:09:00 -0000	[thread overview]
Message-ID: <87he8pckfl.fsf@egil.codesourcery.com> (raw)
In-Reply-To: <20030423093232.11711.qmail@web8104.in.yahoo.com> (Nitin Gupta's message of "Wed, 23 Apr 2003 10:32:32 +0100 (BST)")

Nitin Gupta <nitingccmail@yahoo.co.in> writes:

> framework due to the new stabs constructs being 
> generated by GCC. To keep sync with lattest GCC 
> releases we are willing to make further changes too, 
> however it won't be feasible at such a short notice. 
> If the community defers its plans  to 'remove' 
> sparclet-aout till GCC 3.4 sparclet users
> too would be able to keep pace with the GCC releases.

Just for the record, *all* the targets we are discussing removing
would be removed from GCC 3.4.  They would be present in GCC 3.3 but
would print a warning message when configured.

zw

  reply	other threads:[~2003-04-23 15:17 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-23 11:55 Nitin Gupta
2003-04-23 16:09 ` Zack Weinberg [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-04-15 10:24 Mark Mitchell
2003-04-15 16:38 ` Michael S. Zick
2003-04-15 21:00 ` Richard Henderson
2003-04-15 21:20   ` Mark Mitchell
2003-04-15 21:47     ` Eric Christopher
2003-04-15 21:43 ` Jeff Epler
2003-04-18  0:14   ` Mark Mitchell
2003-04-18  5:02     ` Jeff Epler
2003-04-18  7:43       ` Mark Mitchell
2003-04-17  8:16 ` Nitin Gupta
2003-04-17 14:01   ` Joel Sherrill

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=87he8pckfl.fsf@egil.codesourcery.com \
    --to=zack@codesourcery.com \
    --cc=gcc@gcc.gnu.org \
    --cc=joel.sherrill@OARcorp.com \
    --cc=mark@codesourcery.com \
    --cc=ngupta@globespanvirata.com \
    --cc=nitingccmail@yahoo.co.in \
    /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).