http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54741
Bug #: 54741
Summary: GCC 4.4, 4.5, 4.6 4.7 (probably 4.8) Generates
un-usable code on AVX supported CPUs (FreeBSD)
Classification: Unclassified
Product: gcc
Version: 4.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54741
--- Comment #2 from M.S. Babaei 2012-09-29
05:43:13 UTC ---
(In reply to comment #1)
> What is the instruction it is causing an illegal instruction signal?
> Run the resulting program using gdb to find out.
As I mentiond above running t
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54741
--- Comment #8 from M.S. Babaei 2012-10-02
07:14:32 UTC ---
(In reply to comment #3)
> use disassemble from inside gdb and look for the faulting instruction.
Sorry I'm not very familiar with GDB, but I assume you need this:
(gdb) di
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54741
--- Comment #9 from M.S. Babaei 2012-10-02
07:18:23 UTC ---
(In reply to comment #7)
> Created attachment 28312 [details]
> A patch with fixed ChangeLog
Now I'm at work. I'll try your patch to build GCC and post later.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54741
--- Comment #11 from M.S. Babaei 2012-10-02
16:58:57 UTC ---
Well well, something happened here!! This bug does not affect me anymore; Now
with or without your patch the above example code works just fine! I even tried
crypto++ which I had
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54741
--- Comment #12 from M.S. Babaei 2012-10-02
17:00:28 UTC ---
Created attachment 28327
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=28327
After applying patch - gcc4.7
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54905
Bug #: 54905
Summary: invalid use of qualified-name 'std::cout'
Classification: Unclassified
Product: gcc
Version: 4.6.4
Status: UNCONFIRMED
Severity: blocker
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29834
--- Comment #6 from M.S. Babaei ---
Hi,
I'm wondering if this bug is ever going to be fixed?
Unfortunately I don't know C and do not understand how inner parts of GCC
works. But, it's mid 2013 and the bug first appeared on late 2006, with anothe
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29834
--- Comment #8 from M.S. Babaei ---
(In reply to Jonathan Wakely from comment #7)
> You can use list-initialization to workaround it:
>
> Doh{x}, ++x;
Thanks for the reply. Yeah, it did the trick for GCC 4.4+. And, I've never
thought of that.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29834
--- Comment #11 from M.S. Babaei ---
(In reply to James Kanze from comment #9)
> Re using the init list syntax: it won't work if you have to be compatible
> with other compilers (like Sun CC). Using something like (Doh (x)), ++x
> seems to be the
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29834
--- Comment #12 from M.S. Babaei ---
(In reply to Manuel López-Ibáñez from comment #10)
> (In reply to M.S. Babaei from comment #8)
> > But this is a bug, and I see no reason why it hasn't been fixed anyway.
>
> I see plenty of reasons: It is a o
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29834
--- Comment #13 from M.S. Babaei ---
(In reply to James Kanze from comment #9)
> Re using the init list syntax: it won't work if you have to be compatible
> with other compilers (like Sun CC). Using something like (Doh (x)), ++x
> seems to be the
12 matches
Mail list logo
