From: Richard Biener <rguenther@suse.de>
To: Eric Botcazou <ebotcazou@adacore.com>
Cc: gcc-patches@gcc.gnu.org, Jakub Jelinek <jakub@redhat.com>
Subject: Re: [PATCH] Fix web/60933
Date: Thu, 24 Apr 2014 09:29:00 -0000 [thread overview]
Message-ID: <alpine.LSU.2.11.1404241117270.18709@zhemvz.fhfr.qr> (raw)
In-Reply-To: <1989200.MzyxOP00E4@polaris>
On Thu, 24 Apr 2014, Eric Botcazou wrote:
> > Meanwhile is does the patch look ok?
>
> No, the current wording is just fine and yours doesn't bring anything (even
> the contrary, since you're listing known problematic versions). This will
> also break http://gcc.gnu.org/install/specific.html#sparc-x-x
Ah, I didn't see that. So the issue here is that the host compiler
miscompiles the in-tree copy? Maybe we should compile host libraries with
-O0 during stage1 (and require recent host GCC for compiling
cross compilers - which we probably do anyway).
It's an issue anyway as soon as we bump the versions downloaded
by contrib/download_prerequesites. What "newer" versions are
affected, btw? Are "very newer" versions fixed maybe?
> I don't see why we should special case GMP, MPFR and MPC here, look at all the
> other dependencies on http://gcc.gnu.org/install/prerequisites.html
>
> And IIUC the real issue is that ftp://gcc.gnu.org/pub/gcc/infrastructure/
> contains obsolete versions.
Hmm, ok. Is the piece referencing contrib/download_prerequesites
and documenting that as the recommended way to setup and do
in-tree builds?
Generally we have conflicting goals - we want to make sure
GCC works with system supplied versions of the libraries
(thus the configure version checks), and we want to specify
versions that work for the in-tree builds (because of the
somewhat awkward setup of the build because of their inter-dependencies
and not doing intermediate installs).
--
Richard Biener <rguenther@suse.de>
SUSE / SUSE Labs
SUSE LINUX Products GmbH - Nuernberg - AG Nuernberg - HRB 16746
GF: Jeff Hawn, Jennifer Guild, Felix Imend"orffer
next prev parent reply other threads:[~2014-04-24 9:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-24 8:18 Richard Biener
2014-04-24 8:22 ` Jakub Jelinek
2014-04-24 8:47 ` Richard Biener
2014-04-24 8:58 ` Jakub Jelinek
2014-04-24 8:33 ` Rainer Orth
2014-04-24 8:39 ` Richard Biener
2014-04-24 9:14 ` Rainer Orth
2014-04-24 9:26 ` Eric Botcazou
2014-04-24 9:29 ` Richard Biener [this message]
2014-04-24 9:38 ` Richard Biener
2014-04-25 9:13 ` Eric Botcazou
2014-04-25 9:51 ` Richard Biener
2014-04-25 10:16 ` Eric Botcazou
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.2.11.1404241117270.18709@zhemvz.fhfr.qr \
--to=rguenther@suse.de \
--cc=ebotcazou@adacore.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.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).