[Bug c++/35553] New: -fkeep-inline-functions and -O errors out in SSE headers

2008-03-12 Thread gpiez at web dot de
: -fkeep-inline-functions and -O errors out in SSE headers Product: gcc Version: 4.3.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: gpiez at web

[Bug c++/35553] -fkeep-inline-functions and -O errors out in SSE headers

2008-03-12 Thread gpiez at web dot de
--- Comment #1 from gpiez at web dot de 2008-03-12 14:49 --- Created an attachment (id=15303) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=15303&action=view) preprocessed source -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35553

[Bug middle-end/36041] Speed up builtin_popcountll

2012-10-26 Thread gpiez at web dot de
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36041 Gunther Piez changed: What|Removed |Added CC||gpiez at web dot de --- Comment

[Bug c/50168] New: __builtin_ctz() and intrinsics __bsr(), __bsf() generate suboptimal code on x86_64

2011-08-23 Thread gpiez at web dot de
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50168 Bug #: 50168 Summary: __builtin_ctz() and intrinsics __bsr(), __bsf() generate suboptimal code on x86_64 Classification: Unclassified Product: gcc Version: unknown St

[Bug c/50168] __builtin_ctz() and intrinsics __bsr(), __bsf() generate suboptimal code on x86_64

2011-08-23 Thread gpiez at web dot de
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50168 --- Comment #3 from Gunther Piez 2011-08-23 21:54:40 UTC --- On 23.08.2011 19:58, jakub at gcc dot gnu.org wrote: > http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50168 > > Jakub Jelinek changed: > >What|Removed

[Bug c/50168] __builtin_ctz() and intrinsics __bsr(), __bsf() generate suboptimal code on x86_64

2011-08-23 Thread gpiez at web dot de
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50168 --- Comment #4 from Gunther Piez 2011-08-23 22:00:31 UTC --- On 23.08.2011 19:58, jakub at gcc dot gnu.org wrote: > While __builtin_c[lt]z* documentation > says that the result is undefined in that case, I wonder if it would be fine > even if lon

[Bug lto/48246] New: ICE in lto_wpa_write_files

2011-03-22 Thread gpiez at web dot de
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48246 Summary: ICE in lto_wpa_write_files Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: lto AssignedTo: unassig...@gcc.gnu.org

[Bug c++/44500] [C++0x] Bogus narrowing conversion error

2011-03-24 Thread gpiez at web dot de
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44500 --- Comment #18 from Gunther Piez 2011-03-24 11:45:47 UTC --- I have chosen the "recommended" way and added a cast, -fpermissive would allow to many other dubious constructs to pass. Still I think c++ should get rid of implicit integer con

[Bug c++/44500] New: Bogus narrowing conversion error

2010-06-11 Thread gpiez at web dot de
Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: gpiez at web dot de GCC build triplet: x86_64-pc-linux-gnu GCC host triplet: x86_64-pc

[Bug c++/44500] [C++0x] Bogus narrowing conversion error

2010-06-11 Thread gpiez at web dot de
--- Comment #2 from gpiez at web dot de 2010-06-11 11:34 --- Sorry for the unicode mess. The error message is 'error: narrowing conversion of "(((int)y) + 1)" from "int" to "char" inside { }'. The same error happens with a non templated functi

[Bug c++/44500] [C++0x] Bogus narrowing conversion error

2010-06-11 Thread gpiez at web dot de
--- Comment #5 from gpiez at web dot de 2010-06-11 12:09 --- So is it provable that for a "T op T" to be stored in T no narrowing takes place? If the answer for T == char is no and for T == int it is yes this is rather fishy ;-) -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44500

[Bug c++/44500] [C++0x] Bogus narrowing conversion error

2010-06-11 Thread gpiez at web dot de
--- Comment #9 from gpiez at web dot de 2010-06-11 13:27 --- I understand now after the implicit promotion to int of a non constant value the result of the narrowing operation can't be guaranteed to fit in the original type. But I still think it shouldn't give an error,

[Bug c++/44500] [C++0x] Bogus narrowing conversion error

2010-06-12 Thread gpiez at web dot de
--- Comment #13 from gpiez at web dot de 2010-06-12 08:47 --- ... -- gpiez at web dot de changed: What|Removed |Added Status|UNCONFIRMED

[Bug c++/44500] [C++0x] Bogus narrowing conversion error

2010-06-12 Thread gpiez at web dot de
--- Comment #12 from gpiez at web dot de 2010-06-12 08:46 --- I am closing this, as it isn't a gcc bug, as it behaves according to the standard. The bug is in the standard, as it mandates f<1,1> // ok f() // error g() // no error, but undefined behaviu

[Bug c++/44811] New: non controlable bogus warning: right/left shift count is negative

2010-07-04 Thread gpiez at web dot de
Summary: non controlable bogus warning: right/left shift count is negative Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy