public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/55142] [4.8 Regression] internal compiler error: in plus_constant, at explow.c:88
Date: Thu, 08 Nov 2012 23:22:00 -0000	[thread overview]
Message-ID: <bug-55142-4-JJEsXKDRox@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55142-4@http.gcc.gnu.org/bugzilla/>


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

--- Comment #29 from Eric Botcazou <ebotcazou at gcc dot gnu.org> 2012-11-08 23:21:44 UTC ---
> So for POINTERS_EXTEND_UNSIGNED > 0, we should transform
> 
> (zero_extend:DI (plus:SI (FOO:SI) (const_int Y)))
> 
> in such a way that it won't cause ICE and zero-extend the
> result.  For X32, we just need to generate
> 
> (plus:SI (REG:SI) (const_int Y))

The ICE is a minor detail, the real issue is convert_memory_address_addr_space
and PR middle-end/49721.  The unmodified compiler generates the same
problematic instructions for the full testcase without -fPIC.  It's clear that
Richard's change, aka the un-sign-extension of sizetype constants, is an
earthquake here.


  parent reply	other threads:[~2012-11-08 23:22 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-31  2:05 [Bug middle-end/55142] New: " hjl.tools at gmail dot com
2012-10-31  2:21 ` [Bug middle-end/55142] " hjl.tools at gmail dot com
2012-10-31  8:26 ` hjl.tools at gmail dot com
2012-10-31  9:14 ` hjl.tools at gmail dot com
2012-10-31 10:19 ` hjl.tools at gmail dot com
2012-10-31 10:59 ` ebotcazou at gcc dot gnu.org
2012-10-31 11:09 ` hjl.tools at gmail dot com
2012-10-31 11:26 ` hjl.tools at gmail dot com
2012-10-31 12:20 ` hjl.tools at gmail dot com
2012-10-31 12:50 ` ebotcazou at gcc dot gnu.org
2012-10-31 13:12 ` hjl.tools at gmail dot com
2012-11-01  8:44 ` ebotcazou at gcc dot gnu.org
2012-11-01 12:51 ` [Bug target/55142] " ebotcazou at gcc dot gnu.org
2012-11-01 14:20 ` ebotcazou at gcc dot gnu.org
2012-11-01 22:24 ` [Bug middle-end/55142] " hjl.tools at gmail dot com
2012-11-01 22:30 ` hjl.tools at gmail dot com
2012-11-01 23:00 ` ebotcazou at gcc dot gnu.org
2012-11-01 23:08 ` hjl.tools at gmail dot com
2012-11-02 23:09 ` hjl.tools at gmail dot com
2012-11-03  2:51 ` hjl.tools at gmail dot com
2012-11-07 18:35 ` ebotcazou at gcc dot gnu.org
2012-11-07 22:12 ` hjl.tools at gmail dot com
2012-11-07 22:43 ` ebotcazou at gcc dot gnu.org
2012-11-07 23:04 ` hjl.tools at gmail dot com
2012-11-08 16:11 ` ebotcazou at gcc dot gnu.org
2012-11-08 16:24 ` ubizjak at gmail dot com
2012-11-08 16:34 ` ubizjak at gmail dot com
2012-11-08 17:18 ` ebotcazou at gcc dot gnu.org
2012-11-08 23:03 ` hjl.tools at gmail dot com
2012-11-08 23:22 ` ebotcazou at gcc dot gnu.org [this message]
2012-11-09  0:35 ` hjl.tools at gmail dot com
2012-11-09  2:36 ` hjl.tools at gmail dot com
2012-11-12  4:08 ` hjl.tools at gmail dot com
2012-11-13 14:17 ` ebotcazou at gcc dot gnu.org
2012-11-13 14:32 ` [Bug target/55142] " hjl.tools at gmail dot com
2012-11-13 18:21 ` hjl.tools at gmail dot com
2012-11-13 18:36 ` [Bug middle-end/55142] " hjl at gcc dot gnu.org
2012-11-13 19:37 ` ebotcazou at gcc dot gnu.org
2012-11-19 19:18 ` hjl at gcc dot gnu.org
2014-05-30  2:22 ` pinskia at gcc dot gnu.org
2014-05-30 22:47 ` pinskia at gcc dot gnu.org
2014-11-23  4:13 ` pinskia 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-55142-4-JJEsXKDRox@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).