public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Rainer Orth <ro@TechFak.Uni-Bielefeld.DE>
To: dclarke@blastwave.org
Cc: "Kaveh R. GHAZI" <ghazi@caip.rutgers.edu>, gcc@gcc.gnu.org
Subject: Re: MPC version 0.8 released!
Date: Thu, 05 Nov 2009 17:53:00 -0000	[thread overview]
Message-ID: <19187.4396.283382.768980@komagatake.TechFak.Uni-Bielefeld.DE> (raw)
In-Reply-To: <65299.10.0.66.17.1257441721.squirrel@interact.purplecow.org>

Dennis Clarke writes:

> > "Kaveh R. GHAZI" <ghazi@caip.rutgers.edu> writes:
> >
> >> Please test this version and report back in this thread (not to me
> >> privately) the results of "make check".  Also include your target
> >> triplet,
> >> and the versions of your compiler, gmp and mpfr.
> >
> > target			GCC	GMP	MPFR
> >
> > sparc-sun-solaris2.11	4.1.1	4.2.1	2.3.2
> > i386-pc-solaris2.10	4.1.1	4.2.1	2.3.2
> > mips-sgi-irix6.5	3.4.5	4.3.0	2.3.2
> > alpha-dec-osf4.0f	3.4.4	4.2.1	2.3.2
> >
> > All tests passed everywhere.
> 
> what about sparc-sun-solaris2.10 ? sparc-sun-solaris2.9 and 2.8 ?

I don't have Solaris 8 anymore and no Solaris 9/SPARC system appropriate
for GCC testing.  I don't expect differences between Solaris 10 and 11
here, and frankly, I don't have the cycles (human, not machine) to do all
this testing, so I'm relying on user reports should unexpected problems
occur.

	Rainer

-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University

  reply	other threads:[~2009-11-05 17:53 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-05 17:22 Dennis Clarke
2009-11-05 17:53 ` Rainer Orth [this message]
2009-11-05 20:59 ` Eric Botcazou
  -- strict thread matches above, loose matches on Subject: below --
2009-11-05 18:16 Dennis Clarke
2009-11-05 19:06 ` Kaveh R. Ghazi
2009-11-05 20:29   ` Mikael Pettersson
2009-11-05 15:54 Kaveh R. GHAZI
2009-11-05 17:20 ` Rainer Orth
2009-11-07 17:39   ` Kaveh R. Ghazi
2009-11-07 19:38     ` Gerald Pfeifer
2009-11-08  2:33       ` Gerald Pfeifer
2009-11-07 22:06     ` Dave Korn
2009-11-08  4:40     ` Weddington, Eric
2009-11-09  2:49     ` John David Anglin
2009-11-06 17:13 ` Paolo Carlini
2009-11-06 17:16   ` Richard Guenther
2009-11-06 17:21     ` Paolo Carlini
2009-11-06 17:28   ` Eric Botcazou
2009-11-06 17:38     ` Paolo Carlini
2009-11-06 17:44       ` Eric Botcazou
2009-11-06 17:53         ` Paolo Carlini
2009-11-06 18:16           ` Basile STARYNKEVITCH
2009-11-06 18:37             ` Paolo Carlini
2009-11-06 18:51               ` Richard Guenther
2009-11-06 19:01                 ` Paolo Carlini
2009-11-06 19:04                 ` Paolo Carlini
2009-11-06 19:05                   ` Richard Guenther
2009-11-06 19:07                     ` Paolo Carlini
2009-11-06 19:24                       ` Ian Lance Taylor
2009-11-06 19:33                         ` Paolo Carlini
2009-11-06 21:58                           ` Kaveh R. Ghazi
2009-11-06 23:25                             ` Joseph S. Myers
2009-11-08 10:43 ` Janus Weil
2009-11-08 22:57 ` Kaz Kojima

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=19187.4396.283382.768980@komagatake.TechFak.Uni-Bielefeld.DE \
    --to=ro@techfak.uni-bielefeld.de \
    --cc=dclarke@blastwave.org \
    --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).