From: Martin Vaeth <martin@mvath.de>
To: gentoo-amd64@lists.gentoo.org
Subject: [gentoo-amd64] Re: Status of Gcc-5.1.0?
Date: Sat, 23 May 2015 15:47:04 +0000 (UTC) [thread overview]
Message-ID: <slrnmm187o.5a4.martin@lounge.imp.fu-berlin.de> (raw)
In-Reply-To: 20150522174107.df90e9ac19e0ce7d2075fdd8@comcast.net
Frank Peters <frank.peters@comcast.net> wrote:
>
> Also, as opposed to link-time optimization (LTO), gcc-graphite is
> stable.
My experience is quite the opposite: With graphite, I had
many random crashes (and seldom also unexplainable compiler
errors which vanish without graphite). The situation did not
improve or got even worse with 4.8 to 4.9.
OTOH, with LTO there are sometimes link errors (unsurprisingly),
but usually it works smoothly.
next prev parent reply other threads:[~2015-05-23 15:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-20 18:55 [gentoo-amd64] Status of Gcc-5.1.0? Frank Peters
2015-05-22 18:35 ` Stefan G. Weichinger
2015-05-22 21:41 ` Frank Peters
2015-05-23 15:47 ` Martin Vaeth [this message]
2015-05-23 16:48 ` [gentoo-amd64] " Frank Peters
2015-05-23 20:36 ` Barry Schwartz
2015-05-25 12:29 ` Martin Vaeth
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=slrnmm187o.5a4.martin@lounge.imp.fu-berlin.de \
--to=martin@mvath.de \
--cc=gentoo-amd64@lists.gentoo.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