public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sven.c.dack at virginmedia dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/62077] --with-build-config=bootstrap-lto fails
Date: Mon, 18 Aug 2014 15:03:00 -0000	[thread overview]
Message-ID: <bug-62077-4-Cyvs7Qp6SU@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-62077-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62077

--- Comment #56 from Sven C. Dack <sven.c.dack at virginmedia dot com> ---
> I don't see why we need to fix this for the 4.9 or 4.8 branch.  It never
> worked there and another existing workaround is to configure with
> --enable-stage1-checking=release.

One reason is that it is not working in any of the recent stable compilers. 5.0
is not stable yet and said to be release not before next year.

At least one of the stable compilers should be able to bootstrap itself with
LTO, because it is one of the primary features in its latest development. It
just looks bad when it fails and will discourage people from adopting it. You
do want GCC users to make use of all its features. Why else put them in there
in the first place, or just make them wait, when it is easy to fix?


  parent reply	other threads:[~2014-08-18 15:03 UTC|newest]

Thread overview: 60+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-09 20:55 [Bug bootstrap/62077] New: --with-build-config=bootstrap-lto fails, sven.c.dack at virginmedia dot com
2014-08-10 15:41 ` [Bug bootstrap/62077] " sven.c.dack at virginmedia dot com
2014-08-10 15:46 ` sven.c.dack at virginmedia dot com
2014-08-11  8:51 ` rguenth at gcc dot gnu.org
2014-08-11 10:07 ` rguenth at gcc dot gnu.org
2014-08-11 10:19 ` venkataramanan.kumar at amd dot com
2014-08-12  7:24 ` sven.c.dack at virginmedia dot com
2014-08-12  7:47 ` sven.c.dack at virginmedia dot com
2014-08-12  8:03 ` pinskia at gcc dot gnu.org
2014-08-12  8:10 ` rguenther at suse dot de
2014-08-12  8:23 ` venkataramanan.kumar at amd dot com
2014-08-12  9:20 ` rguenth at gcc dot gnu.org
2014-08-12 10:52 ` venkataramanan.kumar at amd dot com
2014-08-12 11:07 ` sven.c.dack at virginmedia dot com
2014-08-12 12:51 ` rguenth at gcc dot gnu.org
2014-08-13  8:06 ` [Bug bootstrap/62077] --with-build-config=bootstrap-lto fails sven.c.dack at virginmedia dot com
2014-08-13  8:18 ` sven.c.dack at virginmedia dot com
2014-08-13  9:25 ` rguenth at gcc dot gnu.org
2014-08-13  9:57 ` rguenth at gcc dot gnu.org
2014-08-13 10:00 ` venkataramanan.kumar at amd dot com
2014-08-13 11:05 ` rguenth at gcc dot gnu.org
2014-08-13 11:12 ` rguenth at gcc dot gnu.org
2014-08-13 11:21 ` rguenth at gcc dot gnu.org
2014-08-13 12:34 ` rguenth at gcc dot gnu.org
2014-08-13 13:51 ` rguenth at gcc dot gnu.org
2014-08-13 14:02 ` sven.c.dack at virginmedia dot com
2014-08-13 15:09 ` venkataramanan.kumar at amd dot com
2014-08-13 19:43 ` venkataramanan.kumar at amd dot com
2014-08-14  7:26 ` venkataramanan.kumar at amd dot com
2014-08-14  8:45 ` rguenth at gcc dot gnu.org
2014-08-14 10:30 ` rguenth at gcc dot gnu.org
2014-08-14 12:36 ` venkataramanan.kumar at amd dot com
2014-08-14 17:48 ` sven.c.dack at virginmedia dot com
2014-08-14 22:49 ` sven.c.dack at virginmedia dot com
2014-08-15  5:38 ` sven.c.dack at virginmedia dot com
2014-08-15 10:22 ` sven.c.dack at virginmedia dot com
2014-08-15 10:26 ` rguenther at suse dot de
2014-08-15 10:44 ` trippels at gcc dot gnu.org
2014-08-15 10:56 ` sven.c.dack at virginmedia dot com
2014-08-15 11:37 ` trippels at gcc dot gnu.org
2014-08-15 17:28 ` jason at gcc dot gnu.org
2014-08-15 20:02 ` sven.c.dack at virginmedia dot com
2014-08-15 20:07 ` sven.c.dack at virginmedia dot com
2014-08-17  8:19 ` sven.c.dack at virginmedia dot com
2014-08-17 10:55 ` sven.c.dack at virginmedia dot com
2014-08-17 15:49 ` sven.c.dack at virginmedia dot com
2014-08-18 11:00 ` venkataramanan.kumar at amd dot com
2014-08-18 13:11 ` rguenther at suse dot de
2014-08-18 13:36 ` venkataramanan.kumar at amd dot com
2014-08-18 13:40 ` rguenther at suse dot de
2014-08-18 15:03 ` sven.c.dack at virginmedia dot com [this message]
2015-04-15  7:30 ` rguenth at gcc dot gnu.org
2015-04-15  7:49 ` vekumar at gcc dot gnu.org
2015-04-15  8:12 ` rguenther at suse dot de
2015-04-15  8:34 ` rguenth at gcc dot gnu.org
2015-04-17 11:04 ` jakub at gcc dot gnu.org
2015-04-17 11:28 ` rguenth at gcc dot gnu.org
2015-04-17 17:10 ` jakub at gcc dot gnu.org
2015-04-17 17:11 ` jakub at gcc dot gnu.org
2015-05-06 14:47 ` hjl.tools at gmail dot com

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=bug-62077-4-Cyvs7Qp6SU@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /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).