Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

gccgo: internal compiler errors #1575

Closed
alberts opened this issue Mar 3, 2011 · 7 comments
Closed

gccgo: internal compiler errors #1575

alberts opened this issue Mar 3, 2011 · 7 comments
Milestone

Comments

@alberts
Copy link
Contributor

@alberts alberts commented Mar 3, 2011

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
Copy link
Contributor

@ianlancetaylor ianlancetaylor commented Mar 3, 2011

Comment 1:

Labels changed: added gccgo.

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

Status changed to Accepted.

@alberts
Copy link
Contributor Author

@alberts alberts commented May 16, 2011

Comment 2:

It seems these have all been fixed?

@ianlancetaylor
Copy link
Contributor

@ianlancetaylor ianlancetaylor commented May 16, 2011

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
Copy link
Contributor

@rsc rsc commented Dec 9, 2011

Comment 4:

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

@rsc
Copy link
Contributor

@rsc rsc commented Dec 12, 2011

Comment 5:

Labels changed: added priority-go1.

@robpike
Copy link
Contributor

@robpike robpike commented Jan 13, 2012

Comment 6:

Owner changed to builder@golang.org.

@ianlancetaylor
Copy link
Contributor

@ianlancetaylor ianlancetaylor commented Feb 16, 2012

Comment 7:

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

Owner changed to @ianlancetaylor.

Status changed to Fixed.

@rsc rsc added this to the Go1 milestone Apr 10, 2015
@rsc rsc removed the priority-go1 label Apr 10, 2015
@golang golang locked and limited conversation to collaborators Jun 24, 2016
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants