[Bug sanitizer/113251] New: [14 Regression] ICE on gcc.dg/asan/pr63845.c on i686-linux since r14-6946

2024-01-06 Thread jakub at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113251 Bug ID: 113251 Summary: [14 Regression] ICE on gcc.dg/asan/pr63845.c on i686-linux since r14-6946 Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: norm

[Bug sanitizer/113251] [14 Regression] ICE on gcc.dg/asan/pr63845.c on i686-linux since r14-6946

2024-01-06 Thread jakub at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113251 Jakub Jelinek changed: What|Removed |Added Target Milestone|--- |14.0 Priority|P3

[Bug libstdc++/113250] std::filesystem::equivalent("", "/") should throw

2024-01-06 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113250 Jonathan Wakely changed: What|Removed |Added Last reconfirmed||2024-01-06 Ever confirmed|0

[Bug target/105525] some targets don't define __INTPTR_TYPE__ breaking libgcov-driver.c

2024-01-06 Thread mikpelinux at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105525 Mikael Pettersson changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRME

[Bug lto/113204] [14 Regression] lto1: error: qsort comparator non-negative on sorted output: 64

2024-01-06 Thread sjames at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113204 Sam James changed: What|Removed |Added CC||sjames at gcc dot gnu.org See Als

[Bug lto/113204] [14 Regression] lto1: error: qsort comparator non-negative on sorted output: 64

2024-01-06 Thread sjames at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113204 --- Comment #3 from Sam James --- 13 is affected too at least, I'm pretty sure, but I can't check right now. Just needs checking.

[Bug lto/113204] lto1: error: qsort comparator non-negative on sorted output: 64

2024-01-06 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113204 Andrew Pinski changed: What|Removed |Added Summary|[14 Regression] lto1: |lto1: error: qsort |e

[Bug target/113140] [SPARC] [13 Regression] Segmentation fault during RTL pass: dbr

2024-01-06 Thread ebotcazou at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113140 Eric Botcazou changed: What|Removed |Added Assignee|unassigned at gcc dot gnu.org |ebotcazou at gcc dot gnu.org

[Bug c/113252] New: No -Wtype-limits on comparaisons against type max values

2024-01-06 Thread mailhol.vincent at wanadoo dot fr via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113252 Bug ID: 113252 Summary: No -Wtype-limits on comparaisons against type max values Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Prio

[Bug sanitizer/113251] [14 Regression] ICE on gcc.dg/asan/pr63845.c on i686-linux since r14-6946

2024-01-06 Thread iii at linux dot ibm.com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113251 Ilya Leoshkevich changed: What|Removed |Added CC||iii at linux dot ibm.com --- Comment

[Bug c/113252] No -Wtype-limits on comparaisons against type max values

2024-01-06 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113252 --- Comment #1 from Andrew Pinski --- Created attachment 56995 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56995&action=edit (non-preprocessed) testcase

[Bug libstdc++/113200] std::char_traits::move is not constexpr when the argument is a string literal

2024-01-06 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113200 --- Comment #11 from GCC Commits --- The releases/gcc-13 branch has been updated by Jonathan Wakely : https://gcc.gnu.org/g:22601c1c25652c71c8bab4707866c020d6dad79a commit r13-8193-g22601c1c25652c71c8bab4707866c020d6dad79a Author: Jonathan Wak

[Bug libstdc++/113241] [13/14 Regression] Unguarded use of __is_convertible built-in

2024-01-06 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113241 --- Comment #2 from GCC Commits --- The releases/gcc-13 branch has been updated by Jonathan Wakely : https://gcc.gnu.org/g:4c66513656775d551db36b53c253cf236f0eeba8 commit r13-8194-g4c66513656775d551db36b53c253cf236f0eeba8 Author: Jonathan Wake

[Bug fortran/96724] Bogus warnings with the repeat intrinsic and the flag -Wconversion-extra

2024-01-06 Thread anlauf at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96724 anlauf at gcc dot gnu.org changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|-

[Bug libstdc++/113241] [13/14 Regression] Unguarded use of __is_convertible built-in

2024-01-06 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113241 Jonathan Wakely changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug c/87950] GCC warns about reaching end of non-void function when all switch cases are completely handled

2024-01-06 Thread arsen at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87950 Arsen Arsenović changed: What|Removed |Added CC||arsen at gcc dot gnu.org --- Comment #

[Bug sanitizer/113244] Potential thread sanitizer false positive with future exception

2024-01-06 Thread gcc-bugzilla at mhxnet dot de via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113244 --- Comment #2 from Marcus Holland-Moritz --- (In reply to Andrew Pinski from comment #1) > I suspect this is because libstdc++.so is NOT instrumented for TSAN. This is certainly possible. Is there documentation available on how to build a sui

[Bug analyzer/102671] -Wanalyzer-null-dereference false positive when compiling GNU Emacs

2024-01-06 Thread eggert at cs dot ucla.edu via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102671 --- Comment #4 from Paul Eggert --- Created attachment 56996 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56996&action=edit marker.i example from GNU Emacs Here is another example of the problem, taken from bleeding-edge GNU Emacs compi

[Bug analyzer/102671] -Wanalyzer-null-dereference false positive when compiling GNU Emacs

2024-01-06 Thread eggert at cs dot ucla.edu via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102671 --- Comment #5 from Paul Eggert --- Created attachment 56997 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56997&action=edit xselect.i example from GNU Emacs Attached is another example taken from bleeding-edge GNU Emacs, compiled with g

