public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug go/100537] [12 Regression] Bootstrap-O3 and bootstrap-debug fail on 32-bit ARM after gcc-12-657-ga076632e274a Date: Fri, 18 Feb 2022 09:29:17 +0000 [thread overview] Message-ID: <bug-100537-4-Z711a3oCHZ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-100537-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100537 --- Comment #21 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-11 branch has been updated by Richard Biener <rguenth@gcc.gnu.org>: https://gcc.gnu.org/g:8a1e92ff45e8e254fb557d20dcfa54a88d354329 commit r11-9592-g8a1e92ff45e8e254fb557d20dcfa54a88d354329 Author: Ian Lance Taylor <iant@golang.org> Date: Sat May 22 19:19:13 2021 -0700 compiler: mark global variables whose address is taken To implement this, change the backend to use flag bits for variables. Fixes https://gcc.gnu.org/PR100537 PR go/100537 * go-gcc.cc (class Gcc_backend): Update methods that create variables to take a flags parameter. Reviewed-on: https://go-review.googlesource.com/c/gofrontend/+/322129 (cherry picked from commit 358832c46a378e5a0b8a2fa3c2739125e3e680c7)
prev parent reply other threads:[~2022-02-18 9:29 UTC|newest] Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-11 16:39 [Bug middle-end/100537] New: " mkuvyrkov at gcc dot gnu.org 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 [this message]
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-Z711a3oCHZ@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).