From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: Andreas Schwab <schwab@suse.de>
Cc: Marek Polacek <polacek@redhat.com>,
Richard Biener <richard.guenther@gmail.com>,
Jeff Law <law@redhat.com>, GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Fix middle-end/67133, part 1
Date: Sun, 23 Aug 2015 10:54:00 -0000 [thread overview]
Message-ID: <20150823104038.GI24297@lug-owl.de> (raw)
In-Reply-To: <mvm37zebaee.fsf@hawking.suse.de>
[-- Attachment #1: Type: text/plain, Size: 1890 bytes --]
On Thu, 2015-08-20 11:02:17 +0200, Andreas Schwab <schwab@suse.de> 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
> "And now for something completely different."
Not quite. As it seems, it breaks any build:
configure --prefix=... --disable-multilib --enable-languages=all,ada,go
make
Seems the Go code triggers this ICE, so you just need to enable Go.
MfG, JBG
--
Jan-Benedict Glaw jbglaw@lug-owl.de +49-172-7608481
Signature of: Eine Freie Meinung in einem Freien Kopf
the second : für einen Freien Staat voll Freier Bürger.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2015-08-23 10:40 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
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 [this message]
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=20150823104038.GI24297@lug-owl.de \
--to=jbglaw@lug-owl.de \
--cc=gcc-patches@gcc.gnu.org \
--cc=law@redhat.com \
--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).