[Bug c++/116223] [14/15 Regression] GCC rejects program involving integral conversion in non-type template parameter with auto

2024-08-03 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116223 Andrew Pinski changed: What|Removed |Added Target Milestone|--- |14.3

[Bug other/91085] [11 only] fixincludes breaks

2024-08-03 Thread sjames at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91085 Sam James changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug middle-end/115428] 3 * unused in today's build

2024-08-03 Thread sjames at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115428 Sam James changed: What|Removed |Added See Also||https://gcc.gnu.org/bugzill

[Bug c++/116223] New: GCC rejects program involving integral conversion in non-type template parameter with auto

2024-08-03 Thread jlame646 at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116223 Bug ID: 116223 Summary: GCC rejects program involving integral conversion in non-type template parameter with auto Product: gcc Version: 15.0 Status: UNCONFIRMED

[Bug tree-optimization/106409] GCC with LTO: -Walloc-size-larger-than warning (argument 1 value ‘18...615’ (SIZE_MAX) exceeds maximum object size with new)

2024-08-03 Thread sjames at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106409 Sam James changed: What|Removed |Added Summary|GCC with LTO: Warning: |GCC with LTO: |argument 1

[Bug fortran/116221] -Wmaybe-uninitialized in symbol.cc's gfc_get_ha_symbol

2024-08-03 Thread sjames at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116221 --- Comment #1 from Sam James --- The same issue shows up in a few other places: ``` In function ‘gfc_get_intrinsic_sub_symbol’,

[Bug ipa/116222] New: -Wmaybe-uninitialized in record_target_from_binfo in ipa-devirt.cc

2024-08-03 Thread sjames at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116222 Bug ID: 116222 Summary: -Wmaybe-uninitialized in record_target_from_binfo in ipa-devirt.cc Product: gcc Version: 15.0 Status: UNCONFIRMED Keywords: build

[Bug fortran/116221] New: -Wmaybe-uninitialized in gfc_get_ha_symbol

2024-08-03 Thread sjames at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116221 Bug ID: 116221 Summary: -Wmaybe-uninitialized in gfc_get_ha_symbol Product: gcc Version: 15.0 Status: UNCONFIRMED Keywords: build Severity: normal Priority: P3

[Bug middle-end/116218] -Wformat-overflow in gengtype.cc

2024-08-03 Thread sjames at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116218 --- Comment #1 from Sam James --- All versions I tried fail, although the diagnostic improved between 11 and 12: 11: ``` In file included from /usr/include/stdio.h:970, from /var/tmp/portage/sys-devel/gcc-15.0./work/gcc-15.

[Bug middle-end/116216] [13/14/15 regression] -Wstringop-overread in attribs.cc

2024-08-03 Thread sjames at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116216 Sam James changed: What|Removed |Added Summary|-Wstringop-overread in |[13/14/15 regression] |at

[Bug target/116202] RISC-V: Miscompile at -O3 with zvl256b

2024-08-03 Thread pan2.li at intel dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116202 --- Comment #3 from Li Pan --- (In reply to Li Pan from comment #2) > Confirmed, thanks and will take care of it soon. Just prepared a fix, and will send it out if no surprise from test.

[Bug target/116215] [12/13/14/15 regression] -Wstringop-overflow in i386-expand.cc

2024-08-03 Thread sjames at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116215 Sam James changed: What|Removed |Added Summary|-Wstringop-overflow in |[12/13/14/15 regression]

[Bug middle-end/116219] [14/15 regression] -O3 -march=znver3 -gno-statement-frontiers -fcompare-debug failure when building botan-3.2.0

2024-08-03 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116219 --- Comment #6 from Andrew Pinski --- interesting, removing the line markers cause the compare debug to go away.

[Bug tree-optimization/116213] [14/15 regression] -Wmaybe-uninitialized in tree-ssa-loop-niter.cc

2024-08-03 Thread sjames at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116213 Sam James changed: What|Removed |Added Summary|-Wmaybe-uninitialized in|[14/15 regression] |tree-

[Bug tree-optimization/116213] -Wmaybe-uninitialized in tree-ssa-loop-niter.cc

2024-08-03 Thread sjames at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116213 --- Comment #1 from Sam James --- Created attachment 58818 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=58818&action=edit attempted-reduction.ii

[Bug middle-end/116219] [14/15 regression] -O3 -march=znver3 -gno-statement-frontiers -fcompare-debug failure when building botan-3.2.0

2024-08-03 Thread sjames at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116219 --- Comment #5 from Sam James --- I'm trying to reduce it but it's pretty slow going.

[Bug lto/116220] -Wmaybe-uninitialised in lto_obj_begin_section

2024-08-03 Thread sjames at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116220 --- Comment #1 from Sam James --- Am I missing something here? libiberty's simple_object_elf_copy_lto_debug_sections also does: ``` dest = simple_object_write_create_section (dobj, pfnname[i - 1],

[Bug lto/116220] New: -Wmaybe-uninitialised in lto_obj_begin_section

2024-08-03 Thread sjames at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116220 Bug ID: 116220 Summary: -Wmaybe-uninitialised in lto_obj_begin_section Product: gcc Version: 15.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: l

[Bug middle-end/116219] [14/15 regression] -O3 -march=znver3 -gno-statement-frontiers -fcompare-debug failure when building botan-3.2.0

2024-08-03 Thread sjames at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116219 --- Comment #4 from Sam James --- ah, sorry

[Bug middle-end/116219] [14/15 regression] -O3 -march=znver3 -gno-statement-frontiers -fcompare-debug failure when building botan-3.2.0

2024-08-03 Thread sjames at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116219 --- Comment #3 from Sam James --- It's at r15-2707-g8256d5c0097dff but I was also still using -fno-tree-forwprop when I hit it. (I'll drop that from my build flags now for the compare-debug stuff.)

[Bug middle-end/116219] [14/15 regression] -O3 -march=znver3 -gno-statement-frontiers -fcompare-debug failure when building botan-3.2.0

2024-08-03 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116219 --- Comment #2 from Andrew Pinski --- Oh there was a mismatch between the summary and comment #0, `-O3` should be used.

[Bug middle-end/116219] [14/15 regression] -O2 -march=znver3 -gno-statement-frontiers -fcompare-debug failure when building botan-3.2.0

2024-08-03 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116219 --- Comment #1 from Andrew Pinski --- was this before or after r15-2691-g33baa20c5cdcf5 ?

[Bug middle-end/116219] New: [14/15 regression] -O2 -march=znver3 -gno-statement-frontiers -fcompare-debug failure when building botan-3.2.0

2024-08-03 Thread sjames at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116219 Bug ID: 116219 Summary: [14/15 regression] -O2 -march=znver3 -gno-statement-frontiers -fcompare-debug failure when building botan-3.2.0 Product: gcc Version: 15.

[Bug middle-end/116218] New: -Wformat-overflow in gengtype.cc

2024-08-03 Thread sjames at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116218 Bug ID: 116218 Summary: -Wformat-overflow in gengtype.cc Product: gcc Version: 15.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: middle-end

[Bug middle-end/116216] New: -Wstringop-overread in attribs.cc

2024-08-03 Thread sjames at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116216 Bug ID: 116216 Summary: -Wstringop-overread in attribs.cc Product: gcc Version: 15.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: middle-end

[Bug libstdc++/116217] New: RangeAdaptorClosure pipe operator is underconstrained

2024-08-03 Thread eddiejnolan at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116217 Bug ID: 116217 Summary: RangeAdaptorClosure pipe operator is underconstrained Product: gcc Version: 14.1.0 Status: UNCONFIRMED Severity: normal Priority: P3 Com

[Bug middle-end/107743] expmed: extract_bit_field_1: maybe-uninitialized warning

2024-08-03 Thread sjames at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107743 Sam James changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever confirmed|0

[Bug middle-end/107743] expmed: extract_bit_field_1: maybe-uninitialized warning

2024-08-03 Thread sjames at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107743 Sam James changed: What|Removed |Added CC||sjames at gcc dot gnu.org --- Comment #3 fr

[Bug target/116202] RISC-V: Miscompile at -O3 with zvl256b

2024-08-03 Thread pan2.li at intel dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116202 --- Comment #2 from Li Pan --- Confirmed, thanks and will take care of it soon.

[Bug target/116215] New: -Wstringop-overflow in i386-expand.cc

2024-08-03 Thread sjames at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116215 Bug ID: 116215 Summary: -Wstringop-overflow in i386-expand.cc Product: gcc Version: 15.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target

[Bug tree-optimization/116214] New: -Wmaybe-uninitialized in tree-vect-stmts.cc

2024-08-03 Thread sjames at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116214 Bug ID: 116214 Summary: -Wmaybe-uninitialized in tree-vect-stmts.cc Product: gcc Version: 15.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: tree

[Bug tree-optimization/116213] New: -Wmaybe-uninitialized in tree-ssa-loop-niter.cc

2024-08-03 Thread sjames at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116213 Bug ID: 116213 Summary: -Wmaybe-uninitialized in tree-ssa-loop-niter.cc Product: gcc Version: 15.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component:

[Bug middle-end/116211] C Functions returning a struct always manipulate the stack pointer on RISC-V targets

2024-08-03 Thread gr.audio at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116211 --- Comment #4 from Guillaume --- OK thanks!

[Bug middle-end/116211] C Functions returning a struct always manipulate the stack pointer on RISC-V targets

2024-08-03 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116211 Andrew Pinski changed: What|Removed |Added Target||Riscv Severity|normal

[Bug middle-end/116211] C Functions returning a struct always manipulate the stack pointer on RISC-V targets

2024-08-03 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116211 --- Comment #3 from Andrew Pinski --- Well x86_64 has a redzone by default so if the stack usage is small enough, there would be no incremental of the stack there. Try on aarch64 or mips or powerpc, you will see the same issue. This is a known

[Bug libstdc++/116212] New: [13/14/15 regression] -Walloc-size-larger-than warning when building 20_util/specialized_algorithms/uninitialized_move/constrained.cc with -O3

2024-08-03 Thread sjames at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116212 Bug ID: 116212 Summary: [13/14/15 regression] -Walloc-size-larger-than warning when building 20_util/specialized_algorithms/uninitialized_move/cons trained.cc with

[Bug middle-end/116211] C Functions returning a struct always manipulate the stack pointer on RISC-V targets

2024-08-03 Thread gr.audio at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116211 --- Comment #2 from Guillaume --- Hi, thanks. Yes it looks like it, but I could not reproduce this exact problem with x86_64. Maybe present for other targets though.

[Bug middle-end/116211] C Functions returning a struct always manipulate the stack pointer on RISC-V targets

2024-08-03 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116211 --- Comment #1 from Andrew Pinski --- This is most likely a dup of the other bug.

[Bug c/116211] New: C Functions returning a struct always manipulate the stack pointer on RISC-V targets

2024-08-03 Thread gr.audio at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116211 Bug ID: 116211 Summary: C Functions returning a struct always manipulate the stack pointer on RISC-V targets Product: gcc Version: 14.1.1 Status: UNCONFIRMED S

[Bug libstdc++/116210] 17_intro/names.cc test fails with >=glibc-2.35 and _FORTIFY_SOURCE

2024-08-03 Thread sjames at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116210 Sam James changed: What|Removed |Added CC||siddhesh at gcc dot gnu.org Keywo

[Bug libstdc++/116210] 17_intro/names.cc test fails

2024-08-03 Thread sjames at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116210 --- Comment #2 from Sam James --- This probably only shows up with _FORTIFY_SOURCE.

[Bug libstdc++/116210] 17_intro/names.cc test fails

2024-08-03 Thread sjames at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116210 --- Comment #1 from Sam James --- stdlib.h:46 for me is: ``` __fortify_function __attribute_overloadable__ __wur char * __NTH (realpath (const char *__restrict __name, __fortify_clang_overload_arg (char *, __restrict, __resolved

[Bug libstdc++/116210] New: 17_intro/names.cc test fails

2024-08-03 Thread sjames at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116210 Bug ID: 116210 Summary: 17_intro/names.cc test fails Product: gcc Version: 15.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libstdc++

[Bug go/85629] GCC 8.1.0: FTBFS: make check fails in Go part

2024-08-03 Thread ian at airs dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85629 Ian Lance Taylor changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug tree-optimization/116209] range_op_table/operator_table should become a final singleton class

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

[Bug tree-optimization/116209] New: range_op_table/operator_table should become a final singleton class

2024-08-03 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116209 Bug ID: 116209 Summary: range_op_table/operator_table should become a final singleton class Product: gcc Version: 15.0 Status: UNCONFIRMED Keywords: internal-i

[Bug c++/116208] "inlined from" diagnostic note has whitespace after function name

2024-08-03 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116208 --- Comment #6 from Andrew Pinski --- Note without LTO we get the correct function name.

[Bug c++/116208] "inlined from" diagnostic note has whitespace after function name

2024-08-03 Thread sjames at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116208 --- Comment #5 from Sam James --- Pretty sure yes.

[Bug c++/116208] "inlined from" diagnostic note has whitespace after function name

2024-08-03 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116208 --- Comment #4 from Andrew Pinski --- Does this show up only with LTO?

[Bug c++/116208] "inlined from" diagnostic note has whitespace after function name

2024-08-03 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116208 --- Comment #3 from Andrew Pinski --- Note the fix for the warning should be: range_operator *m_range_tree[RANGE_OP_TABLE_SIZE]{}; in range-op.h. That is value initialize m_range_tree which was not done before hand.

[Bug c++/116208] "inlined from" diagnostic note has whitespace after function name

2024-08-03 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116208 Andrew Pinski changed: What|Removed |Added Component|middle-end |c++ --- Comment #2 from Andrew Pinski

[Bug middle-end/116208] "inlined from" diagnostic note has whitespace after function name

2024-08-03 Thread sjames at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116208 --- Comment #1 from Sam James --- Oh! $ rg __ct_base gcc/cp/decl.cc:4782:{"__ct_base ", &base_ctor_identifier, cik_ctor},

[Bug middle-end/116208] New: "inlined from" diagnostic note has whitespace after function name

2024-08-03 Thread sjames at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116208 Bug ID: 116208 Summary: "inlined from" diagnostic note has whitespace after function name Product: gcc Version: 15.0 Status: UNCONFIRMED Keywords: diagnostic

[Bug testsuite/116207] gcc.target/aarch64/simd/vmmla.c is broken (started being tested with r15-2414-g2d105efd6f60)

2024-08-03 Thread sjames at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116207 --- Comment #5 from Sam James --- (In reply to Andrew Pinski from comment #4) > -save-temps is used in others. Ah, thanks. There's a bunch of other dubious tests too then. Need to check (some may be OK if .exp sets stuff up fine, some are also

[Bug testsuite/116207] gcc.target/aarch64/simd/vmmla.c is broken (started being tested with r15-2414-g2d105efd6f60)

2024-08-03 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116207 --- Comment #4 from Andrew Pinski --- -save-temps is used in others.

[Bug testsuite/116207] gcc.target/aarch64/simd/vmmla.c is broken (started being tested with r15-2414-g2d105efd6f60)

2024-08-03 Thread sjames at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116207 --- Comment #3 from Sam James --- (In reply to Sam James from comment #2) > I think we want dg-do compile here. It looks like scan-assembler-times > doesn't work with dg-do assemble? No, this is wrong, other testcases do it fine.

[Bug testsuite/116207] gcc.target/aarch64/simd/vmmla.c is broken (started being tested with r15-2414-g2d105efd6f60)

2024-08-03 Thread sjames at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116207 --- Comment #2 from Sam James --- >From the logs: ``` PASS: gcc.target/aarch64/simd/vmmla.c (test for excess errors) gcc.target/aarch64/simd/vmmla.c: output file does not exist UNRESOLVED: gcc.target/aarch64/simd/vmmla.c scan-assembler-times \\t

[Bug testsuite/116207] gcc.target/aarch64/simd/vmmla.c is broken (started being tested with r15-2414-g2d105efd6f60)

2024-08-03 Thread sjames at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116207 --- Comment #1 from Sam James --- Running gcc:gcc.target/aarch64/simd/simd.exp ... UNRESOLVED: gcc.target/aarch64/simd/vmmla.c scan-assembler-times \\tsmmla\\tv[0-9]+.4s, v[0-9]+.16b, v[0-9]+.16b 1 UNRESOLVED: gcc.target/aarch64/simd/vmmla.c s

[Bug testsuite/116207] New: gcc.target/aarch64/simd/vmmla.c is broken (started being tested with r15-2414-g2d105efd6f60)

2024-08-03 Thread sjames at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116207 Bug ID: 116207 Summary: gcc.target/aarch64/simd/vmmla.c is broken (started being tested with r15-2414-g2d105efd6f60) Product: gcc Version: 15.0 Status: UNCONFIRMED

[Bug middle-end/85237] missed optimisation opportunity for large/negative shifts

2024-08-03 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85237 Andrew Pinski changed: What|Removed |Added CC||pinskia at gcc dot gnu.org --- Comment #

[Bug middle-end/82705] Missing tail calls for large structs

2024-08-03 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82705 Andrew Pinski changed: What|Removed |Added CC||pinskia at gcc dot gnu.org --- Comment #

[Bug middle-end/115607] missed tail call with large structure size

2024-08-03 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115607 Andrew Pinski changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRME

[Bug target/116202] RISC-V: Miscompile at -O3 with zvl256b

2024-08-03 Thread rdapp at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116202 Robin Dapp changed: What|Removed |Added CC||pan2.li at intel dot com --- Comment #1 fr

[Bug c++/113755] an implicit deconstructor is (incorrectly) added when the requires of the deconstructor fails

2024-08-03 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113755 Andrew Pinski changed: What|Removed |Added CC||mital at mitalashok dot co.uk --- Comme

[Bug c++/116206] No failure when all C++20 prospective destructors are not viable when templated class definition is instantiated

2024-08-03 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116206 Andrew Pinski changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRME

[Bug target/116007] libquadmath fails to build with libgcc/soft-fp/quad.h:69:1: error: unable to emulate 'TF'

2024-08-03 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116007 --- Comment #19 from GCC Commits --- The master branch has been updated by Jakub Jelinek : https://gcc.gnu.org/g:3ac02e67503ccffa3dfeeffc0a60fce6bdaca43b commit r15-2708-g3ac02e67503ccffa3dfeeffc0a60fce6bdaca43b Author: Jakub Jelinek Date:

[Bug testsuite/91437] Problem with multi-line test outputs on x86_64-w64-mingw32

2024-08-03 Thread egallager at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91437 Eric Gallager changed: What|Removed |Added Keywords||diagnostic CC|

[Bug testsuite/90481] Unclean DejaGnu global state after ERROR in one '*.exp' file

2024-08-03 Thread egallager at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90481 Eric Gallager changed: What|Removed |Added CC||egallager at gcc dot gnu.org --- Comment

[Bug testsuite/71931] build sysroot flags are not passed to target lib tests

2024-08-03 Thread egallager at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71931 Eric Gallager changed: What|Removed |Added CC||egallager at gcc dot gnu.org S

[Bug testsuite/53222] dejagnu trims leading whitespace

2024-08-03 Thread egallager at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53222 Eric Gallager changed: What|Removed |Added CC||dmalcolm at gcc dot gnu.org,

[Bug go/56017] libgo testsuite log and summary file only contain a single test run (the last one)

2024-08-03 Thread egallager at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56017 Eric Gallager changed: What|Removed |Added CC||egallager at gcc dot gnu.org S

[Bug testsuite/53028] add dg-pedantic

2024-08-03 Thread egallager at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53028 Eric Gallager changed: What|Removed |Added CC||egallager at gcc dot gnu.org --- Comment

[Bug c++/116206] New: No failure when all C++20 prospective destructors are not viable when templated class definition is instantiated

2024-08-03 Thread mital at mitalashok dot co.uk via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116206 Bug ID: 116206 Summary: No failure when all C++20 prospective destructors are not viable when templated class definition is instantiated Product: gcc Version: 15

[Bug target/116007] libquadmath fails to build with libgcc/soft-fp/quad.h:69:1: error: unable to emulate 'TF'

2024-08-03 Thread bergner at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116007 --- Comment #18 from Peter Bergner --- (In reply to Segher Boessenkool from comment #17) > Does it also work if you spell the option name correctly? All unknown > configure > options are always accepted silently. Sorry, it was a typo here, not

[Bug sanitizer/116203] libsanitizer fails to build for aarch64 with __NR_newfstatat was not declared in this scope

2024-08-03 Thread rudi at heitbaum dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116203 --- Comment #7 from rudi at heitbaum dot com --- Hi Andrew, I tested the fix. Not yet. https://lore.kernel.org/all/Zq28wejX3U9J1_JV@faede8dcc269/