[Bug tree-optimization/98907] New: Failure to optimize abs pattern

2021-01-31 Thread gabravier at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98907 Bug ID: 98907 Summary: Failure to optimize abs pattern Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: tree-optimization

[Bug testsuite/98870] [11 regression] assembler output count off for gcc.target/powerpc/ppc-fortran/ieee128-math.f90 after r11-6959

2021-01-31 Thread meissner at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98870 Michael Meissner changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

gcc -fanalyzer: false positives: use after free, double free

2021-01-31 Thread Heinrich Schuchardt via Gcc-bugs
gcc (Debian 11-20210130-1) 11.0.0 20210130 (experimental) [master revision 4d31df40899:799f8820257:2900f2f2c5fb234678eb8b76564e5994ec5970b9] gcc -fanalyzer for the sample code below gives false positive results. If I remove field ref from struct marker, no problem is reported. Best regards

[Bug libfortran/98825] Unexpected behavior of FORTRAN FORMAT expressions when suppressing new line with '$'

2021-01-31 Thread jvdelisle at charter dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98825 --- Comment #9 from Jerry DeLisle --- The folowing patch fixes this and regression tests OK. diff --git a/libgfortran/io/transfer.c b/libgfortran/io/transfer.c index 8ab0583dd55..27bee9d4e01 100644 --- a/libgfortran/io/transfer.c +++

[Bug tree-optimization/98906] [8/9/10/11 Regression] Miscompiles code even at -O1

2021-01-31 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98906 Andrew Pinski changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug middle-end/87489] [8/9/10/11 Regression] Spurious -Wnonnull warning

2021-01-31 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87489 Martin Sebor changed: What|Removed |Added Keywords|deferred|patch Assignee|unassigned at

[Bug tree-optimization/98906] [8/9/10/11 Regression] Miscompiles code even at -O1

2021-01-31 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98906 --- Comment #3 from Andrew Pinski --- unsigned quo = (uint32_t)(int64_t)(quo_hi) + (uint32_t)(int64_t)(quo_lo); Fixes the issue ..

[Bug middle-end/87489] [8/9/10/11 Regression] Spurious -Wnonnull warning

2021-01-31 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87489 Martin Sebor changed: What|Removed |Added Attachment #50098|0 |1 is obsolete|

[Bug tree-optimization/98906] [8/9/10/11 Regression] Miscompiles code even at -O1

2021-01-31 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98906 --- Comment #2 from Andrew Pinski --- (In reply to Andrew Pinski from comment #1) > I think this code is undefined/unspecified as -86 is outside the range of an > unsigned int. Even with changing to cast to int first still gives the same. Note

[Bug tree-optimization/98906] [8/9/10/11 Regression] Miscompiles code even at -O1

2021-01-31 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98906 --- Comment #1 from Andrew Pinski --- So ccp3 is doing it. Visiting statement: quo_lo_52 = floorf (_51); which is likely CONSTANT Match-and-simplified floorf (_51) to -8.6e+1 Lattice value changed to CONSTANT -8.6e+1. Adding SSA edges to

[Bug middle-end/87489] [8/9/10/11 Regression] Spurious -Wnonnull warning

2021-01-31 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87489 --- Comment #12 from Martin Sebor --- Created attachment 50098 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=50098=edit Patch to move -Wnonnull to pass_merge_phi. No change in GCC 11 so far. I've reduced the test case in attachment

[Bug tree-optimization/98906] New: [8/9/10/11 Regression] Miscompiles code even at -O1

2021-01-31 Thread amonakov at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98906 Bug ID: 98906 Summary: [8/9/10/11 Regression] Miscompiles code even at -O1 Product: gcc Version: 11.0 Status: UNCONFIRMED Keywords: wrong-code Severity: normal

[Bug middle-end/98900] misleading -Wuninitialized using a variable outside its lifetime with -O2

2021-01-31 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98900 Martin Sebor changed: What|Removed |Added See Also||https://gcc.gnu.org/bugzill

[Bug target/98905] lstat() confused with wrong struct stat

2021-01-31 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98905 Jonathan Wakely changed: What|Removed |Added Last reconfirmed||2021-01-31

[Bug middle-end/98901] missing warning passing a dangling pointer to a function

2021-01-31 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98901 Martin Sebor changed: What|Removed |Added Ever confirmed|0 |1 Last reconfirmed|

[Bug fortran/98904] valgrind error in gfc_trans_assignment_1 during bootstrap

2021-01-31 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98904 David Binderman changed: What|Removed |Added CC||vehre at gcc dot gnu.org --- Comment

[Bug middle-end/98900] misleading -Wuninitialized using a variable outside its lifetime with -O2

2021-01-31 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98900 Martin Sebor changed: What|Removed |Added Blocks||24639 CC|

[Bug c/98905] New: lstat() confused with wrong struct stat

2021-01-31 Thread gcc at madler dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98905 Bug ID: 98905 Summary: lstat() confused with wrong struct stat Product: gcc Version: 5.5.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c

[Bug c++/85428] constexpr pointer equality comparison not considered constant expression

2021-01-31 Thread barry.revzin at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85428 Barry Revzin changed: What|Removed |Added CC||barry.revzin at gmail dot com ---

[Bug fortran/98904] valgrind error in gfc_trans_assignment_1 during bootstrap

2021-01-31 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98904 --- Comment #1 from David Binderman --- The compile line of relevance is /home/dcb/gcc/working.valgrind/./gcc/gfortran -B/home/dcb/gcc/working.valgrind/./gcc/ -B/home/dcb/gcc/results.20210131.valgrind/x86_64-pc-linux-gnu/bin/ -B/home/dcb/gcc

[Bug fortran/98904] New: valgrind error in gfc_trans_assignment_1 during bootstrap

2021-01-31 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98904 Bug ID: 98904 Summary: valgrind error in gfc_trans_assignment_1 during bootstrap Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal

[Bug c/98902] -fmerge-all-constants leaves dangling reference

2021-01-31 Thread schwab--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98902 Andreas Schwab changed: What|Removed |Added Resolution|FIXED |INVALID

[Bug c/98902] -fmerge-all-constants leaves dangling reference

2021-01-31 Thread astrange at ithinksw dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98902 Alexander Strange changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug fortran/98903] New: [Coarray, F2018] Implement TEAM_NUMBER in image-selector-spec

2021-01-31 Thread tkoenig at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98903 Bug ID: 98903 Summary: [Coarray, F2018] Implement TEAM_NUMBER in image-selector-spec Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal

[Bug c/98902] -fmerge-all-constants leaves dangling reference

2021-01-31 Thread schwab--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98902 --- Comment #1 from Andreas Schwab --- What's your target? There is supposed to be ".set a2,a1" at the end.

[Bug c/98902] New: -fmerge-all-constants leaves dangling reference

2021-01-31 Thread astrange at ithinksw dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98902 Bug ID: 98902 Summary: -fmerge-all-constants leaves dangling reference Product: gcc Version: 10.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component:

[Bug c/98901] New: Static analyses warning disappears when the value is passed to a function with variable number of arguments when optimisation is on

2021-01-31 Thread oleg.pekar.2017 at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98901 Bug ID: 98901 Summary: Static analyses warning disappears when the value is passed to a function with variable number of arguments when optimisation is on Product: gcc

[Bug c/98900] New: Wrong static analyses warning when optimisation is on

2021-01-31 Thread oleg.pekar.2017 at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98900 Bug ID: 98900 Summary: Wrong static analyses warning when optimisation is on Product: gcc Version: 8.3.1 Status: UNCONFIRMED Severity: normal Priority: P3