[Bug tree-optimization/106867] New: [13 Regression] ICE in set, at value-range.cc:372

2022-09-06 Thread asolokha at gmx dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106867 Bug ID: 106867 Summary: [13 Regression] ICE in set, at value-range.cc:372 Product: gcc Version: 13.0 Status: UNCONFIRMED Keywords: ice-on-valid-code Severity: normal

[Bug middle-end/106833] Miss to handle OPAQUE_TYPE specially in verify_type

2022-09-06 Thread linkw at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106833 --- Comment #11 from Kewen Lin --- One modified case from pr102347.c (same option set is used), which can reproduce the ICE without any gcc source adjustment. #pragma GCC target "cpu=power10" int main () { float *b; const __vector_quad c;

[Bug middle-end/106833] Handle OPAQUE_TYPE in gimple_canonical_types_compatible_p

2022-09-06 Thread linkw at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106833 --- Comment #10 from Kewen Lin --- (In reply to Segher Boessenkool from comment #9) > Although, preferably we should not allow assigning one opaque type to another > opaque type just because they will eventually use the same mode, not without >

[Bug tree-optimization/106866] New: [13 Regression] ICE in predicate::init_from_control_deps

2022-09-06 Thread asolokha at gmx dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106866 Bug ID: 106866 Summary: [13 Regression] ICE in predicate::init_from_control_deps Product: gcc Version: 13.0 Status: UNCONFIRMED Keywords: ice-on-valid-code

[Bug tree-optimization/106865] addcarry pattern

2022-09-06 Thread unlvsur at live dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106865 --- Comment #2 from cqwrteur --- template inline constexpr T add_carry(T a,T b,T carryin,T& carryout) noexcept { a+=b; carryout=a inline constexpr T sub_carry(T a,T b,T carryin,T& carryout) noexcept { a-=b;

[Bug testsuite/106345] Some ppc64le tests fail with -mcpu=power9 -mtune=power9

2022-09-06 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106345 --- Comment #10 from CVS Commits --- The master branch has been updated by Kewen Lin : https://gcc.gnu.org/g:7a43e52a48b6403a99d3e8ab3105869b4b3c081e commit r13-2504-g7a43e52a48b6403a99d3e8ab3105869b4b3c081e Author: Kewen Lin Date: Tue Sep

[Bug c/106830] [13 Regression] ICE: in tree_to_uhwi, at tree.cc:6392 (from check_for_xor_used_as_pow) since r13-2386-gbedfca647a9e9c1a

2022-09-06 Thread dmalcolm at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106830 David Malcolm changed: What|Removed |Added Status|ASSIGNED|WAITING Keywords|

[Bug tree-optimization/53947] [meta-bug] vectorizer missed-optimizations

2022-09-06 Thread crazylht at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53947 Bug 53947 depends on bug 103144, which changed state. Bug 103144 Summary: vectorizer failed to recognize shift>>=1 in loop as shift>>i https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103144 What|Removed |Added

[Bug tree-optimization/103144] vectorizer failed to recognize shift>>=1 in loop as shift>>i

2022-09-06 Thread crazylht at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103144 Hongtao.liu changed: What|Removed |Added Resolution|--- |FIXED Status|NEW

[Bug tree-optimization/103144] vectorizer failed to recognize shift>>=1 in loop as shift>>i

2022-09-06 Thread crazylht at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103144 --- Comment #6 from Hongtao.liu --- Fixed in GCC13.

[Bug tree-optimization/103144] vectorizer failed to recognize shift>>=1 in loop as shift>>i

2022-09-06 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103144 --- Comment #5 from CVS Commits --- The master branch has been updated by hongtao Liu : https://gcc.gnu.org/g:c13223b790bbc5e4a3f5605e057eac59b61b2c85 commit r13-2503-gc13223b790bbc5e4a3f5605e057eac59b61b2c85 Author: liuhongt Date: Thu Aug

[Bug target/55522] -funsafe-math-optimizations is unexpectedly harmful, especially w/ -shared

2022-09-06 Thread sam at gentoo dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55522 --- Comment #14 from Sam James --- (In reply to Andrew Pinski from comment #13) > Patient: Doctor it hurts when I do this. > Doctor: then don't do that and if you read the instructions I gave you I > told you I would hurt this way. > This

[Bug target/55522] -funsafe-math-optimizations is unexpectedly harmful, especially w/ -shared

2022-09-06 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55522 --- Comment #13 from Andrew Pinski --- Patient: Doctor it hurts when I do this. Doctor: then don't do that and if you read the instructions I gave you I told you I would hurt this way. Note I think it was a mistake that gcc had -ffast-math

[Bug analyzer/106854] [[gnu::malloc(deallocator)]] for non-pointer functions (e.g., fd)

2022-09-06 Thread colomar.6.4.3 at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106854 --- Comment #6 from Alejandro Colomar --- timerfd_create() might not be important if the timer is not correctly deleted. pthread_mutex_init() is another one that is quite more important, as leaking such a thing in a multithreaded program will

[Bug target/55522] -funsafe-math-optimizations is unexpectedly harmful, especially w/ -shared

2022-09-06 Thread foom at fuhm dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55522 James Y Knight changed: What|Removed |Added CC||foom at fuhm dot net --- Comment #12

[Bug target/106574] gcc 12 with O3 leads to failures in glibc's y1f128 tests

2022-09-06 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106574 Andrew Pinski changed: What|Removed |Added Resolution|INVALID |MOVED

[Bug target/106574] gcc 12 with O3 leads to failures in glibc's y1f128 tests

2022-09-06 Thread michael.hudson at canonical dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106574 Michael Hudson-Doyle changed: What|Removed |Added Resolution|--- |INVALID

[Bug middle-end/104151] [10/11/12/13 Regression] x86: excessive code generated for 128-bit byteswap

2022-09-06 Thread pobrn at protonmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104151 Barnabás Pőcze changed: What|Removed |Added CC||pobrn at protonmail dot com ---

[Bug c/106835] [i386] Taking an address of _GLOBAL_OFFSET_TABLE_ produces a wrong value

2022-09-06 Thread hjl.tools at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106835 --- Comment #8 from H.J. Lu --- GCC generates _GLOBAL_OFFSET_TABLE_ to indicate GOTPC32 relocation. It can't be treated as a normal symbol.

[Bug tree-optimization/106862] ice in compute_control_dep_chain, at gimple-predicate-analysis.cc:1105

2022-09-06 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106862 --- Comment #2 from David Binderman --- Reduced C++ code seems to be: extern fprintf(char); struct string { string(char); }; struct { call(); replace(string); } vsllib; struct ListNode { ListNode(); }; struct TestNode {

[Bug middle-end/106833] Handle OPAQUE_TYPE in gimple_canonical_types_compatible_p

2022-09-06 Thread segher at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106833 --- Comment #9 from Segher Boessenkool --- Although, preferably we should not allow assigning one opaque type to another opaque type just because they will eventually use the same mode, not without warning anyway? Or is that unavoidable?

[Bug tree-optimization/106865] addcarry pattern

2022-09-06 Thread unlvsur at live dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106865 cqwrteur changed: What|Removed |Added CC||unlvsur at live dot com --- Comment #1 from

[Bug tree-optimization/106865] New: addcarry pattern

2022-09-06 Thread unlvsur at live dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106865 Bug ID: 106865 Summary: addcarry pattern Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: tree-optimization

[Bug c++/106864] New: Unexpected capture of "constexpr int" variable inside lambda

2022-09-06 Thread a.elovikov at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106864 Bug ID: 106864 Summary: Unexpected capture of "constexpr int" variable inside lambda Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal

[Bug c++/106863] New: internal compiler error: in write_template_arg_literal, at cp/mangle.cc:3678

2022-09-06 Thread jehova at existiert dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106863 Bug ID: 106863 Summary: internal compiler error: in write_template_arg_literal, at cp/mangle.cc:3678 Product: gcc Version: 12.2.0 Status: UNCONFIRMED

[Bug fortran/106857] [10/11/12/13 Regression] ICE in gfc_simplify_pack, at fortran/simplify.cc:6438

2022-09-06 Thread anlauf at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106857 anlauf at gcc dot gnu.org changed: What|Removed |Added Status|UNCONFIRMED |NEW CC|

[Bug analyzer/106854] [[gnu::malloc(deallocator)]] for non-pointer functions (e.g., fd)

2022-09-06 Thread colomar.6.4.3 at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106854 --- Comment #5 from Alejandro Colomar --- We could also keep the old [[gnu::malloc(...)]] attribute, of course, if a new attribute would be an issue. We would just have to add an extra argument (the third?, or one before the function name?) to

[Bug analyzer/106854] [[gnu::malloc(deallocator)]] for non-pointer functions (e.g., fd)

2022-09-06 Thread colomar.6.4.3 at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106854 --- Comment #4 from Alejandro Colomar --- Hi David, I was missing that this is to be introduced in GCC 13, which of course I still don't have; but thanks! It'll be a great improvement. Still, this doesn't seem to cover all cases. See for

[Bug analyzer/106854] [[gnu::malloc(deallocator)]] for non-pointer functions (e.g., fd)

2022-09-06 Thread dmalcolm at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106854 David Malcolm changed: What|Removed |Added CC||mir at gcc dot gnu.org --- Comment #3

[Bug tree-optimization/106862] ice in compute_control_dep_chain, at gimple-predicate-analysis.cc:1105

2022-09-06 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106862 --- Comment #1 from David Binderman --- I have a cvise reduction running. The code is in C++, which cvise isn't very efficient at reducing, so I expect it will be some hours before I have any finished reduction.

[Bug target/106834] GCC creates R_X86_64_GOTOFF64 for 4-bytes immediate

2022-09-06 Thread hjl.tools at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106834 --- Comment #12 from H.J. Lu --- We can't use movq_GLOBAL_OFFSET_TABLE_@GOTPCREL(%rip), %rax to get the address of _GLOBAL_OFFSET_TABLE_ since there is no entry for _GLOBAL_OFFSET_TABLE_ in GOT. We can't use movl $_GLOBAL_OFFSET_TABLE_,

[Bug c++/106862] New: ice in compute_control_dep_chain, at gimple-predicate-analysis.cc:1105

2022-09-06 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106862 Bug ID: 106862 Summary: ice in compute_control_dep_chain, at gimple-predicate-analysis.cc:1105 Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal

[Bug c/106861] New: [12/13 Regression] ICE in add_cfi_args_size, at dwarf2cfi.cc:501

2022-09-06 Thread gscfq--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106861 Bug ID: 106861 Summary: [12/13 Regression] ICE in add_cfi_args_size, at dwarf2cfi.cc:501 Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal

[Bug c/106860] New: [12/13 Regression] ICE in single_pred_edge, at basic-block.h:347

2022-09-06 Thread gscfq--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106860 Bug ID: 106860 Summary: [12/13 Regression] ICE in single_pred_edge, at basic-block.h:347 Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal

[Bug c/106859] New: [10/11/12/13 Regression] ICE in val_store, at var-tracking.cc:2532

2022-09-06 Thread gscfq--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106859 Bug ID: 106859 Summary: [10/11/12/13 Regression] ICE in val_store, at var-tracking.cc:2532 Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal

[Bug c++/106858] New: [12/13 Regression] ICE: tree check: expected tree that contains 'decl common' structure, have 'baselink' in cp_ubsan_maybe_instrument_member_access, at cp/cp-ubsan.cc:172

2022-09-06 Thread gscfq--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106858 Bug ID: 106858 Summary: [12/13 Regression] ICE: tree check: expected tree that contains 'decl common' structure, have 'baselink' in cp_ubsan_maybe_instrument_member_access, at

[Bug fortran/106857] New: [10/11/12/13 Regression] ICE in gfc_simplify_pack, at fortran/simplify.cc:6438

2022-09-06 Thread gscfq--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106857 Bug ID: 106857 Summary: [10/11/12/13 Regression] ICE in gfc_simplify_pack, at fortran/simplify.cc:6438 Product: gcc Version: 13.0 Status: UNCONFIRMED

[Bug fortran/106856] New: [12/13 Regression] ICE in gfc_conv_expr_present, at fortran/trans-expr.cc:1977

2022-09-06 Thread gscfq--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106856 Bug ID: 106856 Summary: [12/13 Regression] ICE in gfc_conv_expr_present, at fortran/trans-expr.cc:1977 Product: gcc Version: 13.0 Status: UNCONFIRMED

[Bug bootstrap/106855] [13 Regression] Removal of stabs/xcoff debugging broke bootstrap on AIX

2022-09-06 Thread dje at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106855 --- Comment #2 from David Edelsohn --- dwarf2out.cc uses XCOFF_DEBUGGING_INFO to emit DWARF information with XCOFF syntax.

[Bug bootstrap/106855] [13 Regression] Removal of stabs/xcoff debugging broke bootstrap on AIX

2022-09-06 Thread dje at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106855 David Edelsohn changed: What|Removed |Added Ever confirmed|0 |1 Last reconfirmed|

[Bug bootstrap/106855] New: [13 Regression] Removal of stabs/xcoff debugging broke bootstrap on AIX

2022-09-06 Thread dje at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106855 Bug ID: 106855 Summary: [13 Regression] Removal of stabs/xcoff debugging broke bootstrap on AIX Product: gcc Version: unknown Status: UNCONFIRMED Severity:

[Bug c/106830] [13 Regression] ICE: in tree_to_uhwi, at tree.cc:6392 (from check_for_xor_used_as_pow) since r13-2386-gbedfca647a9e9c1a

2022-09-06 Thread dmalcolm at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106830 David Malcolm changed: What|Removed |Added Assignee|unassigned at gcc dot gnu.org |dmalcolm at gcc dot gnu.org

[Bug c/106835] [i386] Taking an address of _GLOBAL_OFFSET_TABLE_ produces a wrong value

2022-09-06 Thread hjl.tools at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106835 H.J. Lu changed: What|Removed |Added See Also||https://sourceware.org/bugz

[Bug target/106834] GCC creates R_X86_64_GOTOFF64 for 4-bytes immediate

2022-09-06 Thread hjl.tools at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106834 H.J. Lu changed: What|Removed |Added See Also||https://sourceware.org/bugz

[Bug analyzer/106854] [[gnu::malloc(deallocator)]] for non-pointer functions (e.g., fd)

2022-09-06 Thread colomar.6.4.3 at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106854 --- Comment #2 from Alejandro Colomar --- Also interesting might be that one function might have more than one closer. For example, open(2) might be closed by close(2), but it is also closed by fdopen(3), in the sense that the file descriptor

[Bug analyzer/106845] [13 Regression] ICE in exceeds_p, at analyzer/store.cc:464 since r13-2029-g7e3b45befdbbf1a1

2022-09-06 Thread tlange at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106845 Tim Lange changed: What|Removed |Added Assignee|dmalcolm at gcc dot gnu.org|tlange at gcc dot gnu.org

[Bug analyzer/106845] [13 Regression] ICE in exceeds_p, at analyzer/store.cc:464 since r13-2029-g7e3b45befdbbf1a1

2022-09-06 Thread dmalcolm at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106845 --- Comment #4 from David Malcolm --- (In reply to Tim Lange from comment #3) > It seems to me that the implementations of byte_range/bit_range > get_last_byte_offset () already assume that m_size_in_bytes should be > greater than zero. So I

[Bug analyzer/106845] [13 Regression] ICE in exceeds_p, at analyzer/store.cc:464 since r13-2029-g7e3b45befdbbf1a1

2022-09-06 Thread tlange at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106845 --- Comment #3 from Tim Lange --- Thanks for the report! (In reply to David Malcolm from comment #2) > (gdb) call this->dump() > bytes 1-0 This should be the read_bytes in region_model::check_region_bounds, with the start being the offset and

[Bug analyzer/106854] [[gnu::malloc(deallocator)]] for non-pointer functions (e.g., fd)

2022-09-06 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106854 Andrew Pinski changed: What|Removed |Added Assignee|unassigned at gcc dot gnu.org |dmalcolm at gcc dot gnu.org

[Bug c/106854] New: [[gnu::malloc(deallocator)]] for non-pointer functions (e.g., fd)

2022-09-06 Thread colomar.6.4.3 at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106854 Bug ID: 106854 Summary: [[gnu::malloc(deallocator)]] for non-pointer functions (e.g., fd) Product: gcc Version: 12.2.0 Status: UNCONFIRMED Severity: normal

[Bug c/106853] compound literal storage duration

2022-09-06 Thread marcelgcc at firemail dot eu via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106853 --- Comment #4 from marcelgcc at firemail dot eu --- Thanks for the explanation.

[Bug c/106853] compound literal storage duration

2022-09-06 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106853 --- Comment #3 from Andrew Pinski --- The important part of the standards: 6.5.2.5 Compound literals 5 The value of the compound literal is that of an unnamed object initialized by the initializer list. If the compound literal occurs outside

[Bug c/106853] compound literal storage duration

2022-09-06 Thread jakub at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106853 Jakub Jelinek changed: What|Removed |Added CC||jakub at gcc dot gnu.org --- Comment

[Bug c/106853] compound literal storage duration

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

[Bug c/106853] New: compound literal storage duration

2022-09-06 Thread marcelgcc at firemail dot eu via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106853 Bug ID: 106853 Summary: compound literal storage duration Product: gcc Version: 11.3.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c

[Bug c++/106851] [modules] Name conflict for exported using-declaration

2022-09-06 Thread johelegp at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106851 Johel Ernesto Guerrero Peña changed: What|Removed |Added CC||johelegp at gmail dot com

[Bug c/106850] restrict type qualifier ignored on function return type

2022-09-06 Thread colomar.6.4.3 at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106850 --- Comment #3 from Alejandro Colomar --- Ahhh, yeah, something like rvalues don't have qualifiers. I seem to remember now. Maybe the standard should fix this for restrict, because things like clang's _Nonnull would benefit from being kept in

[Bug libstdc++/106852] New: Implement C++23 P2465R3 Standard Library Modules std and std.compat

2022-09-06 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106852 Bug ID: 106852 Summary: Implement C++23 P2465R3 Standard Library Modules std and std.compat Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal

[Bug c++/106851] New: [modules] Name conflict for exported using-declaration

2022-09-06 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106851 Bug ID: 106851 Summary: [modules] Name conflict for exported using-declaration Product: gcc Version: 13.0 Status: UNCONFIRMED Keywords: rejects-valid Severity: normal

[Bug c/106850] restrict type qualifier ignored on function return type

2022-09-06 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106850 --- Comment #2 from Andrew Pinski --- > It's standard. Not really as the warning is correct qualifiers are really ignored on return types as required by the standard.

[Bug c/106850] restrict type qualifier ignored on function return type

2022-09-06 Thread colomar.6.4.3 at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106850 --- Comment #1 from Alejandro Colomar --- The benefits are: - It's standard. - It's less bytes to type.

[Bug c/106850] New: restrict type qualifier ignored on function return type

2022-09-06 Thread colomar.6.4.3 at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106850 Bug ID: 106850 Summary: restrict type qualifier ignored on function return type Product: gcc Version: 12.2.0 Status: UNCONFIRMED Severity: normal

[Bug c++/106849] New: internal compiler error: tree check: expected none of template_decl, have template_decl in do_nonmember_using_decl, at cp/name-lookup.cc:4841

2022-09-06 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106849 Bug ID: 106849 Summary: internal compiler error: tree check: expected none of template_decl, have template_decl in do_nonmember_using_decl, at cp/name-lookup.cc:4841

[Bug c++/106848] New: ICE when compiling module interface file with -g: error: type variant differs by TYPE_MAX_VALUE

2022-09-06 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106848 Bug ID: 106848 Summary: ICE when compiling module interface file with -g: error: type variant differs by TYPE_MAX_VALUE Product: gcc Version: 13.0 Status: UNCONFIRMED

[Bug analyzer/106845] [13 Regression] ICE in exceeds_p, at analyzer/store.cc:464 since r13-2029-g7e3b45befdbbf1a1

2022-09-06 Thread dmalcolm at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106845 --- Comment #2 from David Malcolm --- Failing assertion here: #1 0x014df116 in ana::byte_range::exceeds_p (this=0x7fffbf80, other=..., out_overhanging_byte_range=0x7fffbfc0) at ../../src/gcc/analyzer/store.cc:464 464

[Bug target/99555] [OpenMP/nvptx] Execution-time hang for simple nested OpenMP 'target'/'parallel'/'task' constructs

2022-09-06 Thread vries at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99555 --- Comment #17 from Tom de Vries --- (In reply to Thomas Schwinge from comment #14) > > That's with a Nvidia Tesla K20c GPU, Driver Version: 346.46. > > As that version is "a bit old", I shall first update this, before we spend > > any further

[Bug c++/106829] [12/13 Regression] OpenMP offload internal compiler error: in gimplify_expr, at gimplify.cc:16222 since r12-5835

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

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

2022-09-06 Thread rguenth at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106155 --- Comment #9 from Richard Biener --- This is another example where when doing PHI chaining, we fail to consider the use predicate of the PHI operand in the final PHI which has now no further guard before the use.

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

2022-09-06 Thread rguenth at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106155 --- Comment #8 from Richard Biener --- The following variant warns with all GCC releases I tested (and -fno-ivopts fixes it), not exposing a mitigating jump threading opportunity: int *e; int f1 (void); void f2 (int); long f3 (void *, long,

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

2022-09-06 Thread rguenth at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106155 --- Comment #7 from Richard Biener --- This should now be fixed up to the confusion due to IVOPTs. As said the narrowing is problematic here :/

[Bug middle-end/24639] [meta-bug] bug to track all Wuninitialized issues

2022-09-06 Thread rguenth at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=24639 Bug 24639 depends on bug 106754, which changed state. Bug 106754 Summary: compute_control_dep_chain over-estimates domain https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106754 What|Removed |Added

[Bug tree-optimization/106754] compute_control_dep_chain over-estimates domain

2022-09-06 Thread rguenth at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106754 Richard Biener changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED

[Bug tree-optimization/106754] compute_control_dep_chain over-estimates domain

2022-09-06 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106754 --- Comment #1 from CVS Commits --- The master branch has been updated by Richard Biener : https://gcc.gnu.org/g:0a4a2667dc115ca73b552fcabf8570620dfbe55f commit r13-2500-g0a4a2667dc115ca73b552fcabf8570620dfbe55f Author: Richard Biener Date:

[Bug libstdc++/103382] condition_variable::wait() is not cancellable because it is marked noexcept

2022-09-06 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103382 Jonathan Wakely changed: What|Removed |Added Assignee|unassigned at gcc dot gnu.org |redi at gcc dot gnu.org

[Bug libstdc++/103382] condition_variable::wait() is not cancellable because it is marked noexcept

2022-09-06 Thread vanyacpp at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103382 Ivan Sorokin changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug c++/106838] Built-in traits have wrong preconditions

2022-09-06 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106838 Jonathan Wakely changed: What|Removed |Added Status|UNCONFIRMED |ASSIGNED Ever confirmed|0

[Bug c++/106838] Built-in traits have wrong preconditions

2022-09-06 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106838 --- Comment #7 from Jonathan Wakely --- Oh, and actually __is_final is a fourth kind: // D. // "If T is a class type, T shall be a complete type." So the same as C, but doesn't allow incomplete unions.

[Bug c++/106847] deprecated class data member makes the class generate diagnostics even when the member is not used

2022-09-06 Thread avi at scylladb dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106847 --- Comment #1 from Avi Kivity --- Clang equivalent: https://github.com/llvm/llvm-project/issues/55774

[Bug c++/106847] New: deprecated class data member makes the class generate diagnostics even when the member is not used

2022-09-06 Thread avi at scylladb dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106847 Bug ID: 106847 Summary: deprecated class data member makes the class generate diagnostics even when the member is not used Product: gcc Version: 13.0 Status:

[Bug c++/106838] Built-in traits have wrong preconditions

2022-09-06 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106838 --- Comment #6 from Jonathan Wakely --- (In reply to Jonathan Wakely from comment #5) > (void) __is_trivial(I[]); // { dg-error "incomplete type" "FAILS" } This gives an error in gcc-12, so is a regression. But gcc-12 also gives additional

[Bug c++/106838] Built-in traits have wrong preconditions

2022-09-06 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106838 --- Comment #5 from Jonathan Wakely --- (In reply to Jonathan Wakely from comment #4) > All traits of kind C currently reject T[] and T[1], but should accept them. Gah, they do in gcc-12, but not trunk, sorry. But they do reject incomplete

[Bug target/106827] operator++ doesn't work for enum -O2 -mcpu=cortex-m0plus

2022-09-06 Thread rearnsha at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106827 --- Comment #8 from Richard Earnshaw --- That's C++ for you, it permits you to overload operators in completely meaningless ways.

[Bug tree-optimization/106844] ICE in init_use_preds, at gimple-predicate-analysis.cc:1944 since r13-2436-ge9ea2688271bd0b4

2022-09-06 Thread rguenth at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106844 Richard Biener changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug tree-optimization/106844] ICE in init_use_preds, at gimple-predicate-analysis.cc:1944 since r13-2436-ge9ea2688271bd0b4

2022-09-06 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106844 --- Comment #2 from CVS Commits --- The master branch has been updated by Richard Biener : https://gcc.gnu.org/g:1a4e1425f8498580994e32ceb3c50bd52616a82d commit r13-2493-g1a4e1425f8498580994e32ceb3c50bd52616a82d Author: Richard Biener Date:

[Bug analyzer/106845] [13 Regression] ICE in exceeds_p, at analyzer/store.cc:464 since r13-2029-g7e3b45befdbbf1a1

2022-09-06 Thread rguenth at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106845 Richard Biener changed: What|Removed |Added Target Milestone|--- |13.0

[Bug c++/106837] False compilation error "inconsistent begin/end types in range-based 'for' statement"

2022-09-06 Thread ofekshilon at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106837 --- Comment #4 from Ofek Shilon --- This can be tested empirically. Remove the entire build_x_binary_op check, build gcc and run on this snippet. If it builds correctly than the begin/end types are indeed comparable and the emitted error is

[Bug c++/106841] [12 Regression] ICE in vect_get_vec_defs_for_operand, at tree-vect-stmts.cc:1509 since r12-2733-g31855ba6b16cd138

2022-09-06 Thread rguenth at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106841 Richard Biener changed: What|Removed |Added Summary|[12/13 Regression] ICE in |[12 Regression] ICE in

[Bug analyzer/106845] [13 Regression] ICE in exceeds_p, at analyzer/store.cc:464 since r13-2029-g7e3b45befdbbf1a1

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

[Bug c++/106841] [12/13 Regression] ICE in vect_get_vec_defs_for_operand, at tree-vect-stmts.cc:1509 since r12-2733-g31855ba6b16cd138

2022-09-06 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106841 --- Comment #5 from CVS Commits --- The master branch has been updated by Richard Biener : https://gcc.gnu.org/g:e33e61d417eb5e981bb7d709f8681a2f55ed518a commit r13-2492-ge33e61d417eb5e981bb7d709f8681a2f55ed518a Author: Richard Biener Date:

[Bug tree-optimization/106844] ICE in init_use_preds, at gimple-predicate-analysis.cc:1944 since r13-2436-ge9ea2688271bd0b4

2022-09-06 Thread rguenth at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106844 Richard Biener changed: What|Removed |Added Status|NEW |ASSIGNED

[Bug tree-optimization/106842] [12/13 Regression] misleading warning : iteration X invokes undefined behavior

2022-09-06 Thread rguenth at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106842 Richard Biener changed: What|Removed |Added Summary|[12 Regression] misleading |[12/13 Regression]

[Bug tree-optimization/106842] [12 Regression] misleading warning : iteration X invokes undefined behavior

2022-09-06 Thread rguenth at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106842 Richard Biener changed: What|Removed |Added CC||aldyh at gcc dot gnu.org,

[Bug target/106339] [13 Regression] ICE in exact_div, at poly-int.h:2232

2022-09-06 Thread belagod at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106339 Tejas Belagod changed: What|Removed |Added CC||belagod at gcc dot gnu.org Ever

[Bug c++/106841] [12/13 Regression] ICE in vect_get_vec_defs_for_operand, at tree-vect-stmts.cc:1509 since r12-2733-g31855ba6b16cd138

2022-09-06 Thread rguenth at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106841 Richard Biener changed: What|Removed |Added Assignee|unassigned at gcc dot gnu.org |rguenth at gcc dot gnu.org

[Bug preprocessor/106840] [13 Regression] glibc master build failure on ppc64le-linux-gnu since r13-2212-geb4879ab905308

2022-09-06 Thread marxin at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106840 Martin Liška changed: What|Removed |Added CC||jsm28 at gcc dot gnu.org --- Comment #6

[Bug c/106836] [13 Regression] ICE in c_omp_split_clauses, at c-family/c-omp.cc:2636 since r13-2388-ga651e6d59188da89

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

[Bug fortran/106846] New: [OpenMP][5.1] Permit 'declare target' with clauses inside INTERFACE

2022-09-06 Thread burnus at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106846 Bug ID: 106846 Summary: [OpenMP][5.1] Permit 'declare target' with clauses inside INTERFACE Product: gcc Version: 13.0 Status: UNCONFIRMED Keywords: openmp,

[Bug c/106836] [13 Regression] ICE in c_omp_split_clauses, at c-family/c-omp.cc:2636 since r13-2388-ga651e6d59188da89

2022-09-06 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106836 --- Comment #3 from CVS Commits --- The master branch has been updated by Jakub Jelinek : https://gcc.gnu.org/g:1bf8b7adc2de6f2ddaffa3af131b6855ae3e3793 commit r13-2489-g1bf8b7adc2de6f2ddaffa3af131b6855ae3e3793 Author: Jakub Jelinek Date:

[Bug preprocessor/106840] [13 Regression] glibc master build failure on ppc64le-linux-gnu since r13-2212-geb4879ab905308

2022-09-06 Thread jakub at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106840 --- Comment #5 from Jakub Jelinek --- It is treated as an extension even for C and older C++. But given the discussions Joseph started, the above patch changes it such that it only will be recognized as an extension outside of string/character

[Bug lto/91299] [10/11/12/13 Regression] LTO inlines a weak definition in presence of a non-weak definition from an ELF file

2022-09-06 Thread amonakov at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91299 Alexander Monakov changed: What|Removed |Added Keywords||wrong-code Summary|LTO

  1   2   >