public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/57896] [4.8 Regression] ICE in expand_expr_real_2
Date: Thu, 20 Feb 2014 11:01:00 -0000	[thread overview]
Message-ID: <bug-57896-4-8Isr3d1PVR@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-57896-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #23 from Uroš Bizjak <ubizjak at gmail dot com> ---
(In reply to Jakub Jelinek from comment #22)

> IMHO that is way too expensive.

Agreed.

Anyway, it looks you got this problem under control ;)
>From gcc-bugs-return-444336-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 20 11:07:20 2014
Return-Path: <gcc-bugs-return-444336-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 18560 invoked by alias); 20 Feb 2014 11:07:19 -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 18521 invoked by uid 48); 20 Feb 2014 11:07:15 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/60236] gfortran.dg/vect/pr32380.f fails on ARM
Date: Thu, 20 Feb 2014 11:07:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 4.9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dominiq at lps dot ens.fr
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-60236-4-SA9cHIP9ad@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-60236-4@http.gcc.gnu.org/bugzilla/>
References: <bug-60236-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-02/txt/msg02093.txt.bz2
Content-length: 1631

http://gcc.gnu.org/bugzilla/show_bug.cgi?id`236

--- Comment #7 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
> This patch tries to solve the problem in a more general way.
> I wonder if one of you could try this patch on PowerPC?

Sorry for the late answer, but my G5 was buzzy regtesting. With the patch in
comment 5, tested with

make -k check-gfortran RUNTESTFLAGS="vect.exp=pr32380.f
--target_board=unix'{-m32,-m64}'"

I get


        === gfortran tests ==
Schedule of variations:
    unix/-m32
    unix/-m64

Running target unix/-m32
Using /sw/share/dejagnu/baseboards/unix.exp as board description file for
target.
Using /sw/share/dejagnu/config/unix.exp as generic interface file for target.
Using /opt/gcc/work/gcc/testsuite/config/default.exp as
tool-and-target-specific interface file.
Running /opt/gcc/work/gcc/testsuite/gfortran.dg/vect/vect.exp ...

        === gfortran Summary for unix/-m32 ==
# of expected passes        2
Running target unix/-m64
Using /sw/share/dejagnu/baseboards/unix.exp as board description file for
target.
Using /sw/share/dejagnu/config/unix.exp as generic interface file for target.
Using /opt/gcc/work/gcc/testsuite/config/default.exp as
tool-and-target-specific interface file.
Running /opt/gcc/work/gcc/testsuite/gfortran.dg/vect/vect.exp ...

        === gfortran Summary for unix/-m64 ==
# of expected passes        2

        === gfortran Summary ==
# of expected passes        4
/opt/gcc/darwin_buildw/gcc/testsuite/gfortran/../../gfortran  version 4.9.0
20140218 (experimental) [trunk revision 207836p2] (GCC)

So the patch is OK for powerpc-apple-darwin9.


  parent reply	other threads:[~2014-02-20 11:01 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-15  6:44 [Bug c/57896] New: ICE in " zeccav at gmail dot com
2013-07-15  9:37 ` [Bug c/57896] " mikpe at it dot uu.se
2013-07-15 14:23 ` mikpe at it dot uu.se
2013-07-15 15:32 ` glisse at gcc dot gnu.org
2013-07-15 16:32 ` glisse at gcc dot gnu.org
2013-07-15 23:42 ` zeccav at gmail dot com
2013-07-16  6:19 ` zeccav at gmail dot com
2014-02-19  8:11 ` [Bug c/57896] [4.8 Regression] ICE " mpolacek at gcc dot gnu.org
2014-02-19 17:59 ` [Bug target/57896] " ubizjak at gmail dot com
2014-02-19 18:06 ` ubizjak at gmail dot com
2014-02-19 18:34 ` ubizjak at gmail dot com
2014-02-19 18:37 ` [Bug middle-end/57896] " ubizjak at gmail dot com
2014-02-19 19:19 ` mpolacek at gcc dot gnu.org
2014-02-20  9:29 ` ubizjak at gmail dot com
2014-02-20  9:58 ` ubizjak at gmail dot com
2014-02-20 10:15 ` ubizjak at gmail dot com
2014-02-20 10:27 ` [Bug target/57896] " jakub at gcc dot gnu.org
2014-02-20 10:41 ` jakub at gcc dot gnu.org
2014-02-20 10:45 ` ubizjak at gmail dot com
2014-02-20 10:57 ` jakub at gcc dot gnu.org
2014-02-20 11:01 ` ubizjak at gmail dot com [this message]
2014-02-20 11:07 ` [Bug target/57896] [4.7/4.8/4.9 " ubizjak at gmail dot com
2014-02-20 11:42 ` jakub at gcc dot gnu.org
2014-02-20 12:00 ` jakub at gcc dot gnu.org
2014-02-20 12:09 ` ubizjak at gmail dot com
2014-02-20 13:00 ` jakub at gcc dot gnu.org
2014-02-20 13:12 ` ubizjak at gmail dot com
2014-02-20 17:25 ` ubizjak at gmail dot com
2014-02-20 20:40 ` jakub at gcc dot gnu.org
2014-02-20 20:41 ` jakub at gcc dot gnu.org
2014-02-20 20:42 ` [Bug target/57896] [4.7 " jakub at gcc dot gnu.org
2014-02-21  7:56 ` uros at gcc dot gnu.org
2014-02-21  8:01 ` ubizjak at gmail dot com

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-57896-4-8Isr3d1PVR@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).