public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ro at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/104198] New: [12 regression] ifcvf change breaks 64-bit SPARC bootstrap Date: Mon, 24 Jan 2022 08:36:23 +0000 [thread overview] Message-ID: <bug-104198-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104198 Bug ID: 104198 Summary: [12 regression] ifcvf change breaks 64-bit SPARC bootstrap Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: rtl-optimization Assignee: unassigned at gcc dot gnu.org Reporter: ro at gcc dot gnu.org CC: ebotcazou at gcc dot gnu.org, rdapp at gcc dot gnu.org Target Milestone: --- Target: sparcv9-sun-solaris2.11 Between 20220114 (89b4e316a02be9fda3b793a7be871f7c7913cd58) and 20220121 (6f45deb2aed804b185e7dabd2392bfbe14e9bb57) 64-bit Solaris/SPARC bootstrap got broken. The issue can already be seen in the first C++ configure test for stage 2 libstdc++: $ cat conftest.cpp class Foo { public: Foo (void) { a = 0; } private: int a; }; $ ./xgcc -B./ -c conftest.cpp ../conftest.cpp:6:7: error: function definition does not declare parameters 6 | int a; | ^ ../conftest.cpp: In constructor ‘Foo::Foo()’: ../conftest.cpp:4:16: error: ‘a’ was not declared in this scope 4 | Foo (void) { a = 0; } | ^ Looks like a miscompilation and completely breaks the libstdc++ build. A reghunt identified this patch commit aa8cfe785953a0e87d2472311e1260cd98c605c0 Author: Robin Dapp <rdapp@linux.ibm.com> Date: Wed Jan 19 17:36:36 2022 +0100 ifcvt: Try re-using CC for conditional moves. As the culprit. 32-bit Solaris/SPARC (sparc-sun-solaris2.11) is unaffected, however.
next reply other threads:[~2022-01-24 8:36 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-24 8:36 ro at gcc dot gnu.org [this message] 2022-01-24 8:36 ` [Bug rtl-optimization/104198] " ro at gcc dot gnu.org 2022-01-24 8:43 ` pinskia at gcc dot gnu.org 2022-01-24 8:44 ` ro at CeBiTec dot Uni-Bielefeld.DE 2022-01-24 9:04 ` ebotcazou at gcc dot gnu.org 2022-01-24 9:06 ` ro at CeBiTec dot Uni-Bielefeld.DE 2022-01-24 9:08 ` ebotcazou at gcc dot gnu.org 2022-01-24 9:18 ` rdapp at linux dot ibm.com 2022-01-24 9:23 ` ro at CeBiTec dot Uni-Bielefeld.DE 2022-01-24 9:26 ` rguenth at gcc dot gnu.org 2022-01-24 16:54 ` rdapp at linux dot ibm.com 2022-01-25 12:27 ` rdapp at linux dot ibm.com 2022-01-26 17:08 ` rdapp at linux dot ibm.com 2022-01-27 9:36 ` ro at CeBiTec dot Uni-Bielefeld.DE 2022-01-27 13:04 ` ro at CeBiTec dot Uni-Bielefeld.DE 2022-01-31 7:14 ` [Bug rtl-optimization/104198] [12 regression] ifcvt " rdapp at linux dot ibm.com 2022-01-31 10:13 ` rdapp at linux dot ibm.com 2022-02-01 9:32 ` rdapp at linux dot ibm.com 2022-02-08 19:49 ` cvs-commit at gcc dot gnu.org 2022-03-07 15:45 ` jakub at gcc dot gnu.org 2022-03-08 11:31 ` ro at CeBiTec dot Uni-Bielefeld.DE 2022-03-08 11:33 ` jakub at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-104198-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).