Go to file
Corinna Vinschen dcab768cb9 Cygwin: cygtls: fix context alignment
A hang was encountered, apparently triggered by commit 63b503916d,
changing tls_pathbufs from malloc'ed to HeapAlloc'ed memory.  After
lengthy debugging it transpired that adding the heap handle to the
tls_pathbuf struct added 8 bytes to the cygtls area, thus moving
the "context" member by 8 bytes, too, so it was suddently unaligned.

Fix this for now by changing the alignment.

Fix this once and for all, by adding code to the gentls_offsets script
to check if the alignment of the "context" member is 16 bytes.  If not,
print a matching error message, remove the just generated file, and exit
with error.

FIXME: It would be really nice to find a way to auomate the correct
alignment of the "context" member, but I don't see any way to use
alignment attributes to get what we need here.

Signed-off-by: Corinna Vinschen <corinna@vinschen.de>
2022-08-29 15:18:53 +02:00
.github/workflows Cygwin: CI: Drop i686 builds 2022-05-16 13:36:51 +01:00
config Merge autoconf / automake update changes from GCC. 2022-01-17 04:30:37 -05:00
etc etc: switch to automake 2021-11-10 20:14:00 -05:00
include Sync with upstream gcc. 2016-06-23 15:54:55 -04:00
libgloss libgloss: riscv: Convert to non-recursive automake 2022-08-26 16:47:48 +02:00
newlib Fix problem with _newlib_version.h not being filled in correctly 2022-08-22 17:55:23 -04:00
texinfo
winsup Cygwin: cygtls: fix context alignment 2022-08-29 15:18:53 +02:00
.appveyor.yml Cygwin: CI: Drop i686 builds 2022-05-16 13:36:51 +01:00
.gitattributes Add .gitattributes 2015-03-09 20:53:11 +01:00
.gitignore Bump to autoconf 2.69 and automake 1.15.1 2022-01-12 07:05:02 -05:00
COPYING
COPYING.LIB Sync toplevel with upstream GCC. 2016-03-22 10:25:20 +01:00
COPYING.LIBGLOSS Update the address of the FSF in the copyright notice of files which were using the old address. 2021-11-10 20:14:00 -05:00
COPYING.NEWLIB newlib: drop phoenix support 2022-03-28 23:17:06 -04:00
COPYING3
COPYING3.LIB
ChangeLog Update the address of the FSF in the copyright notice of files which were using the old address. 2021-11-10 20:14:00 -05:00
MAINTAINERS MAINTAINERS: clarify policy with config/ (and other top level files) 2012-05-12 03:10:17 +00:00
Makefile.def Sync with upstream gcc. 2016-06-23 15:54:55 -04:00
Makefile.in GCC: Pass --plugin to AR and RANLIB 2022-01-12 08:43:05 -05:00
Makefile.tpl GCC: Pass --plugin to AR and RANLIB 2022-01-12 08:43:05 -05:00
README
README-maintainer-mode Bump to autoconf 2.69 and automake 1.15.1 2022-01-12 07:05:02 -05:00
ar-lib Bump to autoconf 2.69 and automake 1.15.1 2022-01-12 07:05:02 -05:00
compile Sync toplevel with upstream GCC. 2016-03-22 10:25:20 +01:00
config-ml.in Sync toplevel with upstream GCC. 2016-03-22 10:25:20 +01:00
config.guess Bump config.guess and config.sub 2021-02-24 11:03:28 +01:00
config.rpath
config.sub Bump config.guess and config.sub 2021-02-24 11:03:28 +01:00
configure Add support for the haiku operating system. These are the os support patches we have been grooming and maintaining for quite a few years over on git.haiku-os.org. All of these architectures are working and most have been stable for quite some time. 2022-01-12 08:43:25 -05:00
configure.ac Add support for the haiku operating system. These are the os support patches we have been grooming and maintaining for quite a few years over on git.haiku-os.org. All of these architectures are working and most have been stable for quite some time. 2022-01-12 08:43:25 -05:00
depcomp Sync toplevel with upstream GCC. 2016-03-22 10:25:20 +01:00
djunpack.bat
install-sh Sync toplevel with upstream GCC. 2016-03-22 10:25:20 +01:00
libtool.m4 libtool.m4: fix nm BSD flag detection 2022-01-12 08:49:10 -05:00
ltgcc.m4
ltmain.sh PR target/59788 2014-02-05 13:17:47 +00:00
ltoptions.m4
ltsugar.m4
ltversion.m4
lt~obsolete.m4
makefile.vms
missing Sync toplevel with upstream GCC. 2016-03-22 10:25:20 +01:00
mkdep Use remove-advertising-clause script to edit BSD licenses 2020-01-29 19:03:31 +01:00
mkinstalldirs Sync toplevel with upstream GCC. 2016-03-22 10:25:20 +01:00
move-if-change Sync toplevel with upstream GCC. 2016-03-22 10:25:20 +01:00
multilib.am Merge autoconf / automake update changes from GCC. 2022-01-17 04:30:37 -05:00
setup.com
src-release * src-release (do-proto-toplevel): Support subdir-path-prefixed 2013-10-15 20:45:52 +00:00
symlink-tree
test-driver Bump to autoconf 2.69 and automake 1.15.1 2022-01-12 07:05:02 -05:00
ylwrap Sync toplevel with upstream GCC. 2016-03-22 10:25:20 +01:00

README

		   README for GNU development tools

This directory contains various GNU compilers, assemblers, linkers, 
debuggers, etc., plus their support routines, definitions, and documentation.

If you are receiving this as part of a GDB release, see the file gdb/README.
If with a binutils release, see binutils/README;  if with a libg++ release,
see libg++/README, etc.  That'll give you info about this
package -- supported targets, how to use it, how to report bugs, etc.

It is now possible to automatically configure and build a variety of
tools with one command.  To build all of the tools contained herein,
run the ``configure'' script here, e.g.:

	./configure 
	make

To install them (by default in /usr/local/bin, /usr/local/lib, etc),
then do:
	make install

(If the configure script can't determine your type of computer, give it
the name as an argument, for instance ``./configure sun4''.  You can
use the script ``config.sub'' to test whether a name is recognized; if
it is, config.sub translates it to a triplet specifying CPU, vendor,
and OS.)

If you have more than one compiler on your system, it is often best to
explicitly set CC in the environment before running configure, and to
also set CC when running make.  For example (assuming sh/bash/ksh):

	CC=gcc ./configure
	make

A similar example using csh:

	setenv CC gcc
	./configure
	make

Much of the code and documentation enclosed is copyright by
the Free Software Foundation, Inc.  See the file COPYING or
COPYING.LIB in the various directories, for a description of the
GNU General Public License terms under which you can copy the files.

REPORTING BUGS: Again, see gdb/README, binutils/README, etc., for info
on where and how to report problems.