public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/51895] [4.7 Regression] ICE in simplify_subreg
Date: Thu, 19 Jan 2012 13:32:00 -0000 [thread overview]
Message-ID: <bug-51895-4-YC6VCv3XKh@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-51895-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51895
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ebotcazou at gcc dot
| |gnu.org
--- Comment #7 from Jakub Jelinek <jakub at gcc dot gnu.org> 2012-01-19 13:11:13 UTC ---
(In reply to comment #6)
> > Untested patch that attempts to fix BLKmode MEM_REF expansion with
> > non-DECL_ADDRESSABLE non-BLKmode base. It creates abysmal code, so IMNSHO
> > eipa_sra should be fixed not to do this.
>
> Hm, can't we do better using extract_bit_field? I mean, it definitely
> should work to do any BIT_FIELD_REF on an rvalue, even if it is a register.
> The patch from comment #1 doesn't look completely wrong, it just seems that
> the caller should have catered for using the mode of the reg. The docs
> of operand_subword also say 'MODE is the mode of OP in case it is a CONST_INT'
> so MODE should be irrelevant if REG_P (op) ...
>
> Seems to be a tricky area, but using a stack temporary looks like overkill.
We don't have BLKmode pseudos, the only thing that can be BLKmode is MEM. So
I'm afraid we can't avoid that. E.g. VIEW_CONVERT_EXPR of a TImode value to
BLKmode value would be expanded by spilling the TImode value to a stack
temporary and adjust_address it to BLKmode too.
next prev parent reply other threads:[~2012-01-19 13:12 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-19 2:22 [Bug middle-end/51895] New: " jakub at gcc dot gnu.org
2012-01-19 4:17 ` [Bug middle-end/51895] " bergner at gcc dot gnu.org
2012-01-19 8:19 ` jakub at gcc dot gnu.org
2012-01-19 10:16 ` rguenth at gcc dot gnu.org
2012-01-19 10:47 ` jakub at gcc dot gnu.org
2012-01-19 12:47 ` jakub at gcc dot gnu.org
2012-01-19 13:12 ` rguenth at gcc dot gnu.org
2012-01-19 13:32 ` jakub at gcc dot gnu.org [this message]
2012-01-19 13:38 ` rguenth at gcc dot gnu.org
2012-01-19 14:07 ` jakub at gcc dot gnu.org
2012-01-19 16:28 ` ebotcazou at gcc dot gnu.org
2012-01-20 9:42 ` jakub at gcc dot gnu.org
2012-01-20 9:54 ` ebotcazou at gcc dot gnu.org
2012-01-20 14:36 ` rguenth at gcc dot gnu.org
2012-01-20 14:38 ` rguenth at gcc dot gnu.org
2012-01-20 15:30 ` rguenth at gcc dot gnu.org
2012-01-20 17:23 ` jakub at gcc dot gnu.org
2012-01-23 12:37 ` rguenth at gcc dot gnu.org
2012-01-26 14:58 ` jakub at gcc dot gnu.org
2012-01-26 15:03 ` jakub 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-51895-4-YC6VCv3XKh@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).