public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/65577] New: ICE on g++.dg/torture/pr58369.C
Date: Thu, 26 Mar 2015 08:15:00 -0000	[thread overview]
Message-ID: <bug-65577-4@http.gcc.gnu.org/bugzilla/> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="UTF-8", Size: 4434 bytes --]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65577

            Bug ID: 65577
           Summary: ICE on g++.dg/torture/pr58369.C
           Product: gcc
           Version: 5.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: target
          Assignee: unassigned at gcc dot gnu.org
          Reporter: msebor at gcc dot gnu.org

Compiling the g++.dg/torture/pr58369.C test with yesterday's trunk (r221640) on
powerpc64 (a POWER7 processor) fails with the ICE below.  Interestingly, the
ICE disappears with -O1.  On powerpc64le gcc compiles the test successfully.

$ g++ -O0 -c /src/gcc-trunk/gcc/testsuite/g++.dg/torture/pr58369.C
/src/gcc-trunk/gcc/testsuite/g++.dg/torture/pr58369.C: In function ‘T
ellint_rj_imp(T, T, T, T, Policy&) [with T = long double; Policy = PolicyA]’:
/src/gcc-trunk/gcc/testsuite/g++.dg/torture/pr58369.C:88:1: error:
unrecognizable insn:
 }
 ^
(insn 248 247 99 8 (set (reg:DF 10 10)
        (mem/u/c:DF (symbol_ref/u:DI ("*.LC0") [flags 0x2]) [0  S8 A64]))
/src/gcc-trunk/gcc/testsuite/g++.dg/torture/pr58369.C:70 -1
     (nil))
/src/gcc-trunk/gcc/testsuite/g++.dg/torture/pr58369.C:88:1: internal compiler
error: in extract_insn, at recog.c:2343
0x109c9f1b _fatal_insn(char const*, rtx_def const*, char const*, int, char
const*)
    /src/gcc-trunk/gcc/rtl-error.c:110
0x109c9f6f _fatal_insn_not_found(rtx_def const*, char const*, int, char const*)
    /src/gcc-trunk/gcc/rtl-error.c:118
0x1098f907 extract_insn(rtx_insn*)
    /src/gcc-trunk/gcc/recog.c:2343
0x1098f9c7 extract_insn_cached(rtx_insn*)
    /src/gcc-trunk/gcc/recog.c:2234
0x106b6817 cleanup_subreg_operands(rtx_insn*)
    /src/gcc-trunk/gcc/final.c:3137
0x109c74b7 reload(rtx_insn*, int)
    /src/gcc-trunk/gcc/reload1.c:1278
0x10854af7 do_reload
    /src/gcc-trunk/gcc/ira.c:5430
0x10854af7 execute
    /src/gcc-trunk/gcc/ira.c:5589
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <http://gcc.gnu.org/bugs.html> for instructions.
>From gcc-bugs-return-481757-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Mar 26 03:39:44 2015
Return-Path: <gcc-bugs-return-481757-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 88088 invoked by alias); 26 Mar 2015 03:39:44 -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 88040 invoked by uid 48); 26 Mar 2015 03:39:40 -0000
From: "jvdelisle at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/65563] Segfault on reopening fort.xxx file with explicit name
Date: Thu, 26 Mar 2015 08:21:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libfortran
X-Bugzilla-Version: 5.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jvdelisle at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jvdelisle at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-65563-4-516nXyVDGn@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-65563-4@http.gcc.gnu.org/bugzilla/>
References: <bug-65563-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: 2015-03/txt/msg02901.txt.bz2
Content-length: 522

https://gcc.gnu.org/bugzilla/show_bug.cgi?ide563

--- Comment #3 from Jerry DeLisle <jvdelisle at gcc dot gnu.org> ---
(In reply to Thomas Koenig from comment #0)
> This is inspired by
> https://stackoverflow.com/questions/29238857/fortran-error-about-eof-marker/
> ,but is slightly different.
>
> This segfaults:

I cannot reproduce this on trunk (5.0) and I get nothing with
-fsanitize­dress
accept the error message.  This is on x86-64-linux.

So I am at a "works for me" stage here. I will look some more later.


             reply	other threads:[~2015-03-26  3:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-26  8:15 msebor at gcc dot gnu.org [this message]
2015-03-26 20:52 ` [Bug target/65577] " msebor at gcc dot gnu.org
2015-03-26 21:07 ` msebor 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-65577-4@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).