<pre class="notranslate">The deadline support in lookupIPDeadline is apparently not a real deadline, in the sense
that a goroutine is leaking on every lookup that does not return timely.

I have a bug report for mgo where someone got to 50k+ goroutines hanging on it:

<a href="https://jira.mongodb.org/browse/MGO-41" rel="nofollow">https://jira.mongodb.org/browse/MGO-41</a>

I'll have to do something else as I need to support existing releases, but it'd be good
to get this fixed so that deadlines are real, at some point.</pre>
<pre class="notranslate">What steps will reproduce the problem?

GC=gccgo go build sg.go

What is the expected output?

makes it to the link step with 6g

What do you see instead?

compile errors with gccgo:

_cgo_defun.c:36:1: error: unknown type name ‘byte’
_cgo_defun.c:37:1: error: stray ‘\302’ in program
_cgo_defun.c:37:1: error: stray ‘\267’ in program

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

gccgo

Which operating system are you using?

linux

Which revision are you using?  (hg identify)

gccgo (GCC) 4.7.0 20120302
commit f2b34014d56c08d8fa5d93a2329e92046215de6d
git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@184877
138bc75d-0d04-0410-961f-82ee72b054a4

Please provide any additional information below.

The problematic lines in _cgo_defun.c:

extern byte *sg_lib_version_str;
void *·_Cvar_sg_lib_version_str = &amp;sg_lib_version_str;</pre>
<p dir="auto">Attachments:</p>
<ol dir="auto">
<li><a href="https://storage.googleapis.com/go-attachment/3183/0/sg.go" rel="nofollow">sg.go</a> (138 bytes)</li>
</ol>