[Bug target/104688] gcc and libatomic can use SSE for 128-bit atomic loads on Intel and AMD CPUs with AVX

2022-11-23 Thread xry111 at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104688 --- Comment #20 from Xi Ruoyao --- >From Mayshao (Zhaoxin engineer): "On Zhaoxin CPUs with AVX, the VMOVDQA instruction is atomic if the accessed memory is Write Back, but it's not guaranteed for other memory types." Is it allowed to use VMOVD

[Bug lto/107829] Trivial compile time tracking code

2022-11-23 Thread marxin at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107829 Martin Liška changed: What|Removed |Added Status|UNCONFIRMED |ASSIGNED Version|unknown

[Bug lto/107829] Trivial compile time tracking code

2022-11-23 Thread marxin at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107829 Martin Liška changed: What|Removed |Added Keywords||patch --- Comment #2 from Martin Liška

[Bug tree-optimization/107828] tree-inlining would generate SSA with incorrect def stmt

2022-11-23 Thread marxin at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107828 Martin Liška changed: What|Removed |Added Last reconfirmed||2022-11-23 CC|

[Bug target/104688] gcc and libatomic can use SSE for 128-bit atomic loads on Intel and AMD CPUs with AVX

2022-11-23 Thread jakub at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104688 --- Comment #21 from Jakub Jelinek --- What about loads? That is even more important than the stores. While atomic store can be worst case done through cmpxchg16b, even when it is slower, we can't use cmpxchg16b on atomic load because we don't

[Bug tree-optimization/107823] [13 Regression] Dead Code Elimination Regression at -Os (trunk vs. 12.2.0)

2022-11-23 Thread marxin at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107823 Martin Liška changed: What|Removed |Added Last reconfirmed||2022-11-23 CC|

[Bug tree-optimization/107826] ice during GIMPLE pass: slp

2022-11-23 Thread marxin at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107826 Martin Liška changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC|

[Bug libstdc++/107814] [13 regression] experimental/filesystem/iterators/error_reporting.cc FAILs

2022-11-23 Thread ro at CeBiTec dot Uni-Bielefeld.DE via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107814 --- Comment #3 from ro at CeBiTec dot Uni-Bielefeld.DE --- > --- Comment #1 from Jonathan Wakely --- > Are you sure this is a regression? Isn't it the same case as PR104731, but > that > was only fixed for 27_io/filesystem/iterators/error_repo

[Bug libstdc++/107814] [13 regression] experimental/filesystem/iterators/error_reporting.cc FAILs

2022-11-23 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107814 --- Comment #4 from Jonathan Wakely --- I think I'll push the patch in comment 2 and we can see if it helps :-)

[Bug libstdc++/107814] [13 regression] experimental/filesystem/iterators/error_reporting.cc FAILs

2022-11-23 Thread ro at CeBiTec dot Uni-Bielefeld.DE via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107814 --- Comment #5 from ro at CeBiTec dot Uni-Bielefeld.DE --- > --- Comment #4 from Jonathan Wakely --- > I think I'll push the patch in comment 2 and we can see if it helps :-) I've just tried it on sparc and x86, 32 and 64-bit: the test PASSes

[Bug c/107831] New: Missed optimization: -fclash-stack-protection causes unnecessary code generation for dynamic stack allocations that are clearly less than a page

2022-11-23 Thread pskocik at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107831 Bug ID: 107831 Summary: Missed optimization: -fclash-stack-protection causes unnecessary code generation for dynamic stack allocations that are clearly less than a page Pro

[Bug libstdc++/107814] [13 regression] experimental/filesystem/iterators/error_reporting.cc FAILs

2022-11-23 Thread ro at CeBiTec dot Uni-Bielefeld.DE via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107814 --- Comment #6 from ro at CeBiTec dot Uni-Bielefeld.DE --- > --- Comment #2 from Jonathan Wakely --- > I'm unable to access the Solaris/x86 host in the compile farm (gcc210) so I > can't test if this fixes it. It passes on Solaris/sparc. Accor

[Bug target/107830] [13 Regression] ICE in gen_aarch64_bitmask_udiv3, at ./insn-opinit.h:813

2022-11-23 Thread marxin at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107830 Martin Liška changed: What|Removed |Added CC||ktkachov at gcc dot gnu.org,

[Bug libstdc++/107814] [13 regression] experimental/filesystem/iterators/error_reporting.cc FAILs

2022-11-23 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107814 --- Comment #7 from Jonathan Wakely --- (In reply to r...@cebitec.uni-bielefeld.de from comment #6) > According to https://cfarm.tetaneutral.net/machines/list/, gcc210 is a > Solaris 10/SPARC system, so useless for trunk testing. Oh right, yes.

[Bug libstdc++/104731] 27_io/filesystem/iterators/error_reporting.cc FAILs

2022-11-23 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104731 --- Comment #13 from CVS Commits --- The master branch has been updated by Jonathan Wakely : https://gcc.gnu.org/g:1cac00d013856fea4cee0f13c4959c8e21afd2d9 commit r13-4262-g1cac00d013856fea4cee0f13c4959c8e21afd2d9 Author: Jonathan Wakely Date

[Bug libstdc++/107814] [13 regression] experimental/filesystem/iterators/error_reporting.cc FAILs

2022-11-23 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107814 --- Comment #8 from CVS Commits --- The master branch has been updated by Jonathan Wakely : https://gcc.gnu.org/g:1cac00d013856fea4cee0f13c4959c8e21afd2d9 commit r13-4262-g1cac00d013856fea4cee0f13c4959c8e21afd2d9 Author: Jonathan Wakely Date:

[Bug libstdc++/107814] [13 regression] experimental/filesystem/iterators/error_reporting.cc FAILs

2022-11-23 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107814 Jonathan Wakely changed: What|Removed |Added Target Milestone|13.0|10.5 --- Comment #9 from Jonathan Wak

[Bug target/104688] gcc and libatomic can use SSE for 128-bit atomic loads on Intel and AMD CPUs with AVX

2022-11-23 Thread xry111 at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104688 --- Comment #22 from Xi Ruoyao --- (In reply to Jakub Jelinek from comment #21) > What about loads? That is even more important than the stores. While > atomic store can be worst case done through cmpxchg16b, even when it is > slower, we can't

[Bug target/107830] [13 Regression] ICE in gen_aarch64_bitmask_udiv3, at ./insn-opinit.h:813

2022-11-23 Thread ktkachov at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107830 ktkachov at gcc dot gnu.org changed: What|Removed |Added CC||tnfchris at gcc dot gnu.org

[Bug target/107830] [13 Regression] ICE in gen_aarch64_bitmask_udiv3, at ./insn-opinit.h:813

2022-11-23 Thread tnfchris at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107830 Tamar Christina changed: What|Removed |Added Status|NEW |ASSIGNED --- Comment #3 from Tamar Ch

[Bug libstdc++/107811] libstdc++-v3/src/c++17/floating_from_chars.cc:787:9: error: 'fast_float' has not been declared

2022-11-23 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107811 --- Comment #3 from CVS Commits --- The master branch has been updated by Jakub Jelinek : https://gcc.gnu.org/g:e6a32c12b4ef87c084d29863c79503344126d101 commit r13-4263-ge6a32c12b4ef87c084d29863c79503344126d101 Author: Jakub Jelinek Date: W

[Bug libstdc++/107811] libstdc++-v3/src/c++17/floating_from_chars.cc:787:9: error: 'fast_float' has not been declared

2022-11-23 Thread jakub at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107811 Jakub Jelinek changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED

[Bug debug/107832] New: '-fcompare-debug' failure w/ -O2 -ftree-parallelize-loops=2 -fno-gcse-lm

2022-11-23 Thread asolokha at gmx dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107832 Bug ID: 107832 Summary: '-fcompare-debug' failure w/ -O2 -ftree-parallelize-loops=2 -fno-gcse-lm Product: gcc Version: 13.0 Status: UNCONFIRMED Keywords: compa

[Bug c++/107558] [10/11/12/13 Regression] ICE in fld_incomplete_type_of with -fmerge-all-constants and openmp and LTO since r11-16-ga2f32550a085984f

