public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/59199] [4.9 Regression] r205032 caused LTO bootstrap to fail with bootstrap-profile
Date: Fri, 29 Nov 2013 16:45:00 -0000 [thread overview]
Message-ID: <bug-59199-4-trp7p4jMjS@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-59199-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59199
--- Comment #5 from H.J. Lu <hjl.tools at gmail dot com> ---
(In reply to Richard Biener from comment #4)
>
> Likely a update_address_taken bug, eventual fix:
>
> @@ -1329,6 +1336,10 @@ non_rewritable_mem_ref_base (tree ref)
> if (DECL_P (ref))
> return NULL_TREE;
>
> + /* For DEBUG_STMTs we have to look through ADDR_EXPRs. */
> + if (TREE_CODE (ref) == ADDR_EXPR)
> + ref = TREE_OPERAND (ref, 0);
> +
> while (handled_component_p (base))
> base = TREE_OPERAND (base, 0);
I tried it and I still got the same error:
next prev parent reply other threads:[~2013-11-29 16:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-20 3:16 [Bug bootstrap/59199] New: " hjl.tools at gmail dot com
2013-11-20 10:44 ` [Bug bootstrap/59199] " rguenth at gcc dot gnu.org
2013-11-27 21:13 ` hjl.tools at gmail dot com
2013-11-28 8:45 ` rguenth at gcc dot gnu.org
2013-11-29 14:41 ` rguenth at gcc dot gnu.org
2013-11-29 16:45 ` hjl.tools at gmail dot com [this message]
2013-12-02 9:41 ` rguenth at gcc dot gnu.org
2013-12-02 10:04 ` rguenth at gcc dot gnu.org
2013-12-02 13:07 ` hjl.tools at gmail dot com
2013-12-02 15:15 ` rguenth 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-59199-4-trp7p4jMjS@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).