public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: walt <w41ter@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: A tale of computing thud and blunder
Date: Mon, 19 Dec 2011 04:49:48 -0800	[thread overview]
Message-ID: <jcnbo3$vh3$1@dough.gmane.org> (raw)
In-Reply-To: <jcmmol$km0$1@dough.gmane.org>

On 12/18/2011 10:49 PM, Nikos Chantziaras wrote:

> Just like with any other optimization switch, there can be bugs. If
> Gentoo says it doesn't support graphite, then I'd stay away from it
> because Gentoo devs might not listen to your bug reports if you use
> it.

I've been using gcc with graphite support for about a year or so and
I've had zero problems so far.  (I should also mention that I haven't
measured how much difference it makes, either.)

Very important to notice that *building* gcc with graphite support is
not at all the same as *using* graphite support while compiling.

To actually *use* your graphite support, you must include these CFLAGS
while compiling each package:

-floop-block -floop-strip-mine -floop-interchange

That implies that you can turn off graphite support by removing those
flags and recompiling your buggy package before filing a bug report.
(I did that only once and discovered that it didn't change the bug
at all.)

IIRC, gcc doesn't use those flags while compiling itself, but I could
be mistaken about that.  I'll check again next time I compile gcc.





  parent reply	other threads:[~2011-12-19 12:48 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-17 21:07 [gentoo-user] -march=native is *EXTREMELY* conservative Walter Dnes
2011-12-17 21:53 ` Dale
2011-12-17 21:58 ` [gentoo-user] " Nikos Chantziaras
2011-12-18  1:10   ` Walter Dnes
2011-12-18 10:34     ` Walter Dnes
2011-12-18 10:45       ` Nikos Chantziaras
2011-12-18 18:10         ` Andrea Conti
2011-12-19  0:05         ` [gentoo-user] A tale of computing thud and blunder Walter Dnes
2011-12-19  0:17           ` Dale
2011-12-19  5:41             ` Pandu Poluan
2011-12-19  6:15               ` Dale
2011-12-19  6:49                 ` [gentoo-user] " Nikos Chantziaras
2011-12-19  7:21                   ` Dale
2011-12-19 12:49                   ` walt [this message]
2011-12-19  8:14                 ` [gentoo-user] " Pandu Poluan
2011-12-19 16:37                 ` Paul Hartman
2011-12-18  1:15 ` [gentoo-user] -march=native is *EXTREMELY* conservative Paul Hartman

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='jcnbo3$vh3$1@dough.gmane.org' \
    --to=w41ter@gmail.com \
    --cc=gentoo-user@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