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, when someone asked what I thought
of it and why I didn't have it in my cflags (which I had just explained).
I said I didn't know enough about it to make a case either
On Sunday 01 October 2006 18:49, Donnie Berkholz wrote:
I can't give you reasons, but I can tell you it totally broke my x86
system a while back.
-ftree-vectorize on x86 and PowerPC is known to create broken executables
(when it comes to actually create the executable).
I'm using it on AMD64
On Sun, 1 Oct 2006 11:23:37 + (UTC)
Duncan [EMAIL PROTECTED] wrote:
Ryan Hill [EMAIL PROTECTED] posted [EMAIL PROTECTED],
excerpted below, on Sat, 30 Sep 2006 16:37:05 -0600:
If you want flags that just break
stuff with 4.1 you can include -ftree-vectorize.
Could you point me at
On Sat, Sep 30, 2006 at 03:48:53PM -0600, Ryan Hill wrote:
Lionel Bouton wrote:
There are already good resources (http://gentoo-wiki.com/CFLAGS_matrix
was mentioned to me by robbat2) but they may not be advertised enough.
Most of the info on that page is wrong.
The items on there that note
On Sat, Sep 30, 2006 at 04:37:05PM -0600, Ryan Hill wrote:
I thought he wanted flags that broke upgrading between GCC 3.4 and 4.1.
tree-loop-linear wasn't in 3.4. If you want flags that just break
stuff with 4.1 you can include -ftree-vectorize.
Thanks.
The objective here was mainly to