2022-11-23 Thread jakub at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107558 Jakub Jelinek changed: What|Removed |Added CC||jakub at gcc dot gnu.org --- Comment #2

[Bug c/107831] Missed optimization: -fclash-stack-protection causes unnecessary code generation for dynamic stack allocations that are clearly less than a page

2022-11-23 Thread pskocik at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107831 --- Comment #1 from Petr Skocik --- Sidenote regarding the stack-allocating code for cases when the size is not known to be less than pagesize: the code generated for those cases is quite large. It could be replaced (at least under -Os) with a c

[Bug fortran/107317] [10/11/12/13 Regression] ICE in emit_redzone_byte, at asan.cc:1508

2022-11-23 Thread jakub at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107317 Jakub Jelinek changed: What|Removed |Added CC||jakub at gcc dot gnu.org Prio

[Bug tree-optimization/107833] New: wrong code at -Os and above on x86_64-linux-gnu

2022-11-23 Thread zhendong.su at inf dot ethz.ch via Gcc-bugs
--enable-languages=c,c++ --disable-werror --enable-multilib --with-system-zlib Thread model: posix Supported LTO compression algorithms: zlib gcc version 13.0.0 20221123 (experimental) [master r13-4262-g1cac00d0138] (GCC) [562] % [562] % gcctk -O1 small.c; ./a.out [563] % [563] % gcctk -Os small.c [564

[Bug c++/107329] [13 Regression] ICE in gimplify_expr, at gimplify.cc:17118 since r13-2978-g43faf3e5445b5717

2022-11-23 Thread marxin at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107329 --- Comment #1 from Martin Liška --- @Jason: May I ping this please?

[Bug fortran/107317] [10/11/12/13 Regression] ICE in emit_redzone_byte, at asan.cc:1508

2022-11-23 Thread jakub at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107317 --- Comment #4 from Jakub Jelinek --- Corresponding C testcase: -m32 -O2 -fsanitize=address void bar (float *, float *); void foo (void) { float a[4]; float b[2]; bar (a, b); }

[Bug libstdc++/107815] 20_util/to_chars/float128_c++23.cc FAILs

2022-11-23 Thread ro at CeBiTec dot Uni-Bielefeld.DE via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107815 --- Comment #4 from ro at CeBiTec dot Uni-Bielefeld.DE --- > --- Comment #3 from Jakub Jelinek --- >> The line before the assertion failure is >> >> 1.18973e+4932 1e+4932 >> /vol/gcc/src/hg/master/local/libstdc++-v3/testsuite/20_util/to_chars/

[Bug tree-optimization/107833] wrong code at -Os and above on x86_64-linux-gnu since r12-5138-ge82c382971664d6f

2022-11-23 Thread marxin at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107833 Martin Liška changed: What|Removed |Added Last reconfirmed||2022-11-23 Target Milestone|---

[Bug c++/107834] New: #pragma GCC diagnostic ignored "-Wno-psabi" doe not work

2022-11-23 Thread shihyente at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107834 Bug ID: 107834 Summary: #pragma GCC diagnostic ignored "-Wno-psabi" doe not work Product: gcc Version: 12.2.0 Status: UNCONFIRMED Severity: normal Pr

[Bug target/107304] internal compiler error: in convert_move, at expr.cc:220 with -march=tigerlake

2022-11-23 Thread ro at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107304 Rainer Orth changed: What|Removed |Added CC||ro at gcc dot gnu.org --- Comment #29 fro

[Bug c++/107834] #pragma GCC diagnostic ignored "-Wno-psabi" doe not work

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

[Bug bootstrap/107722] [13 Regression] Bootstrap failure for some locales starting with r13-4070

2022-11-23 Thread lhyatt at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107722 Lewis Hyatt changed: What|Removed |Added CC||lhyatt at gcc dot gnu.org --- Comment #5

[Bug modula2/107233] gm2 build hardcodes python3

2022-11-23 Thread ro at CeBiTec dot Uni-Bielefeld.DE via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107233 --- Comment #4 from ro at CeBiTec dot Uni-Bielefeld.DE --- > --- Comment #3 from Gaius Mulley --- > ok, thanks for the suggestion. I've changed gcc/configure.ac to use > AM_PATH_PYTHON and AM_CONDITIONAL: > > # Python3? > AM_PATH_PYTHON(,, [:]

[Bug bootstrap/107722] [13 Regression] Bootstrap failure for some locales starting with r13-4070

2022-11-23 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107722 --- Comment #6 from CVS Commits --- The master branch has been updated by Jakub Jelinek : https://gcc.gnu.org/g:d601708870ad8dc3ef935e440bf03394891d42e2 commit r13-4265-gd601708870ad8dc3ef935e440bf03394891d42e2 Author: Jakub Jelinek Date: W

[Bug bootstrap/107722] [13 Regression] Bootstrap failure for some locales starting with r13-4070

2022-11-23 Thread jakub at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107722 Jakub Jelinek changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED

[Bug tree-optimization/107835] New: [13 Regression] ICE in build2, at tree.cc:5020 since r13-254-gdd3c7873a61019e9

2022-11-23 Thread marxin at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107835 Bug ID: 107835 Summary: [13 Regression] ICE in build2, at tree.cc:5020 since r13-254-gdd3c7873a61019e9 Product: gcc Version: 13.0 Status: UNCONFIRMED Keywords:

[Bug tree-optimization/107835] [13 Regression] ICE in build2, at tree.cc:5020 since r13-254-gdd3c7873a61019e9

2022-11-23 Thread marxin at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107835 Martin Liška changed: What|Removed |Added Last reconfirmed||2022-11-23 Ever confirmed|0

[Bug tree-optimization/107833] wrong code at -Os and above on x86_64-linux-gnu since r12-5138-ge82c382971664d6f

2022-11-23 Thread aldyh at gcc dot gnu.org via Gcc-bugs
/software/local/gcc-trunk > --enable-sanitizers --enable-languages=c,c++ --disable-werror > --enable-multilib --with-system-zlib > Thread model: posix > Supported LTO compression algorithms: zlib > gcc version 13.0.0 20221123 (experimental) [master r13-4262-g1cac00d0138] > (GCC)

[Bug tree-optimization/107833] wrong code at -Os and above on x86_64-linux-gnu since r12-5138-ge82c382971664d6f

2022-11-23 Thread marxin at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107833 --- Comment #3 from Martin Liška --- > Isn't there an uninitialized read from "i" here? Yes ... > At least on the second > time through the outer loop, if (a < h) is true since 1 < 0. > > > c = *f; > > } > > for (h = 0; h <

[Bug c++/107834] #pragma GCC diagnostic ignored "-Wno-psabi" doe not work

2022-11-23 Thread shihyente at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107834 SHIH YEN-TE changed: What|Removed |Added Resolution|--- |INVALID Status|UNCONFIRMED

[Bug modula2/105392] SEGV compiling gm2-libs-pim/BitBlockOps.mod on SPARC

2022-11-23 Thread gaius at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105392 --- Comment #3 from Gaius Mulley --- Many thanks! I've changed all definition modules in gcc/m2/gm2-gcc for consistency.

[Bug c/107836] New: x86_64 inline functions -O2/-O3 optimization error

2022-11-23 Thread czx211355007 at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107836 Bug ID: 107836 Summary: x86_64 inline functions -O2/-O3 optimization error Product: gcc Version: 11.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Compon

[Bug tree-optimization/107833] wrong code at -Os and above on x86_64-linux-gnu since r12-5138-ge82c382971664d6f

2022-11-23 Thread aldyh at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107833 --- Comment #4 from Aldy Hernandez --- (In reply to Martin Liška from comment #3) > > Isn't there an uninitialized read from "i" here? > > Yes ... > > > At least on the second > > time through the outer loop, if (a < h) is true since 1 < 0. >

[Bug c/107836] x86_64 inline functions -O2/-O3 optimization error

2022-11-23 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107836 Andrew Pinski changed: What|Removed |Added Keywords||inline-asm --- Comment #1 from Andrew P

[Bug modula2/105392] SEGV compiling gm2-libs-pim/BitBlockOps.mod on SPARC

2022-11-23 Thread gaius at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105392 Gaius Mulley changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug libstdc++/107815] 20_util/to_chars/float128_c++23.cc FAILs

2022-11-23 Thread jakub at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107815 Jakub Jelinek changed: What|Removed |Added CC||ppalka at gcc dot gnu.org,

[Bug tree-optimization/107837] New: Missed optimization: Using memcpy to load a struct unnecessary uses stack space

2022-11-23 Thread chfast at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107837 Bug ID: 107837 Summary: Missed optimization: Using memcpy to load a struct unnecessary uses stack space Product: gcc Version: 13.0 Status: UNCONFIRMED Severity

[Bug libstdc++/107815] 20_util/to_chars/float128_c++23.cc FAILs

2022-11-23 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107815 --- Comment #6 from Jonathan Wakely --- (In reply to Jakub Jelinek from comment #5) > Jonathan, shall we just #ifdef out the > std::numeric_limits::max() > test in that test for Solaris and maybe HP-UX if it suffers from the same > bug? Yes, I

[Bug libstdc++/107815] 20_util/to_chars/float128_c++23.cc FAILs

2022-11-23 Thread jakub at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107815 --- Comment #7 from Jakub Jelinek --- Ah, we even have PR98384 for that. So either we add // { dg-xfail-run-if "Non-conforming printf (see PR98384)" { *-*-solaris* *-*-darwin* } } to the test and thus xfail it all, or just ifdef out the max case

[Bug c/107836] x86_64 inline functions -O2/-O3 optimization error

2022-11-23 Thread schwab--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107836 Andreas Schwab changed: What|Removed |Added Resolution|--- |INVALID Status|UNCONFIRMED

[Bug libstdc++/107815] 20_util/to_chars/float128_c++23.cc FAILs

2022-11-23 Thread ro at CeBiTec dot Uni-Bielefeld.DE via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107815 --- Comment #8 from ro at CeBiTec dot Uni-Bielefeld.DE --- > --- Comment #5 from Jakub Jelinek --- > The 1e+202L * __DBL_MAX__ number is: > 17976931348623157081452742373170433637802939014881326705103053961532744011074502529640673538215420988836

[Bug libstdc++/107815] 20_util/to_chars/float128_c++23.cc FAILs

2022-11-23 Thread jakub at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107815 --- Comment #9 from Jakub Jelinek --- Created attachment 53953 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53953&action=edit gcc13-pr107815.patch Untested workaround. I've left out Darwin there for now, because I think it just doesn't

[Bug tree-optimization/107838] New: spurious "may be used uninitialized" warning on variable initialized at the first iteration of a loop

2022-11-23 Thread vincent-gcc at vinc17 dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107838 Bug ID: 107838 Summary: spurious "may be used uninitialized" warning on variable initialized at the first iteration of a loop Product: gcc Version: 13.0 Status: UNCONFIR

[Bug tree-optimization/107839] New: spurious "may be used uninitialized" warning while all uses are under "if (c)"

2022-11-23 Thread vincent-gcc at vinc17 dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107839 Bug ID: 107839 Summary: spurious "may be used uninitialized" warning while all uses are under "if (c)" Product: gcc Version: 13.0 Status: UNCONFIRMED Severity:

[Bug c/107840] New: ICE when compiling cursed setjmp/longjmp that uses __builtin_call_with_static_chain

2022-11-23 Thread gabravier at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107840 Bug ID: 107840 Summary: ICE when compiling cursed setjmp/longjmp that uses __builtin_call_with_static_chain Product: gcc Version: 13.0 Status: UNCONFIRMED Seve

[Bug tree-optimization/106155] [12/13 Regression] spurious "may be used uninitialized" warning

2022-11-23 Thread vincent-gcc at vinc17 dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106155 --- Comment #10 from Vincent Lefèvre --- A similar bug (all uses of the variable are under some condition) with a simpler testcase I've just reported: PR107839.

[Bug tree-optimization/80548] -Wmaybe-uninitialized false positive when an assignment is added

2022-11-23 Thread vincent-gcc at vinc17 dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80548 --- Comment #12 from Vincent Lefèvre --- (In reply to Jeffrey A. Law from comment #11) > As I said in my previous comment, the best way forward is to get those two > new instances filed as distinct bugs in BZ. See PR107838 and PR107839.

[Bug middle-end/107317] [10/11/12/13 Regression] ICE in emit_redzone_byte, at asan.cc:1508

2022-11-23 Thread jakub at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107317 Jakub Jelinek changed: What|Removed |Added Status|NEW |ASSIGNED Assignee|unassigned

[Bug c/107841] New: Incorrect generation of the function's epilogue code when there is a _builtin_alloca call.

2022-11-23 Thread avo2000 at mail dot ru via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107841 Bug ID: 107841 Summary: Incorrect generation of the function's epilogue code when there is a _builtin_alloca call. Product: gcc Version: 12.2.0 Status: UNCONFIRMED

[Bug middle-end/107840] ICE when compiling cursed setjmp/longjmp nested function calls and non-local jumps

2022-11-23 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107840 --- Comment #1 from Andrew Pinski --- I don't think it is directly __builtin_call_with_static_chain but rather the non-local jump causing issues.

[Bug target/107841] Incorrect generation of the function's epilogue code when there is a _builtin_alloca call.

2022-11-23 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107841 --- Comment #1 from Andrew Pinski --- Patches are submitted to gcc-patches@ after reading https://gcc.gnu.org/contribute.html

[Bug c/107831] Missed optimization: -fclash-stack-protection causes unnecessary code generation for dynamic stack allocations that are clearly less than a page

2022-11-23 Thread jakub at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107831 Jakub Jelinek changed: What|Removed |Added CC||jakub at gcc dot gnu.org --- Comment #2

[Bug c/107831] Missed optimization: -fclash-stack-protection causes unnecessary code generation for dynamic stack allocations that are clearly less than a page

2022-11-23 Thread jakub at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107831 Jakub Jelinek changed: What|Removed |Added CC||law at gcc dot gnu.org --- Comment #3 f

[Bug middle-end/107840] ICE when compiling cursed setjmp/longjmp nested function calls and non-local jumps

2022-11-23 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107840 --- Comment #2 from Andrew Pinski --- Created attachment 53955 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53955&action=edit testcase not using C23 features

[Bug middle-end/107840] ICE when compiling cursed setjmp/longjmp nested function calls and non-local jumps

2022-11-23 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107840 --- Comment #3 from Andrew Pinski --- With the testcase that does not use C23 features (which was only implemented in GCC 13), we can get the ICE happening all the way back to at least GCC 6 with -fchecking. GCC 5 didn't have -fchecking so I can

[Bug target/107842] New: [avr] Set --param=min-pagesize=0 in the backend

2022-11-23 Thread gjl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107842 Bug ID: 107842 Summary: [avr] Set --param=min-pagesize=0 in the backend Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component:

[Bug target/107843] New: error: incompatible type for argument in ___bpf_ctx_cast2

2022-11-23 Thread james.hilliard1 at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107843 Bug ID: 107843 Summary: error: incompatible type for argument in ___bpf_ctx_cast2 Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Pri

[Bug c/107831] Missed optimization: -fclash-stack-protection causes unnecessary code generation for dynamic stack allocations that are clearly less than a page

2022-11-23 Thread jakub at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107831 --- Comment #4 from Jakub Jelinek --- Say for void bar (char *); void foo (int x, int y) { __attribute__((assume (x < 64))); for (int i = 0; i < y; ++i) bar (__builtin_alloca (x)); } all the alloca calls are known to be small, yet they c

[Bug target/107844] New: error: argument is not a field access for __builtin_preserve_field_info

2022-11-23 Thread james.hilliard1 at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107844 Bug ID: 107844 Summary: error: argument is not a field access for __builtin_preserve_field_info Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal

[Bug c/107845] New: __builtin_init_trampoline ICEs on invalid arguments

2022-11-23 Thread gabravier at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107845 Bug ID: 107845 Summary: __builtin_init_trampoline ICEs on invalid arguments Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Compone

[Bug target/107846] New: error: result of '8000 << 8' requires 22 bits to represent, but 'short int' only has 16 bits

2022-11-23 Thread james.hilliard1 at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107846 Bug ID: 107846 Summary: error: result of '8000 << 8' requires 22 bits to represent, but 'short int' only has 16 bits Product: gcc Version: 13.0 Status: UNCONFIRMED

[Bug target/107842] [avr] Set --param=min-pagesize=0 in the backend

2022-11-23 Thread gjl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107842 Georg-Johann Lay changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFI

[Bug target/105523] Wrong warning array subscript [0] is outside array bounds

2022-11-23 Thread gjl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105523 Georg-Johann Lay changed: What|Removed |Added CC||gjl at gcc dot gnu.org --- Comment #

[Bug target/107847] New: error: integer overflow in expression in bpf-next test_xdp_vlan.c

2022-11-23 Thread james.hilliard1 at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107847 Bug ID: 107847 Summary: error: integer overflow in expression in bpf-next test_xdp_vlan.c Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal

[Bug target/105523] Wrong warning array subscript [0] is outside array bounds

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

[Bug target/106307] error when I do a test on a pointer on Arduino 1.8.19

2022-11-23 Thread gjl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106307 --- Comment #1 from Georg-Johann Lay --- We'd need at least a test case so we can reproduce th issue. Thanks.

[Bug target/105523] Wrong warning array subscript [0] is outside array bounds

2022-11-23 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105523 --- Comment #9 from Andrew Pinski --- (In reply to rudi from comment #5) > Compiling atf with gcc-12.1.0 for the NXP iMX8 target results in the same > error. > > CFLAGS=+“ --param=min-pagesize=0” allows the build to complete. Yes ATF needs to

[Bug c/107831] Missed optimization: -fclash-stack-protection causes unnecessary code generation for dynamic stack allocations that are clearly less than a page

2022-11-23 Thread law at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107831 --- Comment #5 from Jeffrey A. Law --- Right. You also have to know the distance from the last probe (possibly an implicit one) to the start of the alloca space before you can contemplate eliding the probes in alloca space. There's a hook we c

[Bug libstdc++/104875] libstdc++-v3/src/c++11/codecvt.cc:312:24: warning: left shift count >= width of type

2022-11-23 Thread gjl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104875 --- Comment #3 from Georg-Johann Lay --- Is this fixed now?

[Bug target/105523] Wrong warning array subscript [0] is outside array bounds

2022-11-23 Thread lh_mouse at 126 dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105523 --- Comment #10 from LIU Hao --- (In reply to Andrew Pinski from comment #8) > That inline-asm is not correct and GCC does not understand segments if you > don't use named address space feature. > Named address space is not supported unless a

[Bug tree-optimization/107837] [10/11/12/13 Regression] Missed optimization: Using memcpy to load a struct unnecessary uses stack space

2022-11-23 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107837 Andrew Pinski changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed|

[Bug libstdc++/104875] libstdc++-v3/src/c++11/codecvt.cc:312:24: warning: left shift count >= width of type

2022-11-23 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104875 --- Comment #4 from Jonathan Wakely --- Only for gcc-12 and trunk.

[Bug target/105523] Wrong warning array subscript [0] is outside array bounds

2022-11-23 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105523 --- Comment #11 from Andrew Pinski --- (In reply to LIU Hao from comment #10) > (In reply to Andrew Pinski from comment #8) > > That inline-asm is not correct and GCC does not understand segments if you > > don't use named address space feature.

[Bug c/107127] [11/12/13 Regression] Long compile times on code with C complex since r11-3299-gcba079f354a55363

2022-11-23 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107127 --- Comment #6 from CVS Commits --- The master branch has been updated by Jakub Jelinek : https://gcc.gnu.org/g:8a0fce6a51915c29584427fd376b40073c328090 commit r13-4268-g8a0fce6a51915c29584427fd376b40073c328090 Author: Jakub Jelinek Date: W

[Bug c/107127] [11/12 Regression] Long compile times on code with C complex since r11-3299-gcba079f354a55363

2022-11-23 Thread jakub at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107127 Jakub Jelinek changed: What|Removed |Added Summary|[11/12/13 Regression] Long |[11/12 Regression] Long

[Bug target/105523] Wrong warning array subscript [0] is outside array bounds

2022-11-23 Thread konrad at silmor dot de via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105523 --- Comment #12 from Konrad Rosenbaum --- It would be super helpful if the AVR target (and all its sub-architectures) could have the min-pagesize=0 option(*) set implicitly. This architecture has ONLY firmware - firmware is not special in that a

[Bug middle-end/107845] __builtin_init_trampoline ICEs on invalid arguments

2022-11-23 Thread mpolacek at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107845 Marek Polacek changed: What|Removed |Added CC||mpolacek at gcc dot gnu.org Last reco

[Bug target/107846] error: result of '8000 << 8' requires 22 bits to represent, but 'short int' only has 16 bits

2022-11-23 Thread david.faust at oracle dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107846 --- Comment #1 from David Faust --- I think this is a bug in the test itself (or with these macros from libbpf). libbpf/src/bpf_endian.h #define ___bpf_mvb(x, b, n, m) ((__u##b)(x) << (b-(n+1)*8) >> (b-8) << (m*8)) #define ___bpf_swab16(x) ((_

[Bug fortran/107577] [13 Regression] ICE in find_array_spec, at fortran/resolve.cc:5008 since r13-1757-gf838d15641d256e2

2022-11-23 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107577 --- Comment #4 from CVS Commits --- The master branch has been updated by Harald Anlauf : https://gcc.gnu.org/g:2eaa0cc45e8eae0fc4a440d28c602964bcb1014d commit r13-4269-g2eaa0cc45e8eae0fc4a440d28c602964bcb1014d Author: Steve Kargl Date: Tue

[Bug target/107848] New: libbpf: ELF relo #0 in section #7 has unexpected type 12

2022-11-23 Thread james.hilliard1 at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107848 Bug ID: 107848 Summary: libbpf: ELF relo #0 in section #7 has unexpected type 12 Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Prio

[Bug target/107848] libbpf: ELF relo #0 in section #7 has unexpected type 12

2022-11-23 Thread james.hilliard1 at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107848 --- Comment #1 from James Hilliard --- Working LLVM BTF Dump: $ /home/buildroot/bpf-next/tools/testing/selftests/bpf/tools/sbin/bpftool --debug btf dump file /home/buildroot/bpf-next/tools/testing/selftests/bpf/bpf_dctcp_release.bpf.o format raw

[Bug target/107848] libbpf: ELF relo #0 in section #7 has unexpected type 12

2022-11-23 Thread jose.marchesi at oracle dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107848 --- Comment #2 from Jose E. Marchesi --- This is likely due to the fact they added new BPF relocations: https://reviews.llvm.org/D102712 Or course not bothering telling us.

[Bug target/107846] error: result of '8000 << 8' requires 22 bits to represent, but 'short int' only has 16 bits

2022-11-23 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107846 --- Comment #2 from Andrew Pinski --- (In reply to David Faust from comment #1) > I think this is a bug in the test itself (or with these macros from libbpf). No I think there might be a bug in GCC though I have to double check. cc1: error: res

[Bug c/107846] [13 Regression] error: result of '8000 << 8' requires 22 bits to represent, but 'short int' only has 16 bits

2022-11-23 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107846 Andrew Pinski changed: What|Removed |Added Keywords||diagnostic, needs-bisection Last reco

[Bug c/107846] [13 Regression] error: result of '8000 << 8' requires 22 bits to represent, but 'short int' only has 16 bits

2022-11-23 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107846 --- Comment #4 from Andrew Pinski --- #0 warning_at (location=0, opt=765, gmsgid=0x30ecaf8 "result of %qE requires %u bits to represent, but %qT only has %u bits") at /home/apinski/src/upstream-gcc-git/gcc/gcc/diagnostic.cc:1845 #1 0x0

[Bug analyzer/100705] RFE: warn about dead store

2022-11-23 Thread dmalcolm at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100705 --- Comment #3 from David Malcolm --- See also: PR 80066

[Bug c/107846] [13 Regression] error: result of '8000 << 8' requires 22 bits to represent, but 'short int' only has 16 bits

2022-11-23 Thread jakub at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107846 Jakub Jelinek changed: What|Removed |Added Priority|P3 |P1 CC|

  1   2   >