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 middle-end/55851] [4.8 Regression] ICE in size_binop_loc, at fold-const.c:1385
Date: Thu, 03 Jan 2013 16:32:00 -0000	[thread overview]
Message-ID: <bug-55851-4-HQGXsMsqTT@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55851-4@http.gcc.gnu.org/bugzilla/>


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55851

--- Comment #9 from Richard Biener <rguenth at gcc dot gnu.org> 2013-01-03 16:32:04 UTC ---
Ehm.  (In reply to comment #8)
> Created attachment 29078 [details]
> gcc48-pr55851.patch
> 
> Untested patch (which I don't like very much, but we can't even use something
> like get_initialized_tmp_var which would strip the cast as useless too).

Ugh.  Now that sizetypes are no longer "special" we can also decide to
allow ENUMERAL_TYPE in size positions (and adjust int_binop_types_match_p).

But I'm not sure if we really want non-literal-sizetype sizes in type
trees (they will easily appear in the extra operands of ARRAY_REF and
COMPONENT_REF though, so maybe it's really the right thing to do).

Otherwise using a get_initialized_tmp_var-like mechanism should be ok
as long as you explicitely create the temporary variable with sizetype
(I don't see that it strips the cast before getting at the type to
create the temporary?)


  parent reply	other threads:[~2013-01-03 16:32 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-03  1:05 [Bug middle-end/55851] New: " jan.smets@alcatel-lucent.com
2013-01-03  1:28 ` [Bug middle-end/55851] " pinskia at gcc dot gnu.org
2013-01-03  1:33 ` pinskia at gcc dot gnu.org
2013-01-03  1:36 ` pinskia at gcc dot gnu.org
2013-01-03  1:42 ` pinskia at gcc dot gnu.org
2013-01-03  1:48 ` [Bug middle-end/55851] [4.8 Regression] " pinskia at gcc dot gnu.org
2013-01-03 11:16 ` [Bug c/55851] " rguenth at gcc dot gnu.org
2013-01-03 14:48 ` [Bug middle-end/55851] " jakub at gcc dot gnu.org
2013-01-03 15:32 ` jakub at gcc dot gnu.org
2013-01-03 16:32 ` rguenth at gcc dot gnu.org [this message]
2013-01-07 15:46 ` rguenth at gcc dot gnu.org
2013-01-08  8:32 ` jakub at gcc dot gnu.org
2013-01-08  8:46 ` 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-55851-4-HQGXsMsqTT@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).