From: Rainer Orth <ro@TechFak.Uni-Bielefeld.DE>
To: dclarke@blastwave.org
Cc: Eric Botcazou <ebotcazou@adacore.com>,
"Kaveh R. GHAZI" <ghazi@caip.rutgers.edu>,
gcc@gcc.gnu.org
Subject: Re: Updating Primary and Secondary platform list for gcc-4.5 ???
Date: Mon, 09 Nov 2009 16:17:00 -0000 [thread overview]
Message-ID: <19192.16501.947402.858609@komagatake.TechFak.Uni-Bielefeld.DE> (raw)
In-Reply-To: <64133.10.0.66.17.1257781578.squirrel@interact.purplecow.org>
Dennis Clarke writes:
> > Eric Botcazou <ebotcazou@adacore.com> writes:
> >
> >> > I was looking through the gcc-4.5 primary and secondary platform list
> >> > to ensure we have coverage for MPC testing. It occurs to me that some
> >> > of the OS versions are outdated.
> >> >
> >> > I've included the list from the page
> >> > http://gcc.gnu.org/gcc-4.5/criteria.html
> >> >
> >> > Should we update:
> >> >
> >> > 1. solaris2.10 -> 2.11
> >>
> >> Why move to a not-yet-released version?
> >
> > Indeed: while I regularly test on Solaris 11/SPARC at the moment, it's
> > still so much of a moving target that this doesn't make any sense.
>
> The issue may be one of "de facto" vs "defined as being" released.
>
> There is no such thing as a released Solaris revision that responds to
> uname with SunOS5.11 yet. When Sun/Oracle actually releases something AND
> you can buy a support contract for it then you have a valid platform in
> commercial use.
You can get support for the OpenSolaris distribution if you like, yet this
is still very much work in progress, not a stable platform we can rely on.
> Having said that .. I see roughly 30% of all my traffic from SunOS5.11
> users on either Solaris Nevada or OpenSolaris beta releases.
>
> The question should be ... do we in the community end user world see
> SunOS5.11 as being a de facto release? I would say yes.
Certainly not, even if it is widely used (primarily on laptops, I suppose).
> Solaris 10 is the enterprise class commercial grade Solaris release and it
> is staying put for a long long long time yet.
Indeed, and even if we chose sparc-sun-solaris2.10 as the primary platform
doesn't mean that *-*-solaris2.11 doesn't work, quite the contrary: I
regularly test both and try to keep them working.
Rainer
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University
next prev parent reply other threads:[~2009-11-09 16:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-09 15:46 Dennis Clarke
2009-11-09 16:17 ` Rainer Orth [this message]
-- strict thread matches above, loose matches on Subject: below --
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
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
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=19192.16501.947402.858609@komagatake.TechFak.Uni-Bielefeld.DE \
--to=ro@techfak.uni-bielefeld.de \
--cc=dclarke@blastwave.org \
--cc=ebotcazou@adacore.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).