Revision tags: v6.2.1, v6.2.0, v6.3.0, v6.0.1, v6.0.0, v6.0.0rc1, v6.1.0, v5.8.3, v5.8.2, v5.8.1, v5.8.0, v5.9.0, v5.8.0rc1, v5.6.3, v5.6.2, v5.6.1, v5.6.0, v5.6.0rc1, v5.7.0, v5.4.3, v5.4.2, v5.4.1, v5.4.0, v5.5.0, v5.4.0rc1, v5.2.2, v5.2.1, v5.2.0, v5.3.0, v5.2.0rc, v5.0.2, v5.0.1, v5.0.0, v5.0.0rc2, v5.1.0, v5.0.0rc1, v4.8.1, v4.8.0, v4.6.2, v4.9.0, v4.8.0rc, v4.6.1 |
|
#
b02d68b2 |
| 12-Oct-2016 |
zrj <rimvydas.jasinskas@gmail.com> |
LTO: Prevent -flto exposing csu internals when linking v2.
Userland applications should not see what is happening in these sources, let alone have behavioural changes for -fxxx flags during linking.
LTO: Prevent -flto exposing csu internals when linking v2.
Userland applications should not see what is happening in these sources, let alone have behavioural changes for -fxxx flags during linking.
Also make sure -flto does *not* get near any of crt1 stuff. Caused lost os version elf notes in utilities and even segfaults in pkg(8).
show more ...
|
Revision tags: v4.6.0, v4.6.0rc2, v4.6.0rc, v4.7.0, v4.4.3, v4.4.2, v4.4.1, v4.4.0, v4.5.0, v4.4.0rc, v4.2.4, v4.3.1, v4.2.3, v4.2.1, v4.2.0, v4.0.6, v4.3.0, v4.2.0rc, v4.0.5, v4.0.4, v4.0.3, v4.0.2, v4.0.1, v4.0.0, v4.0.0rc3, v4.0.0rc2, v4.0.0rc, v4.1.0, v3.8.2, v3.8.1, v3.6.3, v3.8.0, v3.8.0rc2, v3.9.0, v3.8.0rc, v3.6.2, v3.6.1, v3.6.0, v3.7.1, v3.6.0rc, v3.7.0, v3.4.3, v3.4.2, v3.4.0, v3.4.1, v3.4.0rc, v3.5.0, v3.2.2, v3.2.1, v3.2.0, v3.3.0, v3.0.3, v3.0.2, v3.0.1, v3.1.0, v3.0.0 |
|
#
86d7f5d3 |
| 26-Nov-2011 |
John Marino <draco@marino.st> |
Initial import of binutils 2.22 on the new vendor branch
Future versions of binutils will also reside on this branch rather than continuing to create new binutils branches for each new version.
|
Revision tags: v2.12.0, v2.13.0, v2.10.1, v2.11.0, v2.10.0, v2.9.1, v2.8.2, v2.8.1, v2.8.0, v2.9.0, v2.6.3, v2.7.3, v2.6.2, v2.7.2, v2.7.1, v2.6.1, v2.7.0, v2.6.0, v2.5.1, v2.4.1, v2.5.0, v2.4.0, v2.3.2, v2.3.1, v2.2.1 |
|
#
e1da6819 |
| 19-Apr-2009 |
Simon Schubert <corecode@dragonflybsd.org> |
csu: move crt files to /usr/lib
Instead of installing our start files in gcc directories, install the generic ones in /usr/lib. This should make porting other compilers more easy.
Requested-by:
csu: move crt files to /usr/lib
Instead of installing our start files in gcc directories, install the generic ones in /usr/lib. This should make porting other compilers more easy.
Requested-by: hasso@
show more ...
|
Revision tags: v2.2.0, v2.3.0, v2.1.1, v2.0.1 |
|
#
cac7e294 |
| 23-Aug-2007 |
Simon Schubert <corecode@dragonflybsd.org> |
Don't define USED_FOR_TARGET on the command line.
This produces all kinds of side effects, ultimately leading to the csu sources and the compiler being out of sync on compilation, thus triggering an
Don't define USED_FOR_TARGET on the command line.
This produces all kinds of side effects, ultimately leading to the csu sources and the compiler being out of sync on compilation, thus triggering an internal compiler error.
Details for the curious and for historical purposes: Our gcc is configured to work with a ld which can merge ro and rw sections to rw sections. Nevertheless cc1 will enforce sections in one unit to be of one type or the other, i.e. it disallows section flag changes. Sections are usually a compiler internal detail, so a flag change is considered a compiler bug and thus cc1 aborts with an internal compiler error on such occasions.
The csu libs consider themselves as part of the compiler and use section declarations. However if the lib and the compiler don't agree on some settings and are out of sync, the lib will decide to create a rw .eh_frame section (by not declaring a variable constant). If the compiler uses the .eh_frame section as well, like gcc41/amd64 does to store dwarf2 exception rollback information, the above mentioned internal compiler error is triggered.
The essential problem here was that USED_FOR_TARGET will prevent the auto-host.h/dragonfly-native.h config.h-style headers to set the necessary compiler configuration which is also used by the csu libs. By moving it to the place where the gcc people intended it to be, everything works as desired.
show more ...
|
#
fd8b66cd |
| 15-Jan-2007 |
Simon Schubert <corecode@dragonflybsd.org> |
Create startup files from the GCC sources and drop our versions. This places the startup files into the GCC specific lib dir. A short overview is given in lib/csu/README.
This fixes issues with gcc
Create startup files from the GCC sources and drop our versions. This places the startup files into the GCC specific lib dir. A short overview is given in lib/csu/README.
This fixes issues with gcc41 and static binaries.
show more ...
|
#
959124df |
| 04-Apr-2011 |
Sascha Wildner <saw@online.de> |
csu: Adjust some flags etc. to more closely resemble the vendor Makefile.
Also, use ${PICFLAG} instead of -fpic.
Submitted-by: John Marino <draco@marino.st>
|
#
969901d9 |
| 27-Feb-2011 |
Sascha Wildner <saw@online.de> |
gnu/lib/csu: Add -fno-asynchronous-unwind-tables to the CFLAGS.
Quoth FreeBSD's commit msg:
Often reported issue with newer ld is: error in /usr/lib/crtendS.o(.eh_frame); no .eh_frame_hdr table wil
gnu/lib/csu: Add -fno-asynchronous-unwind-tables to the CFLAGS.
Quoth FreeBSD's commit msg:
Often reported issue with newer ld is: error in /usr/lib/crtendS.o(.eh_frame); no .eh_frame_hdr table will be created.
The issue is that crtend is compiled with unwind table, and also it places the special CIE into the .eh_frame indicating the end of section, that is located before generated unwind table. New ld has assertion that verifies that closing CIE is indeed the last CIE, causing the crypting message to be issued, and refusing to generate dwarf unwind.
Add -fno-asynchronous-unwind-tables to disable unwind table generation for crtbegin/crtend.
Taken-from: FreeBSD
show more ...
|