public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rdsandiford at googlemail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/53249] [4.8 Regression] Bootstrap failure
Date: Sun, 06 May 2012 16:01:00 -0000 [thread overview]
Message-ID: <bug-53249-4-S6s12mFZOe@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-53249-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53249
--- Comment #9 from rdsandiford at googlemail dot com <rdsandiford at googlemail dot com> 2012-05-06 15:56:09 UTC ---
"hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org> writes:
> get_address_mode in dwarf2out.c works for this testcase.
Yeah, that's what I was testing FWIW. If x32 wants to do this,
then pretty much every instance of:
targetm.addr_space.address_mode (MEM_ADDR_SPACE (mem))
needs to use get_address_mode instead. So I'm trying to convert all of them.
(There's a duplicate copy in var-tracking.c, so the patch consolidates
them into a general rtl.h function.)
next prev parent reply other threads:[~2012-05-06 15:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-05 22:22 [Bug bootstrap/53249] New: " hjl.tools at gmail dot com
2012-05-05 23:27 ` [Bug bootstrap/53249] " hjl.tools at gmail dot com
2012-05-06 10:59 ` rsandifo at gcc dot gnu.org
2012-05-06 14:16 ` hjl.tools at gmail dot com
2012-05-06 14:35 ` hjl.tools at gmail dot com
2012-05-06 14:54 ` hjl.tools at gmail dot com
2012-05-06 15:07 ` hjl.tools at gmail dot com
2012-05-06 15:09 ` rsandifo at gcc dot gnu.org
2012-05-06 15:56 ` hjl.tools at gmail dot com
2012-05-06 16:01 ` rdsandiford at googlemail dot com [this message]
2012-05-06 17:04 ` hjl.tools at gmail dot com
2012-05-09 9:24 ` rsandifo at gcc dot gnu.org
2012-05-09 9:40 ` rsandifo at gcc dot gnu.org
2012-05-09 13:34 ` hjl 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-53249-4-S6s12mFZOe@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).