[Bug tree-optimization/104603] [10/11/12 Regression] wrong detection of -Warray-bounds for interesting tail resusive case

2022-02-18 Thread herumi at nifty dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104603 --- Comment #7 from herumi --- Created attachment 52478 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52478&action=edit an original code The array-bounds.zip file is a little stripped original issue. array-bounds% g++-11.2 -O2 -c a.cpp

[Bug tree-optimization/104603] [10/11/12 Regression] wrong detection of -Warray-bounds for interesting tail resusive case

2022-02-18 Thread herumi at nifty dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104603 --- Comment #5 from herumi --- >Can you file a seperate issue with the preprocessed source (-save-temps) since >it really does look like a seperate issue all together. May I attach a zipped a.ii which is generated by the following commands? T

[Bug tree-optimization/104603] [10/11/12 Regression] wrong detection of -Warray-bounds for interesting tail resusive case

2022-02-18 Thread herumi at nifty dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104603 --- Comment #3 from herumi --- >Also if this is from some larger code, >it might be useful to have the non-reduced testcase >since the reduced testcase might being showing something different. The reason why I made this code is from the issue:

[Bug c++/104603] New: wrong detection of g++ -Warray-bounds about downcast

2022-02-18 Thread herumi at nifty dot com via Gcc-bugs
Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: herumi at nifty dot com Target Milestone: --- Created attachment 52477 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52477&action=edit a minimal sample of the bug g++-10.3.0 and g++-11.2 -O2 -Warray

[Bug c++/84858] New: wrong exception handling of std::function

2018-03-13 Thread herumi at nifty dot com
++ Assignee: unassigned at gcc dot gnu.org Reporter: herumi at nifty dot com Target Milestone: --- The following code shows "g" infinitely. Is my code wrong? Or is it a bug of gcc? >g++ t.cpp -O2 -std=c++11 && ./a.out >f >f >g >g > My

[Bug c/42968] _mm_cvtsi128_si32() should always be assigned to movd.

2010-02-05 Thread herumi at nifty dot com
--- Comment #2 from herumi at nifty dot com 2010-02-05 17:20 --- >You should split your application into files that are compiled with either -msse2 or -msse4. Using -msse4, you will get what you asked for. I see, but according to Intel 64 and IA-32 Architectures Optimization Refere

[Bug c/42968] New: _mm_cvtsi128_si32() should always be assigned to movd.

2010-02-05 Thread herumi at nifty dot com
Version: 4.4.3 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: herumi at nifty dot com GCC build triplet: i686-pc-linux-gnu GCC host triplet: i686-pc-linux-gnu GCC ta