diff options
| author | Ian Lance Taylor <ian@gcc.gnu.org> | 2019-02-15 01:57:51 +0000 |
|---|---|---|
| committer | Ian Lance Taylor <ian@gcc.gnu.org> | 2019-02-15 01:57:51 +0000 |
| commit | 8a9f2a6bbd6bdf164ca987edac34ac72447881a5 (patch) | |
| tree | 0722c462bd08d8478a0d1861b10b9f966193505e /libgo/runtime/go-caller.c | |
| parent | c8530c410972f09b88bb143e5e5a4910bd72b2ee (diff) | |
| download | gcc-8a9f2a6bbd6bdf164ca987edac34ac72447881a5.zip gcc-8a9f2a6bbd6bdf164ca987edac34ac72447881a5.tar.gz gcc-8a9f2a6bbd6bdf164ca987edac34ac72447881a5.tar.bz2 | |
compiler, runtime: harmonize types referenced by both C and Go
Compiling with LTO revealed a number of cases in the runtime and
standard library where C and Go disagreed about the type of an object or
function (or where Go and code generated by the compiler disagreed). In
all cases the underlying representation was the same (e.g., uintptr vs.
void*), so this wasn't causing actual problems, but it did result in a
number of annoying warnings when compiling with LTO.
Reviewed-on: https://go-review.googlesource.com/c/160700
From-SVN: r268923
Diffstat (limited to 'libgo/runtime/go-caller.c')
| -rw-r--r-- | libgo/runtime/go-caller.c | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/libgo/runtime/go-caller.c b/libgo/runtime/go-caller.c index 6fe4340..2143446 100644 --- a/libgo/runtime/go-caller.c +++ b/libgo/runtime/go-caller.c @@ -192,12 +192,12 @@ struct caller_ret _Bool ok; }; -struct caller_ret Caller (int n) __asm__ (GOSYM_PREFIX "runtime.Caller"); +struct caller_ret Caller (intgo n) __asm__ (GOSYM_PREFIX "runtime.Caller"); /* Implement runtime.Caller. */ struct caller_ret -Caller (int skip) +Caller (intgo skip) { struct caller_ret ret; Location loc; |