[Bug libgomp/113192] [11/12/13/14 Regression] ERROR: couldn't execute "../../../gcc/libgomp/testsuite/flock": no such file or directory

2024-01-06 Thread danglin at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113192 --- Comment #3 from John David Anglin --- export FLOCK=/home/dave/gnu/gcc/gcc/libgomp/testsuite/flock in my build script works around configure issue.

[Bug analyzer/113253] New: gcc -g causes -fanalyzer to issue false positive

2024-01-06 Thread eggert at cs dot ucla.edu via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113253 Bug ID: 113253 Summary: gcc -g causes -fanalyzer to issue false positive Product: gcc Version: 13.2.1 Status: UNCONFIRMED Severity: normal Priority: P3 Componen

[Bug analyzer/102671] -Wanalyzer-null-dereference false positive when compiling GNU Emacs

2024-01-06 Thread eggert at cs dot ucla.edu via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102671 --- Comment #6 from Paul Eggert --- (In reply to Paul Eggert from comment #4) > Created attachment 56996 [details] > marker.i example from GNU Emacs > > Here is another example of the problem, taken from bleeding-edge GNU Emacs Ooops, please i

[Bug fortran/113254] New: Option -fallow-invalid-boz does not help with sample code

2024-01-06 Thread xecej4 at outlook dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113254 Bug ID: 113254 Summary: Option -fallow-invalid-boz does not help with sample code Product: gcc Version: 11.4.0 Status: UNCONFIRMED Severity: normal P

[Bug sanitizer/105347] [12/13/14 Regression] Failed to build from source on FreeBSD 11.* due to using nonexistent sha224.h

2024-01-06 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105347 Andrew Pinski changed: What|Removed |Added Resolution|--- |WONTFIX Status|NEW

[Bug tree-optimization/113239] [13 regression] After 822a11a1e64, bogus -Warray-bounds warnings in std::vector

2024-01-06 Thread dimitry--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113239 Dimitry Andric changed: What|Removed |Added CC||amacleod at redhat dot com --- Comment

[Bug tree-optimization/113239] [13 regression] After 822a11a1e64, bogus -Warray-bounds warnings in std::vector

2024-01-06 Thread dimitry--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113239 --- Comment #3 from Dimitry Andric --- Alright, I can confirm that adding --param=vrp1-mode=vrp makes the warning go away. However, this option is no longer recognized by gcc-14-6924-g00dea7e8c41. I assume the ranger mode is now the default, and

[Bug c/113255] New: wrong code with -O2 -mtune=k8

2024-01-06 Thread mednafen at sent dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113255 Bug ID: 113255 Summary: wrong code with -O2 -mtune=k8 Product: gcc Version: 13.2.0 Status: UNCONFIRMED Keywords: wrong-code Severity: normal Priority: P3

[Bug target/113255] [11/12/13/14 Regression] wrong code with -O2 -mtune=k8

2024-01-06 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113255 Andrew Pinski changed: What|Removed |Added Target Milestone|--- |11.5 Known to fail|

[Bug c++/102780] Checking constraints using large fold expression is slow

2024-01-06 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102780 --- Comment #8 from GCC Commits --- The master branch has been updated by Jonathan Wakely : https://gcc.gnu.org/g:7d11d813583efad652c83c7631ef8d6d18489119 commit r14-6974-g7d11d813583efad652c83c7631ef8d6d18489119 Author: Jonathan Wakely Date:

[Bug libstdc++/112997] _Unwind_Exception conflicts with void*. failed to build with clang

2024-01-06 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112997 --- Comment #9 from GCC Commits --- The master branch has been updated by Jonathan Wakely : https://gcc.gnu.org/g:8c5d00f8291d718ef64c742b9c971e16f75e5074 commit r14-6975-g8c5d00f8291d718ef64c742b9c971e16f75e5074 Author: Jonathan Wakely Date:

[Bug libstdc++/112997] _Unwind_Exception conflicts with void*. failed to build with clang

2024-01-06 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112997 Jonathan Wakely changed: What|Removed |Added Resolution|WONTFIX |FIXED Target Milestone|---

[Bug fortran/113254] Option -fallow-invalid-boz does not help with sample code

2024-01-06 Thread kargl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113254 kargl at gcc dot gnu.org changed: What|Removed |Added CC||kargl at gcc dot gnu.org

[Bug c++/113256] New: False -Wdangling-reference positive

2024-01-06 Thread pdimov at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113256 Bug ID: 113256 Summary: False -Wdangling-reference positive Product: gcc Version: 13.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++

[Bug bootstrap/113174] gcc fails to bootstrap on pp64le with clang-based host environment (internal compiler error)

2024-01-06 Thread gcc at octaforge dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113174 --- Comment #8 from Daniel Kolesa --- I tried an experiment: I canceled the build after initial generation of insn-recog.cc and patched the offending part with logic from a stage-2 insn-recog.cc I managed to previously capture: ``` --- insn-rec

[Bug fortran/113254] Option -fallow-invalid-boz does not help with sample code

2024-01-06 Thread xecej4 at outlook dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113254 --- Comment #2 from mecej4 --- Created attachment 57001 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57001&action=edit Program source that is handled correctly when -fallow-invalid-boz is specified

[Bug fortran/113254] Option -fallow-invalid-boz does not help with sample code

2024-01-06 Thread kargl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113254 --- Comment #3 from kargl at gcc dot gnu.org --- (In reply to mecej4 from comment #2) > Created attachment 57001 [details] > Program source that is handled correctly when -fallow-invalid-boz is > specified Correctly? It is not the same as the i