From: Ian Lance Taylor Date: Sat, 24 Jan 2015 00:02:55 +0000 (+0000) Subject: re PR go/63565 (please document that (and why) Go binaries should not be stripped) X-Git-Tag: upstream/12.2.0~57112 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=1aaecd3bed5933e313f8bf86dcb05683678925bc;p=platform%2Fupstream%2Fgcc.git re PR go/63565 (please document that (and why) Go binaries should not be stripped) PR go/63565 * gccgo.texi (Invoking gccgo): Mention that Go programs should not be stripped. * gccgo.texi (C Interoperability): Mention that people should use cgo. From-SVN: r220070 --- diff --git a/gcc/go/ChangeLog b/gcc/go/ChangeLog index d525f5d..7a624c7 100644 --- a/gcc/go/ChangeLog +++ b/gcc/go/ChangeLog @@ -1,5 +1,14 @@ 2015-01-23 Ian Lance Taylor + PR go/63565 + * gccgo.texi (Invoking gccgo): Mention that Go programs should not + be stripped. + + * gccgo.texi (C Interoperability): Mention that people should use + cgo. + +2015-01-23 Ian Lance Taylor + PR go/64595 * go-lang.c (go_langhook_init_options_struct): Set default debug_info_level. diff --git a/gcc/go/gccgo.texi b/gcc/go/gccgo.texi index 45fc9d7..6e4c708 100644 --- a/gcc/go/gccgo.texi +++ b/gcc/go/gccgo.texi @@ -142,6 +142,10 @@ the import data directly from the compiled package. When this package is later linked, the compiled form of the package must be included in the link command. +Go programs must generally be compiled with debugging information, and +@option{-g1} is the default as described below. Stripping a Go +program will generally cause it to misbehave or fail. + @c man end @c man begin OPTIONS gccgo @@ -288,6 +292,11 @@ This is different from the behaviour of other Go compilers. When using @command{gccgo} there is limited interoperability with C, or with C++ code compiled using @code{extern "C"}. +This information is provided largely for documentation purposes. For +ordinary use it is best to build programs with the go tool and then +use @code{import "C"}, as described at +@url{http://golang.org/cmd/cgo}. + @menu * C Type Interoperability:: How C and Go types match up. * Function Names:: How Go functions are named.