aboutsummaryrefslogtreecommitdiff
path: root/libgo/go/runtime/testdata/testprogcgo
AgeCommit message (Collapse)AuthorFilesLines
2024-10-18runtime/testdata: fix for C23 nullptr keywordIan Lance Taylor1-2/+2
Backport https://go.dev/cl/620955 from main repo. Original description: src/runtime/testdata/testprogcgo/threadprof.go contains C code with a variable called nullptr. This conflicts with the nullptr keyword in the C23 revision of the C standard (showing up as gccgo test build failures when updating GCC to use C23 by default when building C code). Rename that variable to nullpointer to avoid the clash with the keyword (any other name that's not a keyword would work just as well). Reviewed-on: https://go-review.googlesource.com/c/gofrontend/+/621059
2022-03-16libgo: update to final Go 1.18 releaseIan Lance Taylor1-1/+1
Reviewed-on: https://go-review.googlesource.com/c/gofrontend/+/393377
2022-02-18libgo: update to Go1.18rc1 releaseIan Lance Taylor2-2/+94
Reviewed-on: https://go-review.googlesource.com/c/gofrontend/+/386594
2022-02-11libgo: update to Go1.18beta2Ian Lance Taylor21-34/+169
gotools/ * Makefile.am (go_cmd_cgo_files): Add ast_go118.go (check-go-tool): Copy golang.org/x/tools directories. * Makefile.in: Regenerate. Reviewed-on: https://go-review.googlesource.com/c/gofrontend/+/384695
2021-08-12libgo: update to Go1.17rc2Ian Lance Taylor14-17/+153
Reviewed-on: https://go-review.googlesource.com/c/gofrontend/+/341629
2020-12-30libgo: update to Go1.16beta1 releaseIan Lance Taylor5-60/+31
This does not yet include support for the //go:embed directive added in this release. * Makefile.am (check-runtime): Don't create check-runtime-dir. (mostlyclean-local): Don't remove check-runtime-dir. (check-go-tool, check-vet): Copy in go.mod and modules.txt. (check-cgo-test, check-carchive-test): Add go.mod file. * Makefile.in: Regenerate. Reviewed-on: https://go-review.googlesource.com/c/gofrontend/+/280172
2020-12-08libgo: update to 1.15.6 releaseIan Lance Taylor1-0/+95
Reviewed-on: https://go-review.googlesource.com/c/gofrontend/+/276153
2020-08-01libgo: update to go1.15rc1Ian Lance Taylor2-0/+302
Reviewed-on: https://go-review.googlesource.com/c/gofrontend/+/245157
2020-01-21libgo: update to Go1.14beta1Ian Lance Taylor2-7/+46
Reviewed-on: https://go-review.googlesource.com/c/gofrontend/+/214297
2019-09-06libgo: update to Go 1.13beta1 releaseIan Lance Taylor2-5/+12
Reviewed-on: https://go-review.googlesource.com/c/gofrontend/+/193497 From-SVN: r275473
2019-02-01runtime, sync: use __atomic intrinsics instead of __syncIan Lance Taylor3-7/+7
GCC has supported the __atomic intrinsics since 4.7. They are better than the __sync intrinsics in that they specify a memory model and, more importantly for our purposes, they are reliably implemented either in the compiler or in libatomic. Fixes https://gcc.gnu.org/PR52084 Reviewed-on: https://go-review.googlesource.com/c/160820 From-SVN: r268458
2019-01-18libgo: update to Go1.12beta2Ian Lance Taylor3-2/+28
Reviewed-on: https://go-review.googlesource.com/c/158019 gotools/: * Makefile.am (go_cmd_vet_files): Update for Go1.12beta2 release. (GOTOOLS_TEST_TIMEOUT): Increase to 600. (check-runtime): Export LD_LIBRARY_PATH before computing GOARCH and GOOS. (check-vet): Copy golang.org/x/tools into check-vet-dir. * Makefile.in: Regenerate. gcc/testsuite/: * go.go-torture/execute/names-1.go: Stop using debug/xcoff, which is no longer externally visible. From-SVN: r268084
2018-09-24libgo: update to Go 1.11Ian Lance Taylor3-2/+29
Reviewed-on: https://go-review.googlesource.com/136435 gotools/: * Makefile.am (mostlyclean-local): Run chmod on check-go-dir to make sure it is writable. (check-go-tools): Likewise. (check-vet): Copy internal/objabi to check-vet-dir. * Makefile.in: Rebuild. From-SVN: r264546
2018-02-08runtime: get missing function name from symbol tableIan Lance Taylor1-0/+40
If we trace back through code that has no debug info, as when calling through C code compiled with -g0, we won't have a function name. Try to fetch the function name using the symbol table. Adding the test case revealed that gotest failed to use the gccgo tag when matching files, so add that. Reviewed-on: https://go-review.googlesource.com/92756 From-SVN: r257495
2018-02-08libgo: update to Go1.10rc2Ian Lance Taylor1-0/+28
Reviewed-on: https://go-review.googlesource.com/92736 From-SVN: r257493
2018-01-17libgo: update to Go1.10beta2 releaseIan Lance Taylor1-5/+1
Reviewed-on: https://go-review.googlesource.com/87897 From-SVN: r256794
2018-01-09libgo: update to Go1.10beta1Ian Lance Taylor7-2/+329
Update the Go library to the 1.10beta1 release. Requires a few changes to the compiler for modifications to the map runtime code, and to handle some nowritebarrier cases in the runtime. Reviewed-on: https://go-review.googlesource.com/86455 gotools/: * Makefile.am (go_cmd_vet_files): New variable. (go_cmd_buildid_files, go_cmd_test2json_files): New variables. (s-zdefaultcc): Change from constants to functions. (noinst_PROGRAMS): Add vet, buildid, and test2json. (cgo$(EXEEXT)): Link against $(LIBGOTOOL). (vet$(EXEEXT)): New target. (buildid$(EXEEXT)): New target. (test2json$(EXEEXT)): New target. (install-exec-local): Install all $(noinst_PROGRAMS). (uninstall-local): Uninstasll all $(noinst_PROGRAMS). (check-go-tool): Depend on $(noinst_PROGRAMS). Copy down objabi.go. (check-runtime): Depend on $(noinst_PROGRAMS). (check-cgo-test, check-carchive-test): Likewise. (check-vet): New target. (check): Depend on check-vet. Look at cmd_vet-testlog. (.PHONY): Add check-vet. * Makefile.in: Rebuild. From-SVN: r256365
2017-09-20runtime: restore "goroutine in C code" messageIan Lance Taylor1-0/+1
In the 1.9 upgrade I took out the word "goroutine" from a traceback showing a goroutine running in C code, to let TestCgoNumGoroutine pass. However, it turns out that some code is actually checking for that string; for example, https://github.com/grpc/grpc-go/blob/master/test/leakcheck/leakcheck.go#L44 So keep the message the same, and change the test. Reviewed-on: https://go-review.googlesource.com/64850 From-SVN: r252991
2017-09-14libgo: update to go1.9Ian Lance Taylor2-2/+105
Reviewed-on: https://go-review.googlesource.com/63753 From-SVN: r252767
2017-07-21runtime: allocate more stack space in CgoCallbackGC testIan Lance Taylor1-1/+3
Allocate enough stack space so that the test will work on a system that does not support split stacks. This test is actually not very meaningful for gccgo at present, but it doesn't hurt to keep running it. Updates golang/go#20931 Reviewed-on: https://go-review.googlesource.com/50630 From-SVN: r250433
2017-06-22runtime: don't assume that _ = *s will panic if s is nilIan Lance Taylor1-2/+3
With the gc toolchain apparently var s *string _ = *s is enough to panic with a nil pointer dereference. The gccgo compiler will simply discard the dereference, which I think is a reasonable and acceptable optimization. Change the tests to use an exported variable instead. The tests are not currently run, but they will be with a later patch to gotools. Reviewed-on: https://go-review.googlesource.com/46450 From-SVN: r249562
2017-06-22runtime: don't build test files that use SetCgoTraceback for gccgoIan Lance Taylor6-0/+10
The gofrontend doesn't support the runtime.SetCgoTraceback function, which is specifically for handling mixed Go and C tracebacks. Use a build tag to avoid compiling the runtime/testdata/testprogcgo files that refer to SetCgoTraceback. These files are not currently compiled anyhow, but they will be with a future gotools patch. Reviewed-on: https://go-review.googlesource.com/46452 From-SVN: r249556
2017-06-22runtime: build testprogcgo with -pthreadIan Lance Taylor1-0/+3
Building this test with gccgo requires an explicit -pthread option to be passed to the C compiler, so that it links against -lpthread. This test is not built today, but it will be soon with a future patch. Reviewed-on: https://go-review.googlesource.com/46451 From-SVN: r249555
2017-02-17libgo: update to final Go 1.8 releaseIan Lance Taylor2-4/+4
Along with the update this fixes a problem that was always present but only showed up with the new reflect test. When a program used a **unsafe.Pointer and stored the value in an interface type, the generated type descriptor pointed to the GC data for *unsafe.Pointer. It did that by name, but we were not generating a variable with the right name. Reviewed-on: https://go-review.googlesource.com/37144 From-SVN: r245535
2017-01-23libgo: update to go1.8rc2Ian Lance Taylor3-0/+140
Fix a bug in the generation of the hash value in reflect.FuncOf. The merge script missed a bunch of testdata files over the years. Copy them over. Reviewed-on: https://go-review.googlesource.com/35570 From-SVN: r244835
2017-01-14libgo: update to Go 1.8 release candidate 1Ian Lance Taylor5-15/+211
Compiler changes: * Change map assignment to use mapassign and assign value directly. * Change string iteration to use decoderune, faster for ASCII strings. * Change makeslice to take int, and use makeslice64 for larger values. * Add new noverflow field to hmap struct used for maps. Unresolved problems, to be fixed later: * Commented out test in go/types/sizes_test.go that doesn't compile. * Commented out reflect.TestStructOf test for padding after zero-sized field. Reviewed-on: https://go-review.googlesource.com/35231 gotools/: Updates for Go 1.8rc1. * Makefile.am (go_cmd_go_files): Add bug.go. (s-zdefaultcc): Write defaultPkgConfig. * Makefile.in: Rebuild. From-SVN: r244456
2016-07-22libgo: update to go1.7rc3Ian Lance Taylor16-10/+510
Reviewed-on: https://go-review.googlesource.com/25150 From-SVN: r238662
2016-02-03libgo: Update to go1.6rc1.Ian Lance Taylor11-0/+566
Reviewed-on: https://go-review.googlesource.com/19200 From-SVN: r233110
generated by cgit v1.1 at 2025-08-07 14:30:50 +0000