From: "Duncan" <1i5t5.duncan@cox.net>
To: gentoo-amd64@lists.gentoo.org
Subject: [gentoo-amd64] FW: GCC4 and -ftree-vectorize
Date: Mon, 2 Oct 2006 10:51:41 +0000 (UTC) [thread overview]
Message-ID: <efqqvt$sqh$6@sea.gmane.org> (raw)
-ftree-vectorize just came up on the gentoo-dev list. I've not even
checked the URLs yet, but since it came up here, I thought I'd ask about
it and having gotten a response, here's the gist. (FWIW, I've been
running it experimentally for a bit now. No issues with it have I seen,
but I've not done a full emerge --emptytree system/world yet.) I'll
probably have a bit more to say about it after checking the tinyurls,
which at this point I don't even know where they go yet, let alone their
content.
<quote from Ryan Hill>
Duncan wrote:
> Could you point me at some info on this one (-ftree-vectorize)? It came
> up on the amd64 list a week or so ago[]
http://tinyurl.com/l75we
They've fixed quite a few of the ICE's since last I looked, though there's
more than a couple that went in after 4.1.1. 4.2 is a little better, but
I'm having enough trouble getting it to build things properly _without_
using any fancy flags right now. ;p
See http://tinyurl.com/rt3aa for some real-world examples.
> Or does the problem not necessarily apply to amd64?
I'd say that there's more ICE's on i686-pc-linux-gnu than
x86_64-*-linux-gnu, but there's still enough. Luckily Halcy0n was really
good for reducing testcases and pushing them upstream, so a lot of these
issues got fixed at the source.
<end of quote from Ryan>
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
--
gentoo-amd64@gentoo.org mailing list
next reply other threads:[~2006-10-02 10:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-02 10:51 Duncan [this message]
2006-10-02 10:55 ` [gentoo-amd64] Re: FW: GCC4 and -ftree-vectorize Duncan
2006-10-02 17:49 ` Duncan
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='efqqvt$sqh$6@sea.gmane.org' \
--to=1i5t5.duncan@cox.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