public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: Frank Peters <frank.peters@comcast.net>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] Re: Status of Gcc-5.1.0?
Date: Sat, 23 May 2015 12:48:02 -0400	[thread overview]
Message-ID: <20150523124802.6bd085304b87689bdcb13b4c@comcast.net> (raw)
In-Reply-To: <slrnmm187o.5a4.martin@lounge.imp.fu-berlin.de>

On Sat, 23 May 2015 15:47:04 +0000 (UTC)
Martin Vaeth <martin@mvath.de> wrote:

> 
> My experience is quite the opposite: With graphite, I had
> many random crashes (and seldom also unexplainable compiler
> errors which vanish without graphite).
>

My whole system has been compiled with graphite since its introduction
and I've never seen any problems.

What gcc flags are you using to enable graphite?

Usually, -floop-interchange, -floop-strip-mine, and -floop-block are
enough.

One can go further with -ftree-loop-distribution and -ftree-vectorize
and maybe even others.  AFAIK these extra graphite options may cause
problems.

Regarding LTO, I experienced a severe problem with ghostscipt due to
what I later traced to LTO:

http://bugs.ghostscript.com/show_bug.cgi?id=691768
 
Ever since that time I disabled LTO completely.

Frank Peters



  reply	other threads:[~2015-05-23 16:48 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     ` [gentoo-amd64] " Martin Vaeth
2015-05-23 16:48       ` Frank Peters [this message]
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=20150523124802.6bd085304b87689bdcb13b4c@comcast.net \
    --to=frank.peters@comcast.net \
    --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