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 target/47372] [x32] internal compiler error: in simplify_subreg, at simplify-rtx.c:5222
Date: Fri, 04 Mar 2011 16:43:00 -0000	[thread overview]
Message-ID: <bug-47372-4-G2JyoSDgML@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-47372-4@http.gcc.gnu.org/bugzilla/>

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

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jakub at gcc dot gnu.org

--- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> 2011-03-04 16:43:27 UTC ---
(In reply to comment #3)
> Created attachment 23544 [details]
> preprocessed source file
> 
> got the same ICE when building xulrunner on Fedora 15 on s390x with
> gcc version 4.6.0 20110212 (Red Hat 4.6.0-0.7)
> 
> ./vpx_scale/generic/yv12extend.c: In function 'vp8_yv12_extend_frame_borders':
> ./vpx_scale/generic/yv12extend.c:145:1: internal compiler error: in
> simplify_subreg, at simplify-rtx.c:5222
> 
> will try to build again with gcc-4.6.0-0.12.fc15

Please create new PR instead of hijacking an unrelated one unless you are sure
it is the same thing.  And it isn't in this case, your ICE which I've managed
to reproduce on the following reduced testcase is during var-tracking.

/* { dg-do compile } */
/* { dg-options "-g -Os" } */

typedef __SIZE_TYPE__ size_t;
extern inline __attribute__ ((__always_inline__))
void *
memset (void *x, int y, size_t z)
{
  return __builtin___memset_chk (x, y, z, __builtin_object_size (x, 0));
}

void
foo (unsigned char *x, unsigned char *y, unsigned char *z,
     unsigned char *w, unsigned int v, int u, int t)
{
  int i;
  for (i = 0; i < t; i++)
    {
      memset (z, x[0], v);
      memset (w, y[0], v);
      x += u;
    }
  __builtin_memcpy (z, x, u);
}


  parent reply	other threads:[~2011-03-04 16:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-20  8:19 [Bug target/47372] New: " hjl.tools at gmail dot com
2011-01-20 14:32 ` [Bug target/47372] " hjl.tools at gmail dot com
2011-01-20 14:42 ` hjl at gcc dot gnu.org
2011-03-04 15:46 ` dan at danny dot cz
2011-03-04 16:43 ` jakub at gcc dot gnu.org [this message]
2011-03-04 18:40 ` jakub at gcc dot gnu.org
2011-07-26 21:44 ` hjl at gcc dot gnu.org
2011-07-27 17:24 ` ubizjak at gmail dot com
2011-07-29 16:44 ` hjl at gcc dot gnu.org
2011-08-06 14:51 ` 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-47372-4-G2JyoSDgML@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).