[Bug middle-end/31862] Loop IM and other optimizations harmful for -fopenmp

2007-10-14 Thread tomash dot brechko at gmail dot com
--- Comment #12 from tomash dot brechko at gmail dot com 2007-10-14 14:15 --- I wish I could reopen the bug, but the only option I see is "Leave as UNCONFIRMED". (In reply to comment #9) > So it sounds like you don't any thing about threading programming. Peopl

[Bug target/32301] int __attribute__((vector_size(8))) doesn't use %mm0, produces ugly code

2007-06-12 Thread tomash dot brechko at gmail dot com
--- Comment #2 from tomash dot brechko at gmail dot com 2007-06-12 16:43 --- Sorry, I failed to find two other reports you reference, maybe I'm repeating someone's questions then. Okay, there are reasons not to use %mm0, but why %xmm0 is not used then? Something like f:

[Bug middle-end/32301] New: int __attribute__((vector_size(8))) doesn't use %mm0, produces ugly code

2007-06-12 Thread tomash dot brechko at gmail dot com
Status: UNCONFIRMED Severity: normal Priority: P3 Component: middle-end AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: tomash dot brechko at gmail dot com GCC build triplet: i686-pc-linux-gnu GCC host triplet: i686-pc-linux-gnu GCC t

[Bug c/32273] New: 'restrict' is forgotten after loop unrolling

2007-06-10 Thread tomash dot brechko at gmail dot com
fter loop unrolling Product: gcc Version: 4.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: tomash dot brechko at gmail dot com GCC build tr