public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Alan Lawrence <alan.lawrence@arm.com>
To: Richard Biener <rguenther@suse.de>
Cc: Tom de Vries <Tom_deVries@mentor.com>,
	"gcc-patches@gnu.org" <gcc-patches@gnu.org>,
		Jakub Jelinek <jakub@redhat.com>
Subject: Re: [PATCH] Improve verification of loop->latch in verify_loop_structure
Date: Thu, 26 Nov 2015 11:46:00 -0000	[thread overview]
Message-ID: <CAOckXuM_tSyTiWqoVTTLhjcNEdC86k=5SWTHkeTWAWr-yyaY4A@mail.gmail.com> (raw)
In-Reply-To: <alpine.LSU.2.11.1511251144120.4884@t29.fhfr.qr>

This caused an ICE compiling value.c from gdb on
aarch64-none-linux-gnu; the testcase, after preprocessing on aarch64,
ICEs on both aarch64 and x86_64, but is about 1MB - I'm working on
reducing that down to something small enough to post...

$ ./gcc/xgcc -B ./gcc -O2 -g value.c
../../binutils-gdb/gdb/value.c: In function ‘show_convenience’:
../../binutils-gdb/gdb/value.c:2615:1: error: loop 3’s latch is missing
../../binutils-gdb/gdb/value.c:2615:1: internal compiler error: in
verify_loop_structure, at cfgloop.c:1669
0x71e653 verify_loop_structure()
        /work/alalaw01/src2/gcc/gcc/cfgloop.c:1669
0x97c6ae checking_verify_loop_structure
        /work/alalaw01/src2/gcc/gcc/cfgloop.h:325
0x97c6ae loop_optimizer_init(unsigned int)
        /work/alalaw01/src2/gcc/gcc/loop-init.c:106
0x97c78a rtl_loop_init
        /work/alalaw01/src2/gcc/gcc/loop-init.c:398
0x97c78a execute
        /work/alalaw01/src2/gcc/gcc/loop-init.c:425

--Alan

  reply	other threads:[~2015-11-26 11:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-22 23:29 [PATCH] Check NULL " Tom de Vries
2015-11-23 10:29 ` Richard Biener
2015-11-24 15:19   ` [PATCH] Improve verification of " Tom de Vries
2015-11-25 10:44     ` Richard Biener
2015-11-26 11:46       ` Alan Lawrence [this message]
2015-11-26 11:57         ` Alan Lawrence
2015-11-26 12:16         ` Richard Biener
2015-11-26 14:44           ` Tom de Vries

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='CAOckXuM_tSyTiWqoVTTLhjcNEdC86k=5SWTHkeTWAWr-yyaY4A@mail.gmail.com' \
    --to=alan.lawrence@arm.com \
    --cc=Tom_deVries@mentor.com \
    --cc=gcc-patches@gnu.org \
    --cc=jakub@redhat.com \
    --cc=rguenther@suse.de \
    /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).