[Bug c/64825] New: -Wcast-qual does not warn about struct members which are arrays

Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: dimitry at andric dot com I'm not sure if it is intentional in gcc, but when using -Wcast-qual, it does not warn about casting away the constness of struct members which are arrays

[Bug c++/67888] Compiling clang 3.7.0 results in is used but never defined

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67888 Dimitry Andric changed: What|Removed |Added CC||dimitry at andric dot com

[Bug libstdc++/69388] Allow functexcept.cc definitions to be replaced

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69388 Dimitry Andric changed: What|Removed |Added CC||dimitry at andric dot com --- Comment

[Bug c++/70528] [5 Regression] bogus error: constructor required before non-static data member

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70528 Dimitry Andric changed: What|Removed |Added CC||dimitry at andric dot com --- Comment

[Bug target/91767] [10 regression] After r274953, clang-compiled xgcc segfaults during RTL pass: stv

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91767 --- Comment #3 from Dimitry Andric --- (In reply to Jakub Jelinek from comment #2) > Isn't that a clang bug though? hash_map has a constructor which should be > invoked by the general_scalar_chain constructor... It is possible, though I think

[Bug bootstrap/91767] New: After r274953, clang-compiled xgcc segfaults during RTL pass: stv

Priority: P3 Component: bootstrap Assignee: unassigned at gcc dot gnu.org Reporter: dimitry at andric dot com Target Milestone: --- As reported in https://bugs.freebsd.org/240387, after the gcc10-devel port was updated from the 20190825 snapshot to the 20190901

[Bug target/91767] [10 regression] After r274953, clang-compiled xgcc segfaults during RTL pass: stv

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91767 --- Comment #5 from Dimitry Andric --- Hmm, it appears that this diff "fixes" it: diff --git a/gcc/config/i386/i386-features.c b/gcc/config/i386/i386-features.c index 9505b4a1330..091a59f3cb9 100644 --- a/gcc/config/i386/i386-features.c +++

[Bug jit/101491] [11 regression] /usr/local/include/libgccjit++.h conflicts between different GCC installations

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101491 --- Comment #4 from Dimitry Andric --- (In reply to Gerald Pfeifer from comment #3) > (In reply to David Malcolm from comment #2) > > I wonder why this changed recently; as Dimitry notes, this has been > > done the same since the initial

[Bug jit/101491] [11 regression] /usr/local/include/libgccjit++.h conflicts between different GCC installations

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101491 Dimitry Andric changed: What|Removed |Added CC||dimitry at andric dot com

[Bug middle-end/111632] gcc fails to bootstrap when using libc++

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111632 --- Comment #5 from Dimitry Andric --- Is there any further action required to get this patch in? :)

[Bug other/111632] New: gcc's C++ components fail to compile against recent libc++ headers

Priority: P3 Component: other Assignee: unassigned at gcc dot gnu.org Reporter: dimitry at andric dot com Target Milestone: --- As reported in https://bugs.freebsd.org/274041 and a number of related PRs, when building gcc's C++ sources against recent libc

[Bug other/111632] gcc's C++ components fail to compile against recent libc++ headers

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111632 --- Comment #1 from Dimitry Andric --- Created attachment 56010 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56010=edit Include safe-ctype.h after C++ standard headers, to avoid over-poisoning

[Bug middle-end/111632] gcc's C++ components fail to compile against recent libc++ headers

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111632 --- Comment #3 from Dimitry Andric --- (In reply to Richard Biener from comment #2) > the patch looks reasonable, please post it to gcc-patc...@gcc.gnu.org https://gcc.gnu.org/pipermail/gcc-patches/2023-September/631611.html

[Bug middle-end/111632] gcc fails to bootstrap when using libc++

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111632 --- Comment #10 from Dimitry Andric --- Note there are other issues with poisoned identifiers, so I'll ask again: is a non-bootstrapped build even supposed to work, and officially supported, or not? Or more qualified, is a non-bootstrapped

[Bug middle-end/111632] gcc fails to bootstrap when using libc++

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111632 --- Comment #16 from Dimitry Andric --- Created attachment 57639 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57639=edit Fix identifier poisoning in libcc1plugin and libc1plugin Here is another patch that can be committed separately.

[Bug middle-end/111632] gcc fails to bootstrap when using libc++

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111632 --- Comment #17 from Dimitry Andric --- With both attached patches, I can build gcc master (gcc-14-9347-g790e0b478ea) with --disable-bootstrap, against libc++ 18 on FreeBSD 15-CURRENT, using clang 18 as host compiler.

[Bug middle-end/111632] gcc fails to bootstrap when using libc++

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111632 --- Comment #21 from Dimitry Andric --- (In reply to Iain Sandoe from comment #20) > This is fixed on trunk, but is needed on open release branches. Indeed, please merge both commits:

[Bug middle-end/111632] gcc fails to bootstrap when using libc++

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111632 --- Comment #29 from Dimitry Andric --- (In reply to Liviu Ionescu from comment #28) > (In reply to Francois-Xavier Coudert from comment #27) > > *** Bug 115006 has been marked as a duplicate of this bug. *** > > 11506 is related to gcov.cc,