gccgo: internal compiler errors

[alberts]

What steps will reproduce the problem?

find -mindepth 1 -type d | xargs -n 1 -I DIR sh -c 'echo DIR && cd DIR
&& echo DIR && gccgo -o foo *.go' 2>&1 | grep internal | sort -u

ls *.go | xargs -n 1 gccgo -o foo 2>&1 | grep internal | sort -u

What do you see instead?

go1: internal compiler error: in do_type_descriptor, at go/gofrontend/types.cc:1817
go1: internal compiler error: in get_function_tree, at go/gofrontend/expressions.cc:10097
go1: internal compiler error: in do_get_tree, at go/gofrontend/types.cc:7391
go1: internal compiler error: in fill_in_array_tree, at go/gofrontend/types.cc:4476
go1: internal compiler error: in type, at go/gofrontend/types.cc:6983
go1: internal compiler error: in write_initialization_function, at
go/gofrontend/gogo-tree.cc:387
go1: internal compiler error: Segmentation fault

Which compiler are you using (5g, 6g, 8g, gccgo)?

gccgo

Which operating system are you using?

linux

Which revision are you using?  (hg identify)

URL: svn://gcc.gnu.org/svn/gcc/trunk
Repository Root: svn://gcc.gnu.org/svn/gcc
Repository UUID: 138bc75d-0d04-0410-961f-82ee72b054a4
Revision: 170646

Attachments:

1. bork.tar.bz2 (156847 bytes)

[ianlancetaylor]

Comment 1:

Labels changed: added gccgo.

Owner changed to i...@golang.org.

Status changed to Accepted.

[alberts]

Comment 2:

It seems these have all been fixed?

[ianlancetaylor]

Comment 3:

If they have, it's an accidental consequence of the gcc backend interface work.  That
work is changing the set of ways the compiler can fail, so I was planning to cycle back
to these failures after it was complete.

[rsc]

Comment 4:

Labels changed: added priority-later, removed priority-medium.

[rsc]

Comment 5:

Labels changed: added priority-go1.

[robpike]

Comment 6:

Owner changed to builder@golang.org.

[ianlancetaylor]

Comment 7:

These all work now, in the sense that gccgo no longer crashes on them.

Owner changed to @ianlancetaylor.

Status changed to Fixed.