public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
To: Richard Biener <richard.guenther@gmail.com>
Cc: Andrew Roberts <andrewm.roberts@sky.com>,
	       GCC Development <gcc@gcc.gnu.org>,
	       Eric Botcazou <ebotcazou@adacore.com>
Subject: Re: GCC 8.0.0 Status Report (2018-01-15), Trunk in Regression and Documentation fixes only mode
Date: Fri, 26 Jan 2018 14:22:00 -0000	[thread overview]
Message-ID: <yddd11whf90.fsf@CeBiTec.Uni-Bielefeld.DE> (raw)
In-Reply-To: <CAFiYyc0gJqTSsJmLihLozH4_DtJ24OWLm4pRzF2TMnGpcyS2tg@mail.gmail.com>	(Richard Biener's message of "Wed, 17 Jan 2018 09:19:42 +0100")

Hi Richard,

> On Tue, Jan 16, 2018 at 8:20 PM, Andrew Roberts <andrewm.roberts@sky.com> wrote:
>> Boot strap on Darwin x86_64 with llvm now seems broken as of last 8.0.0
>> snapshot, it still is working fine with 7.2.0.
>> I've added bug: 83903
>>
>> x86_64, armv6, armv7, aarch64 all seem fine on linux. I've been building
>> with latest gmp (6.1.2), mpfr (4.0.0) and mpc (1.1.) across all my systems.
>>
>> I observe isl was updated to 0.18 in the download_prerequisites script. Are
>> the other's going to get updated before the 8.0.0 release?
>
> Now that mpc 1.1.0 was released we could update the versions if we get
> sufficient
> "positives" from people testing with newer releases.

I've given it a try with that combo on sparc-sun-solaris2.10 (a primary
target) and i386-pc-solaris2.10 (32 and 64-bit each), with mixed results:

* The gmp reuse test enters an infinite loop on 32-bit sparc.

* The mpfr trint test FAILs on sparcv9.  The failure vanishes with
  --disable-thread-safe.

* Many mpfr tests FAIL on amd64.  Again, they vanish with
  --disable-thread-safe.

I have not yet tried building gcc with those versions yet.

Beside, IMO we need to make sure that trunk and all open branches can be
built with that version set; having to maintain two different sets isn't
an option.

	Rainer

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

  reply	other threads:[~2018-01-26 14:22 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-15  8:21 Richard Biener
2018-01-16 12:50 ` Segher Boessenkool
2018-01-16 17:11   ` Joseph Myers
2018-01-17 17:56   ` Segher Boessenkool
2018-01-16 19:20 ` Andrew Roberts
2018-01-17  8:20   ` Richard Biener
2018-01-26 14:22     ` Rainer Orth [this message]
2018-01-26 18:56       ` Andrew Roberts
2018-01-27 14:38         ` Rainer Orth
2018-02-06  9:22       ` Rainer Orth
2018-02-06  9:49     ` Matthias Klose
2018-02-06 16:14       ` Vincent Lefevre
2018-02-06 16:28         ` Vincent Lefevre
2018-02-06 17:34           ` Joseph Myers
2018-02-06 21:59             ` Vincent Lefevre
2018-02-06 17:32         ` Joseph Myers
2018-02-06 21:48           ` Vincent Lefevre

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=yddd11whf90.fsf@CeBiTec.Uni-Bielefeld.DE \
    --to=ro@cebitec.uni-bielefeld.de \
    --cc=andrewm.roberts@sky.com \
    --cc=ebotcazou@adacore.com \
    --cc=gcc@gcc.gnu.org \
    --cc=richard.guenther@gmail.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).