From: Peter Barada <pbarada@mail.wm.sps.mot.com>
To: zack@codesourcery.com
Cc: gcc@gcc.gnu.org
Subject: Re: PROPOSAL: Policy for obsoleting targets
Date: Fri, 16 May 2003 16:31:00 -0000 [thread overview]
Message-ID: <200305161631.h4GGV7C08992@hyper.wm.sps.mot.com> (raw)
In-Reply-To: <874r3u27sm.fsf@egil.codesourcery.com> (message from Zack Weinberg on Fri, 16 May 2003 09:08:41 -0700)
> At the time GCC version 3.n is released, all targets which have not
> had a successful build and test report posted to gcc-testresults
> for prereleases of minor version n, or releases n-1 and n-2, go on
> the obsoletion list for version n+1. "Successful" means minimum
> useful functionality: it's okay if only the C compiler works.
http://gcc.gnu.org/gcc-3.2/buildstat.html or
http://gcc.gnu.org/ml/gcc-testresults/2003-04/ only shows host
compilers, and no embedded targets(such as ppc-eabi, m68k-elf, etc).
How do we prevent embedded targets(that are know to work fine) from
from being placed on the obsoletion list?
--
Peter Barada Peter.Barada@motorola.com
Wizard 781-852-2768 (direct)
WaveMark Solutions(wholly owned by Motorola) 781-270-0193 (fax)
next prev parent reply other threads:[~2003-05-16 16:31 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-16 16:08 Zack Weinberg
2003-05-16 16:31 ` Peter Barada [this message]
2003-05-16 17:42 ` Joel Sherrill
2003-05-16 18:30 ` DJ Delorie
2003-05-16 19:19 ` E. Weddington
2003-05-16 22:09 ` Joel Sherrill
2003-05-16 20:16 ` Janis Johnson
2003-05-16 22:10 ` Joel Sherrill
2003-05-16 22:51 ` Janis Johnson
2003-05-16 22:25 ` Paul Koning
2003-05-16 22:34 ` Joel Sherrill
2003-05-16 22:56 ` Alexandre Oliva
2003-05-17 0:02 ` Joe Buck
2003-05-18 6:16 ` Daniel Jacobowitz
2003-05-21 16:46 ` Jason Thorpe
2003-05-19 22:51 ` Michael S. Zick
2003-05-19 23:46 ` Dan Kegel
2003-05-20 0:08 ` Joe Buck
2003-05-22 2:31 ` Ben Elliston
2003-05-22 5:42 ` Dan Kegel
2003-05-22 12:22 ` Michael S. Zick
2003-05-19 2:28 ` Peter Barada
2003-05-19 13:20 ` Paul Koning
2003-05-16 16:34 ` Joe Buck
2003-05-16 17:04 ` Joseph S. Myers
2003-05-16 21:12 ` Joe Buck
2003-05-16 21:21 ` Joseph S. Myers
2003-05-21 16:35 ` Jason Thorpe
2003-05-21 22:02 ` Michael S. Zick
2003-05-16 19:29 ` Daniel Jacobowitz
2003-05-16 16:59 ` Jan Vroonhof
2003-05-18 14:22 ` Marc Espie
2003-05-19 18:28 ` Joe Buck
2003-05-21 17:12 ` Jason Thorpe
2003-05-21 17:49 ` Dan Kegel
2003-05-21 5:25 ` Zack Weinberg
2003-05-21 14:01 ` Michael S. Zick
2003-05-21 16:56 ` Dan Kegel
2003-05-19 18:49 Karim Yaghmour
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=200305161631.h4GGV7C08992@hyper.wm.sps.mot.com \
--to=pbarada@mail.wm.sps.mot.com \
--cc=gcc@gcc.gnu.org \
--cc=zack@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).