Apparently on Solaris 10 a SA_SIGINFO signal handler can be invoked with a nil info argument. I would not have believed it but I've now seen it happen, and the sigaction man page actually says "If the second argument is not equal to NULL, it points to a siginfo_t structure...." So, if that happens, don't crash. Also fix another case where we want to make sure that &T{} does not allocate. Reviewed-on: https://go-review.googlesource.com/33150 From-SVN: r242403 |
||
---|---|---|
.. | ||
gofrontend | ||
ChangeLog | ||
Make-lang.in | ||
README.gcc | ||
config-lang.in | ||
gccgo.texi | ||
go-backend.c | ||
go-c.h | ||
go-gcc-diagnostics.cc | ||
go-gcc.cc | ||
go-gcc.h | ||
go-lang.c | ||
go-linemap.cc | ||
go-location.h | ||
go-sha1.cc | ||
go-system.h | ||
gospec.c | ||
lang-specs.h | ||
lang.opt |
README.gcc
The files in the gofrontend subdirectory are mirrored from the gofrontend project hosted at http://code.google.com/p/gofrontend. These files are the ones in the go subdirectory of that project.