[Bug target/87455] sse_packed_single_insn_optimal is suboptimal on Zen

2020-01-04 Thread fanael4 at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87455 --- Comment #6 from Fanael --- Any hope of getting this fixed in GCC 10? It should just be a matter of removing Zen[12] from X86_TUNE_SSE_PACKED_SINGLE_INSN_OPTIMAL.

[Bug target/87455] sse_packed_single_insn_optimal is suboptimal on Zen

2018-10-12 Thread fanael4 at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87455 --- Comment #5 from Fanael --- Created attachment 44829 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=44829=edit WIP patch > We already have TARGET_SSE_TYPELESS_STORES for stores, so perhaps we want > something like typeless reg-reg

[Bug target/87455] sse_packed_single_insn_optimal is suboptimal on Zen

2018-09-28 Thread fanael4 at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87455 --- Comment #3 from Fanael --- > May be we should remove xorps generation part. If it were up to me, I'd keep to for BDVER[1234] only, because xorps is still one byte shorted than either xorpd or pxor and is as fast there, and introduce a

[Bug target/87455] sse_packed_single_insn_optimal is suboptimal on Zen

2018-09-27 Thread fanael4 at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87455 --- Comment #1 from Fanael --- Assembly diff between the two: --- /dev/fd/63 2018-09-27 17:59:06.120507763 +0200 +++ /dev/fd/62 2018-09-27 17:59:06.120507763 +0200 @@ -7,21 +7,21 @@ main: .LFB5179: .cfi_startproc - movaps

[Bug target/87455] New: sse_packed_single_insn_optimal is suboptimal on Zen

2018-09-27 Thread fanael4 at gmail dot com
Component: target Assignee: unassigned at gcc dot gnu.org Reporter: fanael4 at gmail dot com Target Milestone: --- GCC by default enables -mtune-ctrl=sse_packed_single_insn_optimal on -mtune=znver1, even though that microarchitecture doesn't like it for the same reason Intel's

[Bug target/66655] [5/6 Regression] miscompilation due to ipa-ra on MinGW

2016-01-21 Thread fanael4 at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66655 Fanael changed: What|Removed |Added CC||fanael4 at gmail dot com --- Comment #16 from

[Bug c++/61465] New: Bogus parameter set but not used warning in constructor initialization list

2014-06-10 Thread fanael4 at gmail dot com
: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: fanael4 at gmail dot com When compiling the following code with C++11 and -Wunused-but-set-parameter on struct Foo { Foo(void* x) : y{static_castchar*(x)} {} char* y

[Bug bootstrap/60830] [4.9 Regression] ICE on bootstrapping on cygwin

2014-05-02 Thread fanael4 at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60830 --- Comment #48 from Fanael fanael4 at gmail dot com --- Is revision 209946 an attempt to fix this?

[Bug libgcc/61003] New: [4.9 Regression] Segfault in __deregister_frame_info_bases when exiting, on i686-mingw32 with dw2 unwinding

2014-04-29 Thread fanael4 at gmail dot com
Status: UNCONFIRMED Severity: critical Priority: P3 Component: libgcc Assignee: unassigned at gcc dot gnu.org Reporter: fanael4 at gmail dot com Target: i686-*-mingw32 When targeting i686-mingw32 all programs compiled with GCC

[Bug libgcc/61003] [4.9 Regression] Segfault in __deregister_frame_info_bases when exiting, on i686-mingw32 with dw2 unwinding

2014-04-29 Thread fanael4 at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=61003 --- Comment #1 from Fanael fanael4 at gmail dot com --- Note: I was compiling with -O2, so the line number may not be very indicative. Should I post a backtrace of -O0?

[Bug libstdc++/59665] New: User code can cause ambiguous references to std in libstdc++

2014-01-03 Thread fanael4 at gmail dot com
Priority: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: fanael4 at gmail dot com The following PURE EVIL but legal code: namespace foo { namespace std {} } using namespace foo; #include algorithm causes the compiler to spew out lots of error

[Bug c++/58924] Non-member invocation of overload of operator when the first argument is a temporary of type std::stringstream

2013-10-30 Thread fanael4 at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58924 Fanael fanael4 at gmail dot com changed: What|Removed |Added CC||fanael4 at gmail dot com

[Bug c++/58924] Non-member invocation of overload of operator when the first argument is a temporary of type std::stringstream

2013-10-30 Thread fanael4 at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58924 --- Comment #2 from Fanael fanael4 at gmail dot com --- Er, 'operator(basic_ostreamcharT, traits os, const charT* x)', without the r-value ref, of course.

[Bug c++/58063] default arguments evaluated twice per call

2013-08-04 Thread fanael4 at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58063 Fanael fanael4 at gmail dot com changed: What|Removed |Added CC||fanael4 at gmail dot com

[Bug target/57293] [4.8/4.9 Regression] not needed frame pointers on IA-32 (performance regression?)

2013-08-04 Thread fanael4 at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57293 --- Comment #4 from Fanael fanael4 at gmail dot com --- (In reply to Vladimir Makarov from comment #1) But I am planning to fix it until end of June. Any progress on this one? Patching GCC to use Satan^H^H^H^H^Hreload is a workaround, but one

[Bug c++/57724] wrong error: returning a value from a constructor

2013-06-26 Thread fanael4 at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57724 Fanael fanael4 at gmail dot com changed: What|Removed |Added CC||fanael4 at gmail dot com

[Bug target/57293] [4.8/4.9 Regression] not needed frame pointers on IA-32 (performance regression?)

2013-05-17 Thread fanael4 at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57293 Fanael fanael4 at gmail dot com changed: What|Removed |Added Target|i686-w64-mingw32|i?86-*-* --- Comment #3

[Bug target/57293] New: [4.8/4.9 Regression] not needed frame pointers on IA-32 (performance regression?)

2013-05-15 Thread fanael4 at gmail dot com
Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: fanael4 at gmail dot com About a week ago GCC started to emit frame pointers even in presence of -fomit-frame-pointer whenever there's a call to a function with a callee

[Bug lto/55493] [4.8 Regression] LTO always ICEs on native i686-mingw32

2013-02-27 Thread fanael4 at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55493 Fanael fanael4 at gmail dot com changed: What|Removed |Added Status|WAITING |RESOLVED

[Bug lto/55493] [4.8 Regression] LTO always ICEs on i686-mingw32

2013-01-18 Thread fanael4 at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55493 Fanael fanael4 at gmail dot com changed: What|Removed |Added Status|RESOLVED|REOPENED

[Bug lto/55493] [4.8 Regression] LTO always ICEs on i686-mingw32

2013-01-16 Thread fanael4 at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55493 --- Comment #6 from Fanael fanael4 at gmail dot com 2013-01-16 18:15:25 UTC --- Oh right. Works for me too. I should've tested it more thoroughly first. Sorry for bothering you guys.

[Bug lto/55493] [4.8 Regression] LTO always ICEs on i686-mingw32

2013-01-09 Thread fanael4 at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55493 --- Comment #3 from Fanael fanael4 at gmail dot com 2013-01-09 14:19:09 UTC --- (In reply to comment #2) Are you sure that you do not somehow pull in LTO objects from older releases? Yes, happens even with -nostdlib, even on builds

[Bug lto/55493] New: [4.8 Regression] LTO always ICEs on i686-w64-mingw32

2012-11-27 Thread fanael4 at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55493 Bug #: 55493 Summary: [4.8 Regression] LTO always ICEs on i686-w64-mingw32 Classification: Unclassified Product: gcc Version: 4.8.0 Status: UNCONFIRMED Severity:

[Bug lto/55493] [4.8 Regression] LTO always ICEs on i686-w64-mingw32

2012-11-27 Thread fanael4 at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55493 --- Comment #1 from fanael4 at gmail dot com 2012-11-27 16:25:58 UTC --- Forgot to mention: 4.7.2 - works 4.8.0 r193777 - fails