b0147ac2e6
PR go/79037 compiler, runtime: align gc data for m68k The current GC requires that the gc data be aligned to at least a 4 byte boundary, because it uses the lower two bits of the address for flags (see LOOP and PRECISE in runtime/mgc0.c). As the gc data is stored as a [...]uintptr, that is normally always true. However, on m68k, that only guarantees 2 byte alignment. Fix it by forcing the alignment. The parfor code used by the current GC requires that the parfor data be aligned to at least an 8 byte boundary. The code in parfor.c verifies this. This is normally true, as the data uses uint64_t values, but, again, this must be enforced explicitly on m68k. Fixes GCC PR 79037. Reviewed-on: https://go-review.googlesource.com/35478 From-SVN: r244824 |
||
---|---|---|
.. | ||
config | ||
go | ||
runtime | ||
testsuite | ||
aclocal.m4 | ||
config.h.in | ||
configure | ||
configure.ac | ||
godeps.sh | ||
LICENSE | ||
Makefile.am | ||
Makefile.in | ||
match.sh | ||
MERGE | ||
merge.sh | ||
mkrsysinfo.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.