public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/47727] [x32] Many passes can't handle const symbol when Pmode != ptr_mode
Date: Mon, 14 Feb 2011 14:28:00 -0000 [thread overview]
Message-ID: <bug-47727-4-snh1FI14Gt@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-47727-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47727
--- Comment #6 from rguenther at suse dot de <rguenther at suse dot de> 2011-02-14 14:21:32 UTC ---
On Mon, 14 Feb 2011, hjl.tools at gmail dot com wrote:
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47727
>
> --- Comment #5 from H.J. Lu <hjl.tools at gmail dot com> 2011-02-14 13:51:27 UTC ---
> Does this patch make any senses?
>
> diff --git a/gcc/simplify-rtx.c b/gcc/simplify-rtx.c
> index ce4eab4..e7e7890 100644
> --- a/gcc/simplify-rtx.c
> +++ b/gcc/simplify-rtx.c
> @@ -1099,10 +1099,13 @@ simplify_unary_operation_1 (enum rtx_code code, enum
> mac
> hine_mode mode, rtx op)
> #if defined(POINTERS_EXTEND_UNSIGNED) && !defined(HAVE_ptr_extend)
> /* As we do not know which address space the pointer is refering to,
> we can do this only if the target does not support different pointer
> - or address modes depending on the address space. */
> + or address modes depending on the address space. Since we will
> + generate new instructions, we must be currently emitting into a
> + sequence. */
> if (target_default_pointer_address_modes_p ()
> && POINTERS_EXTEND_UNSIGNED > 0
> && mode == Pmode && GET_MODE (op) == ptr_mode
> + && in_sequence_p ()
> && (CONSTANT_P (op)
> || (GET_CODE (op) == SUBREG
> && REG_P (SUBREG_REG (op))
Not really. simplify-rtx should never emit new instuctions. Probably
Ulrich, when introducing address-spaces didn't properly think about
this in convert_memory_address_addr_space ().
Richard.
next prev parent reply other threads:[~2011-02-14 14:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-14 3:37 [Bug target/47727] New: [x32] internal compiler error: Segmentation fault hjl.tools at gmail dot com
2011-02-14 3:54 ` [Bug target/47727] " hjl.tools at gmail dot com
2011-02-14 4:19 ` hjl.tools at gmail dot com
2011-02-14 6:16 ` hjl.tools at gmail dot com
2011-02-14 6:38 ` [Bug middle-end/47727] [x32] Many passes can't handle const symbol when Pmode != ptr_mode hjl.tools at gmail dot com
2011-02-14 13:58 ` hjl.tools at gmail dot com
2011-02-14 14:28 ` rguenther at suse dot de [this message]
2011-02-14 14:52 ` hjl.tools at gmail dot com
2011-02-14 17:31 ` hjl.tools at gmail dot com
2011-02-14 19:02 ` hjl at gcc dot gnu.org
2011-07-14 22:51 ` hjl at gcc dot gnu.org
2011-07-28 9:23 ` ubizjak at gmail dot com
2011-08-06 14:52 ` hjl at gcc dot gnu.org
2011-08-08 15:57 ` hjl.tools at gmail dot com
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-47727-4-snh1FI14Gt@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).