public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "zsojka at seznam dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/65496] New: ICE: in maybe_record_trace_start, at dwarf2cfi.c:2318 with -O3 -fsched2-use-superblocks -mavx512dq --param=max-pending-list-length=0
Date: Fri, 20 Mar 2015 16:55:00 -0000	[thread overview]
Message-ID: <bug-65496-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 65496
           Summary: ICE: in maybe_record_trace_start, at dwarf2cfi.c:2318
                    with -O3 -fsched2-use-superblocks -mavx512dq
                    --param=max-pending-list-length=0
           Product: gcc
           Version: 5.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: target
          Assignee: unassigned at gcc dot gnu.org
          Reporter: zsojka at seznam dot cz

Created attachment 35075
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=35075&action=edit
reduced testcase

Compiler output:
$ gcc -O3 -fsched2-use-superblocks -mavx512dq --param=max-pending-list-length=0
testcase.c         
testcase.c: In function 'foo':
testcase.c:6:1: internal compiler error: in maybe_record_trace_start, at
dwarf2cfi.c:2318
 }
 ^
0x8843d0 maybe_record_trace_start
        /mnt/svn/gcc-trunk/gcc/dwarf2cfi.c:2318
0x885348 scan_trace
        /mnt/svn/gcc-trunk/gcc/dwarf2cfi.c:2496
0x885c9a create_cfi_notes
        /mnt/svn/gcc-trunk/gcc/dwarf2cfi.c:2650
0x885c9a execute_dwarf2_frame
        /mnt/svn/gcc-trunk/gcc/dwarf2cfi.c:3006
0x885c9a execute
        /mnt/svn/gcc-trunk/gcc/dwarf2cfi.c:3486
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.

$ gcc -v
Using built-in specs.
COLLECT_GCC=/mnt/svn/gcc-trunk/binary-latest/bin/gcc
COLLECT_LTO_WRAPPER=/mnt/svn/gcc-trunk/binary-221530-lto-fortran-checking-yes-rtl-df/libexec/gcc/x86_64-unknown-linux-gnu/5.0.0/lto-wrapper
Target: x86_64-unknown-linux-gnu
Configured with: /mnt/svn/gcc-trunk//configure --enable-checking=yes,rtl,df
--enable-languages=c,c++,lto,fortran
--prefix=/mnt/svn/gcc-trunk/binary-221530-lto-fortran-checking-yes-rtl-df/
--without-cloog --without-ppl
Thread model: posix
gcc version 5.0.0 20150320 (experimental) (GCC) 

Tested revisions:
r221530 - ICE


             reply	other threads:[~2015-03-20 16:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-20 16:55 zsojka at seznam dot cz [this message]
2015-03-20 18:00 ` [Bug target/65496] " jakub at gcc dot gnu.org
2015-03-20 18:10 ` jakub at gcc dot gnu.org
2015-03-23 15:57 ` rth 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-65496-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).