mirror of
https://gcc.gnu.org/git/gcc.git
synced 2024-11-27 22:03:57 +08:00
6b724427aa
In the Go 1.21 release the package internal/profile imports internal/lazyregexp. That works when bootstrapping with Go 1.17, because that compiler has internal/lazyregep and permits importing it. We also have internal/lazyregexp in libgo, but since it is not installed it is not available for importing. This CL adds internal/lazyregexp to the list of internal packages that are installed for bootstrapping. The Go 1.21, and earlier, releases have a couple of functions in the internal/abi package that are always fully intrinsified. The gofrontend recognizes and intrinsifies those functions as well. However, the gofrontend was also building function descriptors for references to the functions without calling them, which failed because there was nothing to refer to. That is OK for the gc compiler, which guarantees that the functions are only called, not referenced. This CL arranges to not generate function descriptors for these functions. For golang/go#60913 Reviewed-on: https://go-review.googlesource.com/c/gofrontend/+/504798 |
||
|---|---|---|
| .. | ||
| config | ||
| go | ||
| misc/cgo | ||
| runtime | ||
| testsuite | ||
| aclocal.m4 | ||
| check-packages.txt | ||
| config.h.in | ||
| configure | ||
| configure.ac | ||
| goarch.sh | ||
| godeps.sh | ||
| gotool-packages.txt | ||
| libgo-packages.txt | ||
| libgo.imp | ||
| LICENSE | ||
| Makefile.am | ||
| Makefile.in | ||
| match.sh | ||
| MERGE | ||
| merge.sh | ||
| mklinknames.awk | ||
| mkrsysinfo.sh | ||
| mkruntimeinc.sh | ||
| mksigtab.sh | ||
| mksysinfo.sh | ||
| mvifdiff.sh | ||
| PATENTS | ||
| README | ||
| README.gcc | ||
| sysinfo.c | ||
| VERSION | ||
See ../README. This is the runtime support library for the Go programming language. This library is intended for use with the Go frontend. This library should not be stripped when it is installed. Go code relies on being able to look up file/line information, which comes from the debugging info using the libbacktrace library. The library has only been tested on GNU/Linux using glibc, and on Solaris. It should not be difficult to port to other operating systems. Directories: go A copy of the Go library from http://golang.org/, with several changes for gccgo. runtime Runtime functions, written in C, which are called directly by the compiler or by the library. Contributing ============ To contribute patches to the files in this directory, please see http://golang.org/doc/gccgo_contribute.html . The master copy of these files is hosted at http://code.google.com/p/gofrontend . Changes to these files require signing a Google contributor license agreement. If you are the copyright holder, you will need to agree to the individual contributor license agreement at http://code.google.com/legal/individual-cla-v1.0.html. This agreement can be completed online. If your organization is the copyright holder, the organization will need to agree to the corporate contributor license agreement at http://code.google.com/legal/corporate-cla-v1.0.html. If the copyright holder for your code has already completed the agreement in connection with another Google open source project, it does not need to be completed again. Debugging ========= This describes how to test libgo when built as part of gccgo. To test a specific package, cd to the libgo build directory (TARGET/libgo) and run `make PKG/check`. For example, `make bytes/check`. To see the exact commands that it runs, including how the compiler is invoked, run `make GOTESTFLAGS=--trace bytes/check`. This will display the commands if the test fails. If the test passes, the commands and other output will be visible in a file named check-testlog in a subdirectory with the name of the package being checked. In the case of bytes/check, this will create bytes/check-testlog. To leave the test program behind, run `make GOTESTFLAGS=--keep bytes/check`. That will leave a gotestNNNN/test directory in the libgo build directory. In that directory you can run `LD_LIBRARY_PATH=../../.libs ./a.out -test.short` to run the tests. You can run specific failing tests using a -test.run option. You can see the tests being run with the -test.v option. You can run the program under a debugger such as gdb.