[Bug tree-optimization/98954] ((X << CST0) & CST1) == 0 is not optimized to 0 == (X & (CST1 >> CST0))

2022-09-10 Thread roger at nextmovesoftware dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98954 Roger Sayle changed: What|Removed |Added Target Milestone|--- |13.0 Status|ASSIGNED

[Bug tree-optimization/98956] Failure to optimize out boolean left shift

2022-09-10 Thread roger at nextmovesoftware dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98956 Roger Sayle changed: What|Removed |Added Status|ASSIGNED|RESOLVED CC|

[Bug tree-optimization/64992] More optimize opportunity

2022-09-10 Thread roger at nextmovesoftware dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64992 Roger Sayle changed: What|Removed |Added CC||roger at nextmovesoftware dot com

[Bug tree-optimization/98956] Failure to optimize out boolean left shift

2022-09-10 Thread roger at nextmovesoftware dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98956 Bug 98956 depends on bug 64992, which changed state. Bug 64992 Summary: More optimize opportunity https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64992 What|Removed |Added --

[Bug target/106902] Program compiled with -O3 -mfma produces different result

2022-09-10 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106902 --- Comment #1 from Andrew Pinski --- Note -mfma should only increase the precision of doing a multiple and add in infinite precision before a rounding step. So if you depend on exactly rounding after each operation then you need to use -ffp-con

[Bug tree-optimization/106902] New: Program compiled with -O3 -fmfa produces different result

2022-09-10 Thread jhllawrence963 at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106902 Bug ID: 106902 Summary: Program compiled with -O3 -fmfa produces different result Product: gcc Version: 12.2.0 Status: UNCONFIRMED Severity: normal P

[Bug c++/106901] False positive -Warray-bounds with -O2 or higher?

2022-09-10 Thread carlosgalvezp at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106901 --- Comment #4 from Carlos Galvez --- Makes sense! Would it make sense to classify this as "maybe-array-bounds" instead? Similar to "maybe-uninitialized" vs "uninitialized"

[Bug c++/106652] [C++23] P1467 - Extended floating-point types and standard names

2022-09-10 Thread jakub at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106652 --- Comment #14 from Jakub Jelinek --- What I did in the patch is stop predefining __FLT32X_*__ macros etc. for C++ because C++ doesn't support those, so perhaps the if !__GNUC_PREREQ (7, 0) || defined __cplusplus conditions related to _Float (b

[Bug c++/106901] False positive -Warray-bounds with -O2 or higher?

2022-09-10 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106901 --- Comment #3 from Andrew Pinski --- Yes if size is 5, then yes it will not be executed. There is another bug about the wording of the warning. The warning is saying there might be an out of bounds due to the bounds of the loop is not bounded o

[Bug c++/106652] [C++23] P1467 - Extended floating-point types and standard names

2022-09-10 Thread jakub at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106652 Jakub Jelinek changed: What|Removed |Added CC||jsm28 at gcc dot gnu.org --- Comment #1

[Bug c++/106652] [C++23] P1467 - Extended floating-point types and standard names

2022-09-10 Thread jakub at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106652 --- Comment #12 from Jakub Jelinek --- Created attachment 53559 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53559&action=edit gcc13-pr106652-lib.patch Some unfinished library changes. Unfortunately, we seem to have a major problem wit

[Bug c++/106901] False positive -Warray-bounds with -O2 or higher?

2022-09-10 Thread carlosgalvezp at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106901 --- Comment #2 from Carlos Galvez --- If size == 5, expected_size == 5, then the loop is not executed, right?

[Bug c++/106901] False positive -Warray-bounds with -O2 or higher?

2022-09-10 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106901 --- Comment #1 from Andrew Pinski --- Maybe I am reading the code wrong. But size will be >= 5 at the loop. So it will be executed. If size is >= 5. And that is what the warning is about.

[Bug c++/106901] New: False positive -Warray-bounds with -O2 or higher?

2022-09-10 Thread carlosgalvezp at gmail dot com via Gcc-bugs
long unsigned int _Nm = 5]', inlined from 'bool bar(const std::array&, std::size_t, std::size_t)' at :13:18, inlined from 'bool foo(const std::array&, std::size_t)' at :23:15: /opt/compiler-explorer/gcc-trunk-20220910/include/c++/13.0.0/array:213:24: warnin

[Bug fortran/100662] intrinsic::ieee_arithmetic fails on aarch, powerpc architectures on FreeBSD

2022-09-10 Thread vital.had at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100662 Sergey Fedorov changed: What|Removed |Added CC||vital.had at gmail dot com --- Comment

[Bug fortran/29383] Fortran 2003/F95[TR15580:1999]: Floating point exception (IEEE) support

2022-09-10 Thread vital.had at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=29383 Sergey Fedorov changed: What|Removed |Added CC||vital.had at gmail dot com --- Comment

[Bug middle-end/106892] [11/12 Regression] Wrong code at -O3 on x86_64-linux-gnu since r11-963-g80d6f89e78fc3b77

2022-09-10 Thread mikpelinux at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106892 Mikael Pettersson changed: What|Removed |Added CC||mikpelinux at gmail dot com --- Com

[Bug c++/106652] [C++23] P1467 - Extended floating-point types and standard names

2022-09-10 Thread jakub at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106652 --- Comment #11 from Jakub Jelinek --- (In reply to Jakub Jelinek from comment #10) Ouch, sorry for lost start of the comment, this is full patch with even [conv.ics.rank]/4 changes and extended test coverage, just std::bfloat16_t support isn't

[Bug c++/106652] [C++23] P1467 - Extended floating-point types and standard names

2022-09-10 Thread jakub at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106652 Jakub Jelinek changed: What|Removed |Added Attachment #53557|0 |1 is obsolete|

[Bug driver/106897] driver: support -gz=zstd

2022-09-10 Thread i at maskray dot me via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106897 --- Comment #4 from Fangrui Song --- Yes, the change will be straightforward, basically the files touched by the pending https://gcc.gnu.org/pipermail/gcc-patches/2022-July/597586.html ("[PATCH] Remove legacy -gz=zlib-gnu"). I sent it because