[Bug tree-optimization/67947] [6 Regression] wrong code at -O3 on x86_64-linux-gnu

2024-07-26 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67947 --- Comment #4 from GCC Commits --- The master branch has been updated by Sam James : https://gcc.gnu.org/g:a75c6295252d0d998a18927dc7510fac965134c4 commit r15-2349-ga75c6295252d0d998a18927dc7510fac965134c4 Author: Sam James Date: Thu Jul 18

[Bug c++/116102] static_cast to derived& of base& does not cause a -fsanitize=vptr violation

2024-07-26 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116102 Andrew Pinski changed: What|Removed |Added Summary|static_cast to derived& of |static_cast to derived& of

[Bug c++/116102] static_cast to derived& of base& does not cause a -fsanitize=vptr violation

2024-07-26 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116102 Andrew Pinski changed: What|Removed |Added Last reconfirmed||2024-07-26 Status|UNCONFIRM

[Bug c/116016] enhancement: add __builtin_set_counted_by(P->FAM, COUNT) or equivalent

2024-07-26 Thread qinzhao at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116016 --- Comment #22 from qinzhao at gcc dot gnu.org --- the following is the user documentation I came up based on all the discussion so far, let me know any comment and suggestion. (refer to GCC's __builtin_clear_padding doc on the prototype of the

[Bug c++/116052] [15 Regression] ICE in diagnostic_context::diagnostic_impl

2024-07-26 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116052 --- Comment #8 from GCC Commits --- The trunk branch has been updated by Jason Merrill : https://gcc.gnu.org/g:ea381d87ecc711d0003ae6841477ae8000894844 commit r15-2351-gea381d87ecc711d0003ae6841477ae8000894844 Author: Jason Merrill Date: Th

[Bug c++/116052] [15 Regression] ICE in diagnostic_context::diagnostic_impl

2024-07-26 Thread jason at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116052 Jason Merrill changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED

[Bug c/115185] Missing "too long" warning when string-array size doesn't include NULL byte

2024-07-26 Thread alx at kernel dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115185 --- Comment #25 from Alejandro Colomar --- BTW, since this seems to be a de-facto place to report bugs found by this warning, let's also list here another one found in Linux by Sam the other day: Report:

[Bug target/116086] RISC-V: Hash mismatch with vectorized 557.xz_r at zvl128b and LMUL=m2

2024-07-26 Thread rdapp at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116086 --- Comment #7 from Robin Dapp --- Ok, if done right, i.e. without introducing a new bug, both the reduced case as well as the original case show the same behavior with respect to the fix. Also, xz calculates the proper hash, phew. I sent a fir

[Bug target/116111] New: RISC-V: 'd' extension allowed with -mabi=ilp32e

2024-07-26 Thread patrick at rivosinc dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116111 Bug ID: 116111 Summary: RISC-V: 'd' extension allowed with -mabi=ilp32e Product: gcc Version: 15.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component:

[Bug c/116016] enhancement: add __builtin_set_counted_by(P->FAM, COUNT) or equivalent

2024-07-26 Thread isanbard at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116016 --- Comment #23 from Bill Wendling --- (In reply to qinzhao from comment #22) > the following is the user documentation I came up based on all the > discussion so far, let me know any comment and suggestion. (refer to GCC's > __builtin_clear_pad

[Bug middle-end/25521] change semantics of const volatile variables

2024-07-26 Thread sjames at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=25521 Sam James changed: What|Removed |Added Resolution|--- |FIXED Target Milestone|---

[Bug target/116085] [13/14/15 Regression] RISC-V: Miscompile at -O2 with zbb

2024-07-26 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116085 --- Comment #7 from GCC Commits --- The master branch has been updated by Jeff Law : https://gcc.gnu.org/g:6e5aae47e3b910f9af6983f744d7a3e2dcecba1d commit r15-2352-g6e5aae47e3b910f9af6983f744d7a3e2dcecba1d Author: Jeff Law Date: Fri Jul 26

[Bug target/116085] [13/14/15 Regression] RISC-V: Miscompile at -O2 with zbb

2024-07-26 Thread law at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116085 Jeffrey A. Law changed: What|Removed |Added Resolution|--- |FIXED Status|NEW

[Bug target/116111] RISC-V: 'd' extension allowed with -mabi=ilp32e

2024-07-26 Thread law at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116111 Jeffrey A. Law changed: What|Removed |Added CC||law at gcc dot gnu.org --- Comment #1

[Bug target/116086] RISC-V: Hash mismatch with vectorized 557.xz_r at zvl128b and LMUL=m2

2024-07-26 Thread patrick at rivosinc dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116086 --- Comment #8 from Patrick O'Neill --- (In reply to Robin Dapp from comment #6) > Ah, thanks for reducing. I didn't get much further with cvise yesterday. > What were your settings for it? I used the normal settings (just --timeout to fail h

[Bug tree-optimization/116098] [14/15 Regression] _Bool value from tagged union is incorrect when built with optimization since r14-1597-g64d90d06d2db43

2024-07-26 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116098 --- Comment #8 from Andrew Pinski --- (In reply to Richard Biener from comment #7) > Ah, it's the code that makes SRA widen bit-precision values to > size-precision integers. That said, I don't see why the V_C_E should not be > moveable. > >

[Bug middle-end/107941] json diagnostics format does not include header stack info

2024-07-26 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107941 --- Comment #6 from GCC Commits --- The master branch has been updated by David Malcolm : https://gcc.gnu.org/g:4d1f71d49e396cb879d43dc96dc591079af66bbe commit r15-2354-g4d1f71d49e396cb879d43dc96dc591079af66bbe Author: David Malcolm Date: F

[Bug middle-end/107941] json diagnostics format does not include header stack info

2024-07-26 Thread dmalcolm at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107941 David Malcolm changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug c/116112] New: ICE: in add_dwarf_attr, at dwarf2out.cc:4515

2024-07-26 Thread iamanonymous.cs at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116112 Bug ID: 116112 Summary: ICE: in add_dwarf_attr, at dwarf2out.cc:4515 Product: gcc Version: 15.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c

[Bug debug/100530] [12/13/14/15 Regression] ICE with -g: in add_dwarf_attr with __seg_gs (Alternative address-space) global variable since r8-4385-ga297ccb52e0c894e

2024-07-26 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100530 --- Comment #16 from Andrew Pinski --- *** Bug 116112 has been marked as a duplicate of this bug. ***

[Bug debug/116112] ICE: in add_dwarf_attr, at dwarf2out.cc:4515

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

[Bug c++/116113] New: ICE: Segmentation fault (maybe_convert_cond)

2024-07-26 Thread iamanonymous.cs at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116113 Bug ID: 116113 Summary: ICE: Segmentation fault (maybe_convert_cond) Product: gcc Version: 15.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++

[Bug c++/116113] ICE: Segmentation fault (maybe_convert_cond)

2024-07-26 Thread iamanonymous.cs at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116113 --- Comment #1 from Anonymous --- Created attachment 58766 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=58766&action=edit cpp testcase

[Bug c++/116113] ICE: Segmentation fault (maybe_convert_cond)

2024-07-26 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116113 Andrew Pinski changed: What|Removed |Added Keywords||ice-on-invalid-code --- Comment #2 from

[Bug c++/116113] [15 Regression] ICE: Segmentation fault (maybe_convert_cond)

2024-07-26 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116113 Andrew Pinski changed: What|Removed |Added Keywords||error-recovery Target Milestone|---

[Bug middle-end/116114] New: PROP_no_crit_edges is no longer tested for can be removed

2024-07-26 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116114 Bug ID: 116114 Summary: PROP_no_crit_edges is no longer tested for can be removed Product: gcc Version: 15.0 Status: UNCONFIRMED Keywords: internal-improvement

[Bug middle-end/116114] PROP_no_crit_edges is no longer tested for can be removed

2024-07-26 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116114 Andrew Pinski changed: What|Removed |Added Ever confirmed|0 |1 Last reconfirmed|

[Bug middle-end/116115] New: Move reload_completed and reload_in_progress to be PROP_reload_completed and PROP_reload_in_progress

2024-07-26 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116115 Bug ID: 116115 Summary: Move reload_completed and reload_in_progress to be PROP_reload_completed and PROP_reload_in_progress Product: gcc Version: 15.0 Status: UNCONFIRM

[Bug target/116105] ESP32 error

2024-07-26 Thread charantiruvuri99 at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116105 --- Comment #3 from Syamala Aamani Vissapragada --- (In reply to Richard Biener from comment #1) > What version of GCC are you using? What is the GCC command-line? Hi @Richard Biener Firstly, I am new to this kind of error from GCC and could

<    1   2