public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeff Law <law@redhat.com>
To: Marek Polacek <polacek@redhat.com>, Andreas Schwab <schwab@suse.de>
Cc: Richard Biener <richard.guenther@gmail.com>,
	       GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Fix middle-end/67133, part 1
Date: Thu, 20 Aug 2015 16:42:00 -0000	[thread overview]
Message-ID: <55D60338.2080306@redhat.com> (raw)
In-Reply-To: <20150820103758.GE2729@redhat.com>

On 08/20/2015 04:37 AM, Marek Polacek wrote:
> On Thu, Aug 20, 2015 at 11:02:17AM +0200, Andreas Schwab wrote:
>> Marek Polacek <polacek@redhat.com> writes:
>>
>>> 	PR middle-end/67133
>>> 	* gimple-ssa-isolate-paths.c
>>> 	(insert_trap_and_remove_trailing_statements): Rename to ...
>>> 	(insert_trap): ... this.  Don't remove trailing statements; split
>>> 	block instead.
>>> 	(find_explicit_erroneous_behaviour): Don't remove all outgoing edges.
>>
>> This breaks go on aarch64:
>>
>> ../../../libgo/go/encoding/gob/decode.go: In function ‘gob.decIgnoreOpFor.pN20_encoding_gob.Decoder’:
>> ../../../libgo/go/encoding/gob/decode.go:843:1: internal compiler error: in operator[], at vec.h:714
>>   func (dec *Decoder) decIgnoreOpFor(wireId typeId) decOp {
>>   ^
>> 0xac5c3b vec<edge_def*, va_gc, vl_embed>::operator[](unsigned int)
>>          ../../gcc/vec.h:714
>> 0xac5c3b extract_true_false_edges_from_block(basic_block_def*, edge_def**, edge_def**)
>>          ../../gcc/tree-cfg.c:8456
>> 0xace9bf gimple_verify_flow_info
>>          ../../gcc/tree-cfg.c:5260
>> 0x6ea1ab verify_flow_info()
>>          ../../gcc/cfghooks.c:260
>> 0xadeca3 cleanup_tree_cfg_noloop
>>          ../../gcc/tree-cfgcleanup.c:739
>> 0xadeca3 cleanup_tree_cfg()
>>          ../../gcc/tree-cfgcleanup.c:788
>> 0x9d21c3 execute_function_todo
>>          ../../gcc/passes.c:1900
>> 0x9d2b07 execute_todo
>>          ../../gcc/passes.c:2005
>
> Whilst I'm struggling with building cross libgo to reproduce this, is
> there something like preprocessed source for go?  So that ideally I'd
> just run ./go1 foo.go?  That'd help tremendously.
The process for finding out what Go's doing is, umm, exceedingly 
difficult.  Though at least for gcc-go, using "-v" will help.

RTH might have some ideas.


Based on the error, I suspect we've got a block ending with a 
GIMPLE_COND with no successors in the CFG.

jeff

  parent reply	other threads:[~2015-08-20 16:41 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-14 11:51 Marek Polacek
2015-08-14 13:19 ` Richard Biener
2015-08-14 13:36   ` Marek Polacek
2015-08-14 14:54     ` Jeff Law
2015-08-14 15:33       ` Marek Polacek
2015-08-14 15:39         ` Jeff Law
2015-08-14 20:12           ` Marek Polacek
2015-08-14 20:36             ` Jeff Law
2015-08-14 21:48               ` Marek Polacek
2015-08-17 17:47                 ` Jeff Law
2015-08-17 18:01                   ` Marek Polacek
2015-08-18  8:47                   ` Richard Biener
2015-08-18 20:09                     ` Marek Polacek
2015-08-19  9:54                       ` Richard Biener
2015-08-19 10:39                         ` Marek Polacek
2015-08-19 14:25                       ` Jeff Law
2015-08-20  9:05                       ` Andreas Schwab
2015-08-20 10:50                         ` Marek Polacek
2015-08-20 10:58                           ` Andreas Schwab
2015-08-20 16:42                           ` Jeff Law [this message]
2015-08-20 16:59                             ` Marek Polacek
2015-08-20 16:59                               ` Jeff Law
2015-08-20 17:02                               ` Marek Polacek
2015-08-20 17:11                                 ` Jeff Law
2015-08-23 10:54                         ` Jan-Benedict Glaw
2015-08-24 15:55                           ` Jeff Law
2015-08-24 16:15                             ` Marek Polacek

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=55D60338.2080306@redhat.com \
    --to=law@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=polacek@redhat.com \
    --cc=richard.guenther@gmail.com \
    --cc=schwab@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).