diff options
| author | Ian Lance Taylor <ian@gcc.gnu.org> | 2016-02-10 18:30:27 +0000 |
|---|---|---|
| committer | Ian Lance Taylor <ian@gcc.gnu.org> | 2016-02-10 18:30:27 +0000 |
| commit | 931f434a72bdc01b58dfc88264e36abd86b19c3d (patch) | |
| tree | 386d8d63867ca51e9229c2f90dff88b83421574f /gcc/go | |
| parent | e03dd76578bb5e8b6d5ba2a2628d349bd5c822bf (diff) | |
| download | gcc-931f434a72bdc01b58dfc88264e36abd86b19c3d.zip gcc-931f434a72bdc01b58dfc88264e36abd86b19c3d.tar.gz gcc-931f434a72bdc01b58dfc88264e36abd86b19c3d.tar.bz2 | |
re PR go/66904 (cmd/go: "#cgo pkg-config:" comments do not work with gccgo)
PR go/66904
cmd/go: fix "#cgo pkg-config:" comments with gccgo
Copy of https://golang.org/cl/18790 by Michael Hudson-Doyle.
The unique difficulty of #cgo pkg-config is that the linker flags are recorded
when the package is compiled but (obviously) must be used when the package is
linked into an executable -- so the flags need to be stored on disk somewhere.
As it happens cgo already writes out a _cgo_flags file: nothing uses it
currently, but this change adds it to the lib$pkg.a file when compiling a
package, reads it out when linking (and passes a version of the .a file with
_cgo_flags stripped out of it to the linker). It's all fairly ugly but it works
and I can't really think of any way of reducing the essential level of
ugliness.
Update golang/go#11739.
GCC PR 66904.
Reviewed-on: https://go-review.googlesource.com/19431
From-SVN: r233290
Diffstat (limited to 'gcc/go')
| -rw-r--r-- | gcc/go/gofrontend/MERGE | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/gcc/go/gofrontend/MERGE b/gcc/go/gofrontend/MERGE index 23f1bfe..fee5168 100644 --- a/gcc/go/gofrontend/MERGE +++ b/gcc/go/gofrontend/MERGE @@ -1,4 +1,4 @@ -4cec4c5db5b054c5536ec5c50ee7aebec83563bc +28a9dfbc3cda0bf7fd4f3fb1506c547f6cdf41a5 The first line of this file holds the git revision number of the last merge done from the gofrontend repository. |