public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug go/100537] Bootstrap-O3 and bootstrap-debug fail on 32-bit ARM after gcc-12-657-ga076632e274a
Date: Wed, 12 May 2021 06:49:10 +0000 [thread overview]
Message-ID: <bug-100537-4-ASSdDL7L8C@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
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |cmang at google dot com,
| |iant at google dot com
Assignee|unassigned at gcc dot gnu.org |ian at airs dot com
Component|middle-end |go
--- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> ---
So the issue is that the go FE creates go..C479 and it somewhere builds the
address of it but fails to set TREE_ADDRESSABLE. There are only a few
build_fold_addr_expr calls in the FE:
> grep -r build_fold_addr .
./go-gcc.cc: tree t = build_fold_addr_expr_loc(location.gcc_location(),
this->t_);
./go-gcc.cc: tree ret = build_fold_addr_expr_loc(location.gcc_location(),
func);
./go-gcc.cc: tree ret = build_fold_addr_expr_loc(location.gcc_location(),
expr);
./go-gcc.cc: fn = build_fold_addr_expr_loc(location.gcc_location(),
./go-gcc.cc:
build_fold_addr_expr_loc(location.gcc_location(),
one does mark the object addressable but all the others do not. So for
those who can reproduce, run the failing compile in a debugger, see
which ADDR_EXPR we complain about and then set a breakpoint in
ggc_internal_alloc conditional on the return value being this ADDR_EXPR.
That should nail one of the above after which you should call
mark_addressable on the object.
next prev parent reply other threads:[~2021-05-12 6:49 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 ` rguenth at gcc dot gnu.org [this message]
2021-05-12 9:03 ` [Bug go/100537] " 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-ASSdDL7L8C@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: link
Be 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).