1 |
Duncan wrote: |
2 |
|
3 |
> Could you point me at some info on this one (-ftree-vectorize)? It came |
4 |
> up on the amd64 list a week or so ago, when someone asked what I thought |
5 |
> of it and why I didn't have it in my cflags (which I had just explained). |
6 |
> I said I didn't know enough about it to make a case either way, and as |
7 |
> such, didn't choose to use it. However, after a bit of discussion, I |
8 |
> decided to add it to my cflags on a very experimental basis. I haven't |
9 |
> experienced any issues with it, but then I haven't done any major |
10 |
> compiling since then either, only the routine updates. |
11 |
|
12 |
http://tinyurl.com/l75we |
13 |
|
14 |
They've fixed quite a few of the ICE's since last I looked, though |
15 |
there's more than a couple that went in after 4.1.1. 4.2 is a little |
16 |
better, but I'm having enough trouble getting it to build things |
17 |
properly _without_ using any fancy flags right now. ;p |
18 |
|
19 |
See http://tinyurl.com/rt3aa for some real-world examples. |
20 |
|
21 |
> Or does the problem not necessarily apply to amd64? Even knowing that |
22 |
> would be useful. I simply don't know anything much at all about it, beyond |
23 |
> a generally vague idea that it means using mmx/sse/whatever vector |
24 |
> instructions to parallelize loops. |
25 |
|
26 |
I'd say that there's more ICE's on i686-pc-linux-gnu than |
27 |
x86_64-*-linux-gnu, but there's still enough. Luckily Halcy0n was |
28 |
really good for reducing testcases and pushing them upstream, so a lot |
29 |
of these issues got fixed at the source. |
30 |
|
31 |
--de. |