[Bug other/96595] New: docs: typos in gfortran -fallow-argument-mismatch invoke description

Priority: P3 Component: other Assignee: unassigned at gcc dot gnu.org Reporter: mkrupcale at matthewkrupcale dot com Target Milestone: --- Created attachment 49053 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=49053&action=edit patch fixing t

[Bug c++/93790] New: Cannot initialize reference from std::reference_wrapper using direct- or list-initialization syntax in GCC 10 c++2a mode

Version: 10.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: mkrupcale at matthewkrupcale dot com Target Milestone: --- The following results in a compile error in GCC 10

[Bug libstdc++/87858] Building old multilib bootstrap GCC: stage1 32-bit libstdc++ fails to build after building 64-bit libstdc++

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87858 --- Comment #2 from Matthew Krupcale --- I can confirm that I'm still observing this when building multilib bootstrap GCC 4.8.3 using GCC 9.2.1 on Fedora 30[1,2]. I tried to verify this issue when building GCC 6.4.1 (GLIBCXX_3.4.22, CXXABI_1.3.10

[Bug libstdc++/87858] New: Building old multilib bootstrap GCC: stage1 32-bit libstdc++ fails to build after building 64-bit libstdc++

Status: UNCONFIRMED Severity: normal Priority: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: mkrupcale at matthewkrupcale dot com Target Milestone: --- Created attachment 44944 --> https://gcc.gnu.

[Bug libstdc++/87858] Building old multilib bootstrap GCC: stage1 32-bit libstdc++ fails to build after building 64-bit libstdc++

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87858 --- Comment #1 from Matthew Krupcale --- Created attachment 44945 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=44945&action=edit analogous patch for GCC 8.2 potentially allowing future GCC to build GCC 8.2 (untested)

[Bug bootstrap/87858] Building old multilib bootstrap GCC: stage1 32-bit libstdc++ fails to build after building 64-bit libstdc++

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87858 --- Comment #3 from Matthew Krupcale --- I now observe this failure in the following two circumstances building multilib bootstrap GCC: - GCC 4.8.3 using GCC 10.2.1-9 on Fedora 33[1] /builddir/build/BUILD/gcc-4.8.3-20140911/obj-x86_64-redhat-li

[Bug bootstrap/87858] Building old multilib bootstrap GCC: stage1 32-bit libstdc++ fails to build after building 64-bit libstdc++

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87858 --- Comment #6 from Matthew Krupcale --- (In reply to Andrew Pinski from comment #5) > Best way to support this really is to build a 4.8 cross compiler and then > build a canandian cross GCC 4.8 and then bootstrap a 4.8.x using that newly > build

[Bug bootstrap/87858] Building old multilib bootstrap GCC: stage1 32-bit libstdc++ fails to build after building 64-bit libstdc++

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87858 --- Comment #8 from Matthew Krupcale --- (In reply to Andrew Pinski from comment #7) > You misunderstood. Building a cross compiler and a canadian cross is so the > new 4.8 compiler is NOT exposing to the bootstrap issue you mentioned. Fair eno

[Bug bootstrap/87858] Building old multilib bootstrap GCC: stage1 32-bit libstdc++ fails to build after building 64-bit libstdc++

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87858 --- Comment #10 from Matthew Krupcale --- Created attachment 55186 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55186&action=edit GCC 7 post stage1 libstdc++ path export patch This patch is for GCC 7 and exports the target libstdc++ path

[Bug bootstrap/87858] Building old multilib bootstrap GCC: stage1 32-bit libstdc++ fails to build after building 64-bit libstdc++

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87858 Matthew Krupcale changed: What|Removed |Added Attachment #44945|0 |1 is obsolete|

[Bug bootstrap/87858] Building old multilib bootstrap GCC: stage1 32-bit libstdc++ fails to build after building 64-bit libstdc++

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87858 --- Comment #12 from Matthew Krupcale --- I've updated the patch to include the target libstdc++ path on LD_LIBRARY_PATH only after stage1 for both host and target module exports--that is, previously, the patches only modified the LD_LIBRARY_PATH