public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Gerald Pfeifer <gerald@pfeifer.com>
To: "Kaveh R. GHAZI" <ghazi@caip.rutgers.edu>
Cc: gcc@gcc.gnu.org
Subject: Re: Updating Primary and Secondary platform list for gcc-4.5 ???
Date: Sat, 07 Nov 2009 20:02:00 -0000	[thread overview]
Message-ID: <alpine.LSU.1.99.0911072047350.16522@acrux.dbai.tuwien.ac.at> (raw)
In-Reply-To: <Pine.GSO.4.58.0911071153550.20504@caipclassic.rutgers.edu>

On Sat, 7 Nov 2009, Kaveh R. GHAZI wrote:
> 2.  i386-unknown-freebsd and i686-apple-darwin are generic, but
> config.guess will supply specific version numbers.  What version
> should MPC be shown to work on?  Any one of them would do?

For FreeBSD, I'd specify versions 6.x and above.  Older versions should 
work down to 3.x or 4.x, but it is not worth bothering unless someone is 
into retro computing.  On the contrary, FreeBSD 6.x to some extent, and 
now 7.x primarily and now also 8.x are tested and used regularily.

> 3.  For freebsd and darwin, do we want to include specific version
> numbers for our platform list, or leave them generic?

I think it's fine keeping things as are.  If you prefer, we can also
make it "whatever Gerald or Loren are currently testing" for FreeBSD, 
of course. ;-)

Gerald

  parent reply	other threads:[~2009-11-07 20:02 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-07 16:56 Kaveh R. GHAZI
2009-11-07 17:39 ` Eric Botcazou
2009-11-09 15:34   ` Rainer Orth
2009-11-07 20:02 ` Gerald Pfeifer [this message]
2009-11-09 15:46 Dennis Clarke
2009-11-09 16:17 ` Rainer Orth
2009-11-09 16:50 Dennis Clarke
2009-11-09 16:59 ` Richard Guenther
2009-11-10 17:03   ` Mark Mitchell
2009-11-12 15:00     ` Kaveh R. Ghazi
2009-11-12 15:11       ` David Edelsohn
2009-11-12 15:43         ` Kaveh R. Ghazi
2009-11-24 19:19       ` Richard Sandiford

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=alpine.LSU.1.99.0911072047350.16522@acrux.dbai.tuwien.ac.at \
    --to=gerald@pfeifer.com \
    --cc=gcc@gcc.gnu.org \
    --cc=ghazi@caip.rutgers.edu \
    /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).