public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mkuvyrkov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/100537] New: Bootstrap-O3 and bootstrap-debug fail on 32-bit ARM after gcc-12-657-ga076632e274a Date: Tue, 11 May 2021 16:39:56 +0000 [thread overview] Message-ID: <bug-100537-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100537 Bug ID: 100537 Summary: Bootstrap-O3 and bootstrap-debug fail on 32-bit ARM after gcc-12-657-ga076632e274a Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: middle-end Assignee: unassigned at gcc dot gnu.org Reporter: mkuvyrkov at gcc dot gnu.org Target Milestone: --- Patch a076632e274abe344ca7648b7c7f299273d4cbe0 appears to have broken bootstrap-O3 and bootstrap-debug at least on 32-bit armhf. 00:33:32 In function ‘syscall.forkExec’: 00:33:32 go1: error: address taken, but ADDRESSABLE bit not set 00:33:32 PHI argument 00:33:32 &go..C479; 00:33:32 for PHI node 00:33:32 err$__object_78 = PHI <err$__object_76(58), &go..C479(59)> 00:33:32 during GIMPLE pass: fre 00:33:32 go1: internal compiler error: verify_ssa failed 00:33:32 0x9c18d7 verify_ssa(bool, bool) 00:33:32 /home/tcwg-buildslave/workspace/tcwg_gnu_0/abe/snapshots/gcc.git~master/gcc/tree-ssa.c:1214 00:33:32 0x6f8d5b execute_function_todo 00:33:32 /home/tcwg-buildslave/workspace/tcwg_gnu_0/abe/snapshots/gcc.git~master/gcc/passes.c:2049 00:33:32 0x6f9abf do_per_function 00:33:32 /home/tcwg-buildslave/workspace/tcwg_gnu_0/abe/snapshots/gcc.git~master/gcc/passes.c:1687 00:33:32 0x6f9abf execute_todo 00:33:32 /home/tcwg-buildslave/workspace/tcwg_gnu_0/abe/snapshots/gcc.git~master/gcc/passes.c:2096 00:33:32 Please submit a full bug report, 00:33:32 with preprocessed source if appropriate. 00:33:32 Please include the complete backtrace with any bug report. 00:33:32 See <https://gcc.gnu.org/bugs/> for instructions. 00:33:32 Makefile:3001: recipe for target 'syscall.lo' failed
next reply other threads:[~2021-05-11 16:39 UTC|newest] Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-11 16:39 mkuvyrkov at gcc dot gnu.org [this message] 2021-05-11 16:40 ` [Bug middle-end/100537] " mkuvyrkov at gcc dot gnu.org 2021-05-11 18:45 ` mkuvyrkov at gcc dot gnu.org 2021-05-12 3:01 ` guojiufu at gcc dot gnu.org 2021-05-12 6:49 ` [Bug go/100537] " rguenth at gcc dot gnu.org 2021-05-12 9:03 ` guojiufu at gcc dot gnu.org 2021-05-12 9:16 ` guojiufu at gcc dot gnu.org 2021-05-12 9:30 ` rguenth at gcc dot gnu.org 2021-05-12 9:47 ` rguenth at gcc dot gnu.org 2021-05-12 11:12 ` guojiufu at gcc dot gnu.org 2021-05-12 15:03 ` rguenth at gcc dot gnu.org 2021-05-12 15:11 ` guojiufu at gcc dot gnu.org 2021-05-12 21:25 ` ian at airs dot com 2021-05-13 2:19 ` guojiufu at gcc dot gnu.org 2021-05-13 7:00 ` guojiufu at gcc dot gnu.org 2021-05-13 7:02 ` guojiufu at gcc dot gnu.org 2021-05-20 22:10 ` bergner at gcc dot gnu.org 2021-05-24 15:55 ` ian at airs dot com 2021-05-24 20:25 ` cvs-commit at gcc dot gnu.org 2021-05-24 20:58 ` ian at airs dot com 2021-09-17 6:36 ` [Bug go/100537] [12 Regression] " pinskia at gcc dot gnu.org 2022-02-17 10:23 ` rguenth at gcc dot gnu.org 2022-02-17 16:18 ` ian at airs dot com 2022-02-18 9:29 ` cvs-commit 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-100537-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).