public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pthaugen at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/58675] ICE in rs6000_secondary_reload_inner:15460, type = store
Date: Wed, 15 Jan 2014 18:20:00 -0000	[thread overview]
Message-ID: <bug-58675-4-NDZHovGl43@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-58675-4@http.gcc.gnu.org/bugzilla/>

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

Pat Haugen <pthaugen at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #30973|0                           |1
        is obsolete|                            |

--- Comment #2 from Pat Haugen <pthaugen at gcc dot gnu.org> ---
Created attachment 31846
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=31846&action=edit
New test

177.mesa still fails to build, new reduced testcase attached.

[pthaugen@igoo pr58675]$ /home/pthaugen/install/gcc/trunk/bin/gcc -c -m64 -O1
-mcpu=power8 triangle-2.c
rs6000_secondary_reload_inner:16294, type = store
(parallel [
        (set (mem/c:SF (plus:DI (plus:DI (reg/f:DI 1 1)
                        (const_int 65536 [0x10000]))
                    (const_int -30176 [0xffffffffffff8a20])) [0 %sfp+35360 S4
A32])
            (reg:SF 32 0))
        (clobber (reg:DI 9 9))
    ])
triangle-2.c: In function ‘lambda_textured_triangle’:
triangle-2.c:452:1: internal compiler error: in rs6000_secondary_reload_fail,
at config/rs6000/rs6000.c:16121
 }
 ^
0x109c2bf7 rs6000_secondary_reload_fail
    /home/pthaugen/src/gcc/trunk/gcc/gcc/config/rs6000/rs6000.c:16121
0x109f5957 rs6000_secondary_reload_inner(rtx_def*, rtx_def*, rtx_def*, bool)
    /home/pthaugen/src/gcc/trunk/gcc/gcc/config/rs6000/rs6000.c:16148
0x10ac908b gen_reload_sf_di_store(rtx_def*, rtx_def*, rtx_def*)
    /home/pthaugen/src/gcc/trunk/gcc/gcc/config/rs6000/vector.md:197
0x1063cf0b insn_gen_fn::operator()(rtx_def*, rtx_def*, rtx_def*) const
    /home/pthaugen/src/gcc/trunk/gcc/gcc/recog.h:285
0x1063cf0b emit_output_reload_insns
    /home/pthaugen/src/gcc/trunk/gcc/gcc/reload1.c:7758
0x1063cf0b do_output_reload
...
>From gcc-bugs-return-440472-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 15 19:10:45 2014
Return-Path: <gcc-bugs-return-440472-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 11818 invoked by alias); 15 Jan 2014 19:10:45 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 11755 invoked by uid 55); 15 Jan 2014 19:10:42 -0000
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/59659] large zero-initialized std::array compile time excessive
Date: Wed, 15 Jan 2014 19:10:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 4.8.2
X-Bugzilla-Keywords: compile-time-hog, memory-hog, missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jason at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jason at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-59659-4-qJnSUPTtQd@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-59659-4@http.gcc.gnu.org/bugzilla/>
References: <bug-59659-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2014-01/txt/msg01614.txt.bz2
Content-length: 756

http://gcc.gnu.org/bugzilla/show_bug.cgi?idY659

--- Comment #9 from Jason Merrill <jason at gcc dot gnu.org> ---
Author: jason
Date: Wed Jan 15 19:10:09 2014
New Revision: 206639

URL: http://gcc.gnu.org/viewcvs?rev 6639&root=gcc&view=rev
Log:
    PR c++/59659
    * typeck2.c (massage_init_elt): New.
    (process_init_constructor_record)
    (process_init_constructor_union): Use it.
    (process_init_constructor_array): Use it.  Use RANGE_EXPR.
    (split_nonconstant_init_1): Handle it.
    * semantics.c (cxx_eval_vec_init_1): Use force_rvalue.

Added:
    trunk/gcc/testsuite/g++.dg/opt/value-init1.C
    trunk/gcc/testsuite/g++.dg/opt/value-init2.C
Modified:
    trunk/gcc/cp/ChangeLog
    trunk/gcc/cp/semantics.c
    trunk/gcc/cp/typeck2.c


  parent reply	other threads:[~2014-01-15 18:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-09 21:30 [Bug target/58675] New: " pthaugen at gcc dot gnu.org
2014-01-14 22:59 ` [Bug target/58675] " bergner at gcc dot gnu.org
2014-01-15 18:20 ` pthaugen at gcc dot gnu.org [this message]
2014-02-10  6:30 ` amodra at gmail dot com
2014-02-10  6:33 ` amodra at gmail dot com
2014-02-15 10:50 ` amodra at gcc dot gnu.org
2014-02-15 10:51 ` amodra at gmail dot com
2014-02-26  4:42 ` amodra at gcc dot gnu.org
2014-04-04 15:06 ` wschmidt 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-58675-4-NDZHovGl43@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).