[Bug tree-optimization/114799] [14 Regression] ICE: tree check: expected class 'type', have 'exceptional' (error_mark) in useless_type_conversion_p, at gimple-expr.cc:85 with -O2 -fno-vect-cost-model

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114799 Jakub Jelinek changed: What|Removed |Added Keywords|needs-bisection | Summary|[14 Regression] ICE

[Bug rtl-optimization/114796] [11/12/13/14 Regression] wrong code at -O2 with "-fno-tree-fre -fno-inline -fselective-scheduling2" on x86_64-linux-gnu

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114796 Jakub Jelinek changed: What|Removed |Added CC||jakub at gcc dot gnu.org Prio

[Bug tree-optimization/114793] [14 Regression] wrong code at -O1 with "-fschedule-insns2 -fselective-scheduling2" on x86_64-linux-gnu (the generated code hangs)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114793 Jakub Jelinek changed: What|Removed |Added CC||jakub at gcc dot gnu.org Prio

[Bug tree-optimization/114792] [14 Regression] ICE on valid code at -O1 with "-fno-tree-ccp -fno-tree-copy-prop" on x86_64-linux-gnu: in get_loop_body, at cfgloop.cc:903

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114792 Jakub Jelinek changed: What|Removed |Added CC||jakub at gcc dot gnu.org Prio

[Bug ipa/114790] [11/12/13/14 regression] ICE when building intel-compute-runtime (error: direct call to ... speculative call sequence has no speculative flag)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114790 Jakub Jelinek changed: What|Removed |Added Target Milestone|--- |11.5 Priority|P3

[Bug rtl-optimization/114788] [13/14 Regression] ICE on valid code at -O{2,3} on x86_64-linux-gnu (during RTL pass: sched2): in move_exprs_to_boundary, at sel-sched.cc:5236

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114788 Jakub Jelinek changed: What|Removed |Added Last reconfirmed||2024-04-22 Target Milestone|---

[Bug c++/114795] internal compiler error: in finish_member_declaration after module import in gcc 14.0.1 snapshot

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114795 --- Comment #4 from porten at kde dot org --- Thanks for the reminder about the workaround. I had once seen it before trying module but did not see the relation when running into problems later. In the small test case, reordering the import and

[Bug tree-optimization/114787] [13/14 Regression] wrong code at -O1 on x86_64-linux-gnu (the generated code hangs)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114787 Jakub Jelinek changed: What|Removed |Added Priority|P1 |P2 Keywords|needs-bisection

[Bug tree-optimization/114787] [13/14 Regression] wrong code at -O1 on x86_64-linux-gnu (the generated code hangs)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114787 --- Comment #8 from Jakub Jelinek --- Seems it is -fdump-tree-profile_estimate-details that changes the code generation.

[Bug tree-optimization/114787] [13/14 Regression] wrong code at -O1 on x86_64-linux-gnu (the generated code hangs)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114787 --- Comment #9 from Jakub Jelinek --- It is the if (dump_file && (dump_flags & TDF_DETAILS) && max_loop_iterations_int (loop) >= 0) { fprintf (dump_file, "Loop %d iterates at most %i times.\n"

[Bug target/85048] [missed optimization] vector conversions

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85048 --- Comment #15 from Matthias Kretz (Vir) --- So it seems that if at least one of the vector builtins involved in the expression is 512 bits GCC needs to locally increase prefer-vector-width to 512? Or, more generally: prefer-vector-width = max(

[Bug tree-optimization/114787] [13/14 Regression] wrong code at -O1 on x86_64-linux-gnu (the generated code hangs)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114787 --- Comment #10 from Andrew Pinski --- I suspect there needs to be a call to free_numbers_of_iterations_estimates somewhere. Maybe it is copyprop, maybe there are a few other missing ones.

[Bug rtl-optimization/114800] New: redundant set-zero when initiate a struct

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114800 Bug ID: 114800 Summary: redundant set-zero when initiate a struct Product: gcc Version: 13.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: rtl-

[Bug c++/93008] Need a way to make inlining heuristics ignore whether a function is inline

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93008 --- Comment #8 from Jan Hubicka --- Note that cold attribute is also quite strong since it turns optimize_size codegen that is often a lot slower. Reading the discussion again, I don't think we have a way to make inline keyword ignored by inline

[Bug c++/93008] Need a way to make inlining heuristics ignore whether a function is inline

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93008 --- Comment #9 from Jonathan Wakely --- Another solution is just to use __builtin_expect or [[likely]] or [[unlikely]] at the call site. That wouldn't need any compiler changes.

[Bug c++/93008] Need a way to make inlining heuristics ignore whether a function is inline

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93008 --- Comment #10 from Jonathan Wakely --- N.B. If you're going to do any more profiling + optimizing of std::vector, please do it with -std=gnu++20 so that everything is constexpr. Otherwise you're only testing C++17 which is the last version befo

[Bug c++/114795] internal compiler error: in finish_member_declaration after module import in gcc 14.0.1 snapshot

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114795 --- Comment #5 from Nathaniel Shead --- Thanks! That error message looks new to me, if you have a reproduction that would be great.

[Bug tree-optimization/114787] [13/14 Regression] wrong code at -O1 on x86_64-linux-gnu (the generated code hangs)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114787 --- Comment #11 from Jakub Jelinek --- Seems it is {,likely_}max_loop_iterations_int on the for (; i < 1; i++) loop which matters (aka loop 3). Given the i = 0 right before it (guess csmith-ism, don't see why it couldn't be in the for init expr

[Bug rtl-optimization/114800] redundant set-zero when initiate a struct

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114800 Xi Ruoyao changed: What|Removed |Added CC||xry111 at gcc dot gnu.org --- Comment #1 fr

[Bug c/114746] With FLT_EVAL_METHOD = 2, -fexcess-precision=fast reduces the precision of floating-point constants and floating-point constant expressions

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114746 --- Comment #4 from Vincent Lefèvre --- I actually find it more confusing the fact that constants are not evaluated in extended precision while everything else is evaluated in extended precision. The real solution to avoid confusion would be to

[Bug target/114676] [12/13/14 Regression] DSE removes assignment that is used later

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114676 --- Comment #16 from Andreas Krebbel --- (In reply to Aleksei Nikiforov from comment #15) > I think fixing compiled code should be possible. I'm not sure if this bug > should be just closed. In addition to fixing the PyTorch usage of the builti

[Bug target/114801] New: [14 Regression] arm: ICE in find_cached_value, at rtx-vector-builder.cc:100 with MVE intrinsics

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114801 Bug ID: 114801 Summary: [14 Regression] arm: ICE in find_cached_value, at rtx-vector-builder.cc:100 with MVE intrinsics Product: gcc Version: 14.0 Status: UNCONFIRMED

[Bug middle-end/114802] New: FAIL: gcc.dg/tree-ssa/forwprop-40.c and forwprop-41.c on s390

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114802 Bug ID: 114802 Summary: FAIL: gcc.dg/tree-ssa/forwprop-40.c and forwprop-41.c on s390 Product: gcc Version: unknown Status: UNCONFIRMED Keywords: missed-optimi

[Bug ipa/114784] [14 Regression] Inlining fails for always_inline inheriting constructor

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114784 Jakub Jelinek changed: What|Removed |Added Status|NEW |ASSIGNED Assignee|unassigned

[Bug target/85048] [missed optimization] vector conversions

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85048 --- Comment #16 from Hongtao Liu --- (In reply to Matthias Kretz (Vir) from comment #15) > So it seems that if at least one of the vector builtins involved in the > expression is 512 bits GCC needs to locally increase prefer-vector-width to > 512

[Bug tree-optimization/114799] [14 Regression] ICE: tree check: expected class 'type', have 'exceptional' (error_mark) in useless_type_conversion_p, at gimple-expr.cc:85 with -O2 -fno-vect-cost-model

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114799 --- Comment #5 from Jakub Jelinek --- _10 is created during pattern recognition: patt_10 = (unsigned short) y.0_1; #0 vect_convert_input (vinfo=0x3a883e0, stmt_info=0x3be5410, type=, unprom=0x7fffcc80, vectype=, subtype=optab_default)

[Bug c/114746] With FLT_EVAL_METHOD = 2, -fexcess-precision=fast reduces the precision of floating-point constants and floating-point constant expressions

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114746 Jakub Jelinek changed: What|Removed |Added CC||jakub at gcc dot gnu.org --- Comment #5

[Bug ipa/114643] [11/12/13/14 Regression] Call to a template function emitted but without the code for the template function itself

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114643 Jakub Jelinek changed: What|Removed |Added CC||jakub at gcc dot gnu.org Last reconfi

[Bug tree-optimization/114787] [13/14 Regression] wrong code at -O1 on x86_64-linux-gnu (the generated code hangs)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114787 Jakub Jelinek changed: What|Removed |Added Priority|P2 |P1 --- Comment #12 from Jakub Jelinek

[Bug libstdc++/114417] std::experimental::simd is not a POD (by ABI definitions) and is always passed by reference instead of by value

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114417 Matthias Kretz (Vir) changed: What|Removed |Added CC||mkretz at gcc dot gnu.org --- Co

[Bug libstdc++/114417] std::experimental::simd is not a POD (by ABI definitions) and is always passed by reference instead of by value

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114417 Matthias Kretz (Vir) changed: What|Removed |Added Resolution|--- |INVALID Status|UNCON

[Bug libstdc++/114750] converting load/store of simd fails compilation on ARM

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114750 --- Comment #2 from Matthias Kretz (Vir) --- Resolved on master. Still need to backport.

[Bug libstdc++/114803] New: simd conversion to [[gnu::vector_size(N)]] type hits invalid code in experimental/bits/simd_builtin.h

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114803 Bug ID: 114803 Summary: simd conversion to [[gnu::vector_size(N)]] type hits invalid code in experimental/bits/simd_builtin.h Product: gcc Version: 14.0 Status: UNCONFIR

[Bug target/114714] [RISC-V][RVV] ICE: insn does not satisfy its constraints (postreload)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114714 Robin Dapp changed: What|Removed |Added CC||rdapp at gcc dot gnu.org --- Comment #5 fr

[Bug libstdc++/114803] simd conversion to [[gnu::vector_size(N)]] type hits invalid code in experimental/bits/simd_builtin.h

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114803 Matthias Kretz (Vir) changed: What|Removed |Added Status|UNCONFIRMED |ASSIGNED Last reconfirmed|

[Bug c++/114804] New: rejects valid code

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114804 Bug ID: 114804 Summary: rejects valid code Product: gcc Version: 13.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: una

[Bug tree-optimization/114787] [13/14 Regression] wrong code at -O1 on x86_64-linux-gnu (the generated code hangs)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114787 --- Comment #13 from Jan Hubicka --- -fdump-tree-all-all changing generated code is also bad. We probably should avoid dumping loop bounds then they are not recorded. I added dumping of loop bounds and this may be unexpected side effect. WIll

[Bug c++/114804] [11/12/13/14 Regression] rejects valid code since r11-6815

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114804 Jakub Jelinek changed: What|Removed |Added CC||jakub at gcc dot gnu.org,

[Bug target/114432] [13 Regression] ICE in connect_traces, at dwarf2cfi.cc:3079 on s390x-linux-gnu

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114432 --- Comment #4 from Stefan Schulze Frielinghaus --- Ignore the previous comment. With -fstack-check and -mbackchain we have for trace 2 an incoming edge from trace 1 (fallthrough) where cur_trace->end_true_args_size == 48 and from further inco

[Bug target/114734] [14] RISC-V rv64gcv_zvl256b miscompile with -flto -O3 -mrvv-vector-bits=zvl

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114734 --- Comment #5 from Robin Dapp --- What happens is that code sinking does: Sinking # VUSE <.MEM_1235> vect__173.251_1238 = .MASK_LEN_LOAD (_911, 32B, { -1, -1, -1, -1 }, loop_len_1064, 0); from bb 3 to bb 4 so we have vect__173.251_1238 = .M

[Bug c++/114805] New: placement new doesn't check array length

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114805 Bug ID: 114805 Summary: placement new doesn't check array length Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++

[Bug c++/114806] New: placement new doesn't check array length

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114806 Bug ID: 114806 Summary: placement new doesn't check array length Product: gcc Version: 13.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++

[Bug c++/114805] placement new doesn't check array length

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114805 Jonathan Wakely changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIR

[Bug c++/114806] placement new doesn't check array length

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114806 --- Comment #1 from Jonathan Wakely --- *** Bug 114805 has been marked as a duplicate of this bug. ***

[Bug c++/114806] placement new doesn't check array length

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114806 Jonathan Wakely changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug c++/99934] bad_array_new_length thrown when non-throwing allocation function would have been used

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99934 Jonathan Wakely changed: What|Removed |Added CC||pshevchuk at pshevchuk dot com --- Com

[Bug target/114801] [14 Regression] arm: ICE in find_cached_value, at rtx-vector-builder.cc:100 with MVE intrinsics

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114801 Christophe Lyon changed: What|Removed |Added Ever confirmed|0 |1 Last reconfirmed|

[Bug modula2/114807] New: badpointer3.mod causes an ICE

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114807 Bug ID: 114807 Summary: badpointer3.mod causes an ICE Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: modula2

[Bug modula2/114807] badpointer3.mod causes an ICE

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114807 Gaius Mulley changed: What|Removed |Added Status|UNCONFIRMED |ASSIGNED Ever confirmed|0

[Bug modula2/114807] badpointer3.mod causes an ICE

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114807 --- Comment #2 from Gaius Mulley --- Created attachment 58009 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=58009&action=edit Proposed fix After the proposed patch fix is applied the cc1gm2 behaviour changes to: $ gm2 -g -c badpointer3.

[Bug analyzer/114778] ICE: in get_region_for_local, at analyzer/region.cc:1366

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114778 --- Comment #1 from David Malcolm --- Thanks for filing this. It's failing this assertion in frame_region::get_region_for_local : 1421case VAR_DECL: 1422 gcc_assert (!is_global_var (expr)); 1423 /* Fall th

[Bug analyzer/106634] [13/14 Regression] ICE in get_region_for_local with nested function extension since r13-2029-g7e3b45befdbbf1a1

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106634 David Malcolm changed: What|Removed |Added CC||iamanonymous.cs at gmail dot com --- C

[Bug analyzer/114778] ICE: in get_region_for_local, at analyzer/region.cc:1366

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114778 David Malcolm changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug c/114808] New: Qualified void return type is not diagnosed

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114808 Bug ID: 114808 Summary: Qualified void return type is not diagnosed Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c

[Bug target/114809] New: [RISC-V RVV] Counting elements might be simpler

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114809 Bug ID: 114809 Summary: [RISC-V RVV] Counting elements might be simpler Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component:

[Bug libstdc++/114417] std::experimental::simd is not a POD (by ABI definitions) and is always passed by reference instead of by value

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114417 --- Comment #11 from Imple Lee --- > What you want to use instead is std::experimental::simd_abi::deduce_t. > That'll give you a not-fixed_size ABI if one exists. And those will likely be > passed via registers (as long as the psABI allows).

[Bug modula2/114807] badpointer3.mod causes an ICE

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114807 --- Comment #3 from GCC Commits --- The master branch has been updated by Gaius Mulley : https://gcc.gnu.org/g:b0469e35dbcc9a93a2cb50e3c0445edc3db174be commit r14-10077-gb0469e35dbcc9a93a2cb50e3c0445edc3db174be Author: Gaius Mulley Date: Mo

[Bug modula2/114807] badpointer3.mod causes an ICE

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114807 Gaius Mulley changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug target/114810] New: [14 Regression] internal compiler error: in lra_split_hard_reg_for, at lra-assigns.cc:1868 (unable to find a register to spill) {*andndi3_doubleword_bmi} with -m32 -mstackrea

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114810 Bug ID: 114810 Summary: [14 Regression] internal compiler error: in lra_split_hard_reg_for, at lra-assigns.cc:1868 (unable to find a register to spill) {*andndi3_d

[Bug target/114810] [14 Regression] internal compiler error: in lra_split_hard_reg_for, at lra-assigns.cc:1868 (unable to find a register to spill) {*andndi3_doubleword_bmi} with -m32 -mstackrealign

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114810 --- Comment #1 from Kostadin Shishmanov --- Created attachment 58011 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=58011&action=edit reduced testcase

[Bug target/114801] [14 Regression] arm: ICE in find_cached_value, at rtx-vector-builder.cc:100 with MVE intrinsics

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114801 Jakub Jelinek changed: What|Removed |Added CC||jakub at gcc dot gnu.org --- Comment #2

[Bug target/114810] [14 Regression] internal compiler error: in lra_split_hard_reg_for, at lra-assigns.cc:1868 (unable to find a register to spill) {*andndi3_doubleword_bmi} with -m32 -mstackrealign

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114810 Jakub Jelinek changed: What|Removed |Added Target Milestone|--- |14.0 Priority|P3

[Bug testsuite/114034] Failure of tests gcov-dump-{1,2}.C

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114034 --- Comment #6 from GCC Commits --- The releases/gcc-12 branch has been updated by Iain D Sandoe : https://gcc.gnu.org/g:6a4824a8bc86fcbcb8f51bab4c24d72ffd00715e commit r12-10385-g6a4824a8bc86fcbcb8f51bab4c24d72ffd00715e Author: Iain Sandoe D

[Bug libstdc++/114803] simd conversion to [[gnu::vector_size(N)]] type hits invalid code in experimental/bits/simd_builtin.h

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114803 --- Comment #1 from GCC Commits --- The master branch has been updated by Matthias Kretz : https://gcc.gnu.org/g:7ef139146a8923a8719873ca3fdae175668e8d63 commit r14-10079-g7ef139146a8923a8719873ca3fdae175668e8d63 Author: Matthias Kretz Date:

[Bug libstdc++/114803] simd conversion to [[gnu::vector_size(N)]] type hits invalid code in experimental/bits/simd_builtin.h

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114803 --- Comment #2 from Matthias Kretz (Vir) --- Fixed in master, still need to backport.

[Bug modula2/114811] New: iso/fail/badexpression.mod and iso/fail/badexpression2.mod ICE

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114811 Bug ID: 114811 Summary: iso/fail/badexpression.mod and iso/fail/badexpression2.mod ICE Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal

[Bug target/114810] [14 Regression] internal compiler error: in lra_split_hard_reg_for, at lra-assigns.cc:1868 (unable to find a register to spill) {*andndi3_doubleword_bmi} with -m32 -mstackrealign

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114810 Uroš Bizjak changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed|

[Bug c/114808] Qualified void return type is not diagnosed

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114808 Jakub Jelinek changed: What|Removed |Added CC||jakub at gcc dot gnu.org --- Comment #1

[Bug tree-optimization/109071] -Warray-bounds false positive warnings due to code duplication from jump threading

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109071 --- Comment #5 from qinzhao at gcc dot gnu.org --- adding __attribute__ ((noreturn)) to the routine "warn" can eliminate the false positive warning.

[Bug c/114808] Qualified void return type is not diagnosed

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114808 --- Comment #2 from Andrew Pinski --- (In reply to Jakub Jelinek from comment #1) > I don't see such a sentence in C++17 nor other C++ standards. It was reported for C, not C++ :). Anyways clang rejects it in C mode (with -pedantic-errors): ``

[Bug modula2/114811] iso/fail/badexpression.mod and iso/fail/badexpression2.mod ICE

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114811 Gaius Mulley changed: What|Removed |Added Ever confirmed|0 |1 Last reconfirmed|

[Bug modula2/114811] iso/fail/badexpression.mod and iso/fail/badexpression2.mod ICE

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114811 --- Comment #1 from Gaius Mulley --- Created attachment 58012 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=58012&action=edit Proposed fix This patch fixes gm2-torture.exp to detect internal compiler error as a negative result and also p

[Bug c/114808] Qualified void return type is not diagnosed

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114808 --- Comment #3 from Jakub Jelinek --- Oops, I'm blind.

[Bug tree-optimization/114785] special handling of COND_EXPR in gimple_extract can be removed

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114785 --- Comment #3 from Richard Biener --- Note there's still code in tree-vect-patterns.cc creating those and code in tree-vect-stmts.cc might use gimple_extract on them.

[Bug tree-optimization/109071] -Warray-bounds false positive warnings due to code duplication from jump threading

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109071 --- Comment #6 from Kees Cook --- (In reply to qinzhao from comment #5) > adding __attribute__ ((noreturn)) to the routine "warn" can eliminate the > false positive warning. But it does return... it's not an assert.

[Bug target/114810] [14 Regression] internal compiler error: in lra_split_hard_reg_for, at lra-assigns.cc:1868 (unable to find a register to spill) {*andndi3_doubleword_bmi} with -m32 -mstackrealign

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114810 --- Comment #4 from Uroš Bizjak --- An interesting observation, when the insn is defined only with problematic alternative: (define_insn_and_split "*andn3_doubleword_bmi" [(set (match_operand: 0 "register_operand" "=&r") (and:

[Bug tree-optimization/114799] [14 Regression] ICE: tree check: expected class 'type', have 'exceptional' (error_mark) in useless_type_conversion_p, at gimple-expr.cc:85 with -O2 -fno-vect-cost-model

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114799 Richard Biener changed: What|Removed |Added Assignee|unassigned at gcc dot gnu.org |rguenth at gcc dot gnu.org

[Bug target/114801] [14 Regression] arm: ICE in find_cached_value, at rtx-vector-builder.cc:100 with MVE intrinsics

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114801 Richard Biener changed: What|Removed |Added Target Milestone|--- |14.0

[Bug rtl-optimization/114810] [14 Regression] internal compiler error: in lra_split_hard_reg_for, at lra-assigns.cc:1868 (unable to find a register to spill) {*andndi3_doubleword_bmi} with -m32 -msta

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114810 Uroš Bizjak changed: What|Removed |Added Keywords||ra Component|target

[Bug c/114808] Qualified void return type is not diagnosed

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114808 Andrew Pinski changed: What|Removed |Added Last reconfirmed||2024-04-22 Ever confirmed|0

[Bug modula2/114811] iso/fail/badexpression.mod and iso/fail/badexpression2.mod ICE

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114811 --- Comment #3 from GCC Commits --- The master branch has been updated by Gaius Mulley : https://gcc.gnu.org/g:b909daa5b67317e46543a7b2ed76e82298645cf6 commit r14-10080-gb909daa5b67317e46543a7b2ed76e82298645cf6 Author: Gaius Mulley Date: Mo

[Bug modula2/114811] iso/fail/badexpression.mod and iso/fail/badexpression2.mod ICE

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114811 Gaius Mulley changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug c/114808] Qualified void return type is not diagnosed

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114808 --- Comment #5 from Halalaluyafail3 --- I made this bug report because of the warning that clang has, but the following paragraph may allow this: > If, in the declaration "T D1", D1 has the form > D ( parameter-type-list ) > or > D ( identifier

[Bug fortran/54389] [F2003/F2008 difference] PURE functions and pointer dummy arguments / DECL_PURE_P issue

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54389 anlauf at gcc dot gnu.org changed: What|Removed |Added Status|NEW |WAITING --- Comment #7 from a

[Bug rtl-optimization/114810] [14 Regression] internal compiler error: in lra_split_hard_reg_for, at lra-assigns.cc:1868 (unable to find a register to spill) {*andndi3_doubleword_bmi} with -m32 -msta

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114810 --- Comment #6 from Vladimir Makarov --- (In reply to Uroš Bizjak from comment #4) > An interesting observation, when the insn is defined only with problematic > alternative: > > (define_insn_and_split "*andn3_doubleword_bmi" > [(set (match_o

[Bug c/114808] Qualified void return type is not diagnosed

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114808 --- Comment #6 from Halalaluyafail3 --- * Paragraph 5 instead of Paragraph 4

[Bug c++/114812] New: Arguments of array type decay to pointer type too eagerly when used as arguments to ref- or ptr-to-function

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114812 Bug ID: 114812 Summary: Arguments of array type decay to pointer type too eagerly when used as arguments to ref- or ptr-to-function Product: gcc Version: 13.2.1

[Bug driver/114813] New: powerpc64: Assembly option -many passed unconditionally, please drop, or make easily configurable

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114813 Bug ID: 114813 Summary: powerpc64: Assembly option -many passed unconditionally, please drop, or make easily configurable Product: gcc Version: 12.2.0

[Bug c/114808] Qualified void return type is not diagnosed

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114808 --- Comment #7 from Joseph S. Myers --- Yes, this is deliberate following the resolution of DR#423 which means qualifiers are ignored on function return types (it's still diagnosed in pre-C11 modes).

[Bug fortran/102597] ICE in gfc_get_extern_function_decl, at fortran/trans-decl.c:2243 since r8-3365-gb89a63b916340ef2

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102597 anlauf at gcc dot gnu.org changed: What|Removed |Added Known to fail||10.5.0, 11.4.1, 12.3.1

[Bug c++/114812] Arguments of array type decay to pointer type too eagerly when used as arguments to ref- or ptr-to-function

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114812 --- Comment #1 from Andrew Pinski --- Maybe a dup of one of the bugs linked from PR 24666.

[Bug target/112868] GCC passes -many to the assembler for --enable-checking=release builds

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112868 Andrew Pinski changed: What|Removed |Added CC||nisse at lysator dot liu.se --- Comment

[Bug driver/114813] powerpc64: Assembly option -many passed unconditionally, please drop, or make easily configurable

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114813 Andrew Pinski changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug tree-optimization/109071] -Warray-bounds false positive warnings due to code duplication from jump threading

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109071 --- Comment #7 from qinzhao at gcc dot gnu.org --- (In reply to Kees Cook from comment #6) > (In reply to qinzhao from comment #5) > > adding __attribute__ ((noreturn)) to the routine "warn" can eliminate the > > false positive warning. > > But

[Bug rtl-optimization/114810] [14 Regression] internal compiler error: in lra_split_hard_reg_for, at lra-assigns.cc:1868 (unable to find a register to spill) {*andndi3_doubleword_bmi} with -m32 -msta

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114810 --- Comment #7 from Uroš Bizjak --- (In reply to Vladimir Makarov from comment #6) > The problem is that the alternative assumes 3 DI values live simultaneously. > This means 6 regs and we have only 6 available ones. One input reg is > assigned

[Bug c/114808] Qualified void return type is not diagnosed

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114808 --- Comment #8 from Andrew Pinski --- https://github.com/llvm/llvm-project/issues/39494 is the clang issue dealing with DR 423 .

[Bug c++/114812] Arguments of array type decay to pointer type too eagerly when used as arguments to ref- or ptr-to-function

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114812 --- Comment #2 from Raymond Kraesig --- (In reply to Andrew Pinski from comment #1) > Maybe a dup of one of the bugs linked from PR 24666. It's none of the open bugs, as far as I can tell. Since it still happens on trunk, I assume it's none of

[Bug tree-optimization/109071] -Warray-bounds false positive warnings due to code duplication from jump threading

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109071 --- Comment #8 from Kees Cook --- The warning is about: val = &sg->vals[index]; poc.c:20:20: warning: array subscript 4 is above array bounds of 'int[4]' [-Warray-bounds=] 20 | val = &sg->vals[index]; |~~~

[Bug translation/66928] Typos in translatable strings

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66928 Abe changed: What|Removed |Added CC||abe_skolnik at yahoo dot com --- Comment #2 from A

[Bug translation/66928] Typos in translatable strings

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66928 --- Comment #3 from Abe --- (In reply to Eric Gallager from comment #1) > are these still there? "No" to all four [please see comment #2, i.e. ].

  1   2   >