summaryrefslogtreecommitdiffstats
path: root/lib/csu/i386-elf
Commit message (Collapse)AuthorAgeFilesLines
* All FreeBSD platforms are elf: move i386-elf to i386emaste2015-05-195-269/+0
| | | | | | | | This was a leftover from when we had both i386 a.out and ELF. Reviewed by: kib, imp Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D2591
* Ensure the cross assembler, linker and objcopy are used for the build32dim2015-04-021-2/+2
| | | | | | | | stage, just like for the regular world stage. Reviewed by: rodrigc, imp, bapt, emaste MFC after: 1 week Differential Revision: https://reviews.freebsd.org/D2187
* Use bsd.lib.mk here as all other csu Makefiles do.bdrewery2014-08-191-7/+11
| | | | | | | | | This effectively reverts r124752. There's no reason this should be different. It resulted in needing NO_PIE in the original opt-out NO_PIE commit as this was not using the proper framework. Reported by: peter
* Revert r267233 for now. PIE support needs to be reworked.bdrewery2014-08-191-2/+0
| | | | | | | | | | | | | | | | | | | | | | | | 1. 50+% of NO_PIE use is fixed by adding -fPIC to INTERNALLIB and other build-only utility libraries. 2. Another 40% is fixed by generating _pic.a variants of various libraries. 3. Some of the NO_PIE use is a bit absurd as it is disabling PIE (and ASLR) where it never would work anyhow, such as csu or loader. This suggests there may be better ways of adding support to the tree. Many of these cases can be fixed such that -fPIE will work but there is really no reason to have it in those cases. 4. Some of the uses are working around hacks done to some Makefiles that are really building libraries but have been using bsd.prog.mk because the code is cleaner. Had they been using bsd.lib.mk then NO_PIE would not have been needed. We likely do want to enable PIE by default (opt-out) for non-tree consumers (such as ports). For in-tree though we probably want to only enable PIE (opt-in) for common attack targets such as remote service daemons and setuid utilities. This is also a great performance compromise since ASLR is expected to reduce performance. As such it does not make sense to enable it in all utilities such as ls(1) that have little benefit to having it enabled. Reported by: kib
* Reviewed by: impsjg2014-07-261-3/+3
| | | | | LDFLAGS is supposed to be given to CC not LD. Define _LDFLAGS as a filtered version of LDFLAGS safe to give to LD
* In preparation for ASLR [1] support add WITH_PIE to support building with -fPIE.bdrewery2014-06-081-0/+2
| | | | | | | | | | | | | | | | This is currently an opt-in build flag. Once ASLR support is ready and stable it should changed to opt-out and be enabled by default along with ASLR. Each application Makefile uses opt-out to ensure that ASLR will be enabled by default in new directories when the system is compiled with PIE/ASLR. [2] Mark known build failures as NO_PIE for now. The only known runtime failure was rtld. [1] http://www.bsdcan.org/2014/schedule/events/452.en.html Submitted by: Shawn Webb <lattera@gmail.com> Discussed between: des@ and Shawn Webb [2]
* Only assign the environ in the startup code when environ is NULL.kib2013-01-071-4/+1
| | | | | | | | | | | | | | Preloaded library could have changed the environment, and unconditional assingment to the environ undoes the customization. The binaries needs to be recompiled to get the fix. Move the common code to set up environ and __progname into the helper. Note that ia64 possibly not fixed, due to it still using old csu. Reported and tested by: John Hein <jhein@symmetricom.com> Reviewed by: kan, scf Approved by: secteam (simon) MFC after: 2 weeks
* After r217375, some startup objects under lib/csu are built in a specialdim2012-04-201-3/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | way: first they are compiled to assembly, then some sed'ing is done on the assembly, and lastly the assembly is compiled to an object file. This last step is done using ${CC}, and not ${AS}, because when the compiler is clang, it outputs directives that are too advanced for our old gas. So we use clang's integrated assembler instead. (When the compiler is gcc, it just calls gas, and nothing is different, except one extra fork.) However, in the .s to .o rules in lib/csu/$ARCH/Makefile, I still passed CFLAGS to the compiler, instead of ACFLAGS, which are specifically for compiling .s files. In case you are using '-g' for debug info anywhere in your CFLAGS, it causes the .s files to already contain debug information in the assembly itself. In the next step, the .s files are also compiled using '-g', and if the compiler is clang, it complains: "error: input can't have .file dwarf directives when -g is used to generate dwarf debug info for assembly code". Fix this by using ${ACFLAGS} for compiling the .s files instead. Reported by: jasone MFC after: 1 week
* Stop calling _init/_fini methods from crt1 for dynamic binaries. Dokib2012-03-112-24/+9
| | | | | | | | | | | | | call preinit, init and fini arrays methods from crt1 for static binaries. Mark new crt1 with FreeBSD-specific ELF note. Move some common crt1 code into new MI file ignore_init.c, to reduce duplication. Also, conservatively adjust nearby sources for style. Reviewed by: kan Tested by: andrew (arm), flo (sparc64) MFC after: 3 weeks
* The (%esp & 0xf) == 0 should be true before the call instruction iskib2011-01-131-0/+1
| | | | | | | | executed, for the properly aligned stack. Reported and tested by: rstone Pointy hat to: kib MFC after: 3 days
* Apply a workaround for a binutils issue with the .note.ABI-tag sectiondim2011-01-131-4/+23
| | | | | | | | | | | | | | | | | | | | | | | | generated from lib/csu/common/crtbrand.c (which ultimately ends up in executables and shared libraries, via crt1.o, gcrt1.o or Scrt1.o). For all arches except sparc, gcc emits the section directive for the abitag struct in crtbrand.c with a PROGBITS type. However, newer versions of binutils (after 2.16.90) require the section to be of NOTE type, to guarantee that the .note.ABI-tag section correctly ends up in the first page of the final executable. Unfortunately, there is no clean way to tell gcc to use another section type, so crtbrand.c (or the C files that include it) must be compiled in multiple steps: - Compile the .c file to a .s file. - Edit the .s file to change the 'progbits' type to 'note', for the section directive that defines the .note.ABI-tag section. - Compile the .s file to an object file. These steps are done in the invididual Makefiles for each applicable arch. Reviewed by: kib
* Add section .note.GNU-stack for assembly files used by 386 and amd64.kib2011-01-073-0/+6
|
* Let all .c and .S files under lib/csu consistently use the __FBSDID()dim2010-12-094-8/+11
| | | | | macro for identification, instead of several different hand-rolled variants (plain .ident, .ascii, etc).
* Add unwind annotations to the asm part of crt1 on i386. Terminate thekib2010-06-181-1/+8
| | | | | | | process with SIGTRAP if _start1() unexpectedly returns. Reviewed by: kan MFC after: 2 weeks
* Do not create *.gmon files for PIE executables on i386.jilles2010-03-201-1/+1
| | | | | | | | | | | | Scrt1_c.o was accidentally compiled with -DGCRT (profiling), like gcrt1_c.o. This problem is i386-specific, the other architectures are OK. If you have problems with PIE executables such as samba and cups leaving behind gmon files, rebuild them after installing this change. PR: ports/143924 Reviewed by: kib MFC after: 3 days
* Build lib/ with WARNS=6 by default.ed2010-01-021-1/+0
| | | | | | | | | Similar to libexec/, do the same with lib/. Make WARNS=6 the norm and lower it when needed. I'm setting WARNS?=0 for secure/. It seems secure/ includes the Makefile.inc provided by lib/. I'm not going to touch that directory. Most of the code there is contributed anyway.
* Properly support -fPIE by linking PIE binaries with specially-builtkib2009-12-023-29/+69
| | | | | | | | | | | | | | Scrt1.o instead of crt1.o, since the later is built as non-PIC. Separate i386-elf crt1.c into the pure assembler part and C code, supplying all data extracted by assembler stub as explicit parameters [1]. Hide and localize _start1 symbol used as an interface between asm and C code. In collaboration with: kan Inspired by: PR i386/127387 [1] Prodded and tested by: rdivacky [1] MFC after: 3 weeks
* Fixed profiling of main() for amd64 and i386. This started rottingbde2005-10-071-6/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | in 1993 in rev.1.5 of the i386 a.out version (csu/i386/crt0.c). Profiling uses a magic label "eprol" to delimit the start of the part of the text section covered by profiling. This label must be placed before the call to main() to get main() properly profiled. It was placed there in rev.1.1 of crt0.c. Rev.1.5 imported the initial implementation of shared libraries in FreeBSD and misplaced the label. Fortunately, the misplaced label was misspelled and the old label wasn't removed, so the new label had no effect. Unfortunately, when profiling was implemented for the ELF in 1998 in rev.1.2 of csu/i386-elf/crt1.c, only the incorrectly placed label was copied (after fixing its name). The bug was then copied to all other arches. The label seems to be still misplaced in NetBSD for most arches. It is in common.c for most arches so it is even further from being inside the function that calls main(). I think "eprol" is short for "end of prologue", but it must be placed before the end of the prologue so that it covers main(). crt0.c has it before the calls atexit(_mcleanup) and monstartup(...), but it cannot affect these calls so I moved it after the call to monstartup(). It now also covers the call to _init() but not the newer call to _init_tls(). Profiling of _init() seems to be harmless, and the call to _init_tls() seems to be misplaced. Reviewed by: jdp (long ago, for a slightly different i386 version)
* Align the stack to a 16 byte boundary so that we can safely call functionsdfr2005-05-191-0/+3
| | | | | | | | | that use SSE. The compiler does attempt to do this in main() but not very successfully - it still manages to use unaligned offsets from %ebp in some cases. Also we need to have an aligned stack in case something uses SSE via _init(). MFC After: 1 week
* Keep the stack aligned to a 16 byte boundary when calling init functionsdfr2005-05-192-0/+4
| | | | | | | so that we don't cause a bus error if they start storing SSE math stuff on the stack. MFC After: 1 week
* Add support for TLS in statically linked programs.dfr2004-08-151-0/+2
|
* The <bsd.files.mk> API seems the best to use here.ru2004-01-201-11/+7
|
* Removed garbage:bde2003-06-041-3/+1
| | | | | | | - -elf in CFLAGS had no effect except to reduce portability. - -elf in LDFLAGS had even less effect, since LDFLAGS is not used. - -Wall in CFLAGS had no effect except to reduce portability and break overriding of WARNS, since the setting of WARNS implies -Wall.
* This is now Gcc 3.3 WARNS 6 clean.obrien2003-05-041-0/+1
|
* make these more useful for lint(1). Minor diff-reductions while I'mmarkm2003-01-261-0/+1
| | | | about it.
* Backed out previous commit (alignment suitable for RELENG_4) as plannedbde2002-12-011-33/+0
| | | | | | | | since it has been MFC'ed. See the log message for the previous commit for more details. The alignment bug in gcc-3 has not been fixed, but it is not very serious and the previous commit just moved it (as intended). Approved by: re (murray)
* Align the stack suitably for the version of gcc in FreeBSD-4 (providedbde2002-09-291-0/+33
| | | | | | | | | | | | | | | | | | | -fomit-frame-pointer is not used). This is mostly moot for -current because gcc-3 does the alignment (slightly incorrectly) in main(). This patch is intended for easy MFC'ing and should be backed out in -current soon since it causes compiler warnings and better fixes are possible in -current. The best fix is to do nothing here and wait for gcc to do stack alignment right. gcc-3 aligns the stack in main(), but does it too late for main()'s local variables and too late for anything called before main(). A misaligned stack is now more than an efficiency problem, since some SSE instructions in some or all (hardware) implementations trap on misaligned operands even if alignment checking is not enabled. PR: 41528: Submitted by: NIIMI Satoshi <sa2c@sa2c.net> (original version) MFC after: 3 days
* Drop support for COPY, -c has been the default mode of install(1)ru2002-07-291-1/+1
| | | | | | for a long time now. Approved by: bde
* The main reason for this is to reduce diffs between all the crt1.c's.markm2002-07-161-18/+25
| | | | | | | | | | | | | | | | | | | Assembler macros are tidied up and made as similar as sanely possible. The macros are translated into C (__inline static) functions for lint. Declaration orders are made the same. Declarations are all ISOfied and tidied up. Comment contents have gratuitous diffs removed. The net result is a bunch of crt1.c's that are 90% the same. It may be possible to now encapsulate the differences in one MD header, and have only one MI crt1.c file (although the macros to do this may be ugly). Helpful comments by: obrien, bde Alpha tested by: des i386-elf tested by: markm
* Whitespace diffs only; this brings this file into the same whitespacemarkm2002-07-031-26/+27
| | | | | | convention as src/lib/csu/*/crt1.c. This will make the follow up diffs easier to see and extract.
* Use .rodata section for $FreeBSD$.obrien2002-05-152-4/+6
|
* Fixed CLEANFILES after bsd.lib.mk sweep.ru2002-05-131-0/+2
|
* SOBJS are not used here for a long time, and were justru2002-05-131-4/+2
| | | | pessimising the `install'.
* Major cleanup of bsd.lib.mk.ru2002-05-131-5/+0
| | | | | | | Get rid of the INTERNALSTATICLIB knob and just use plain INTERNALLIB. INTERNALLIB now means to build static library only and don't install anything. Added a NOINSTALLLIB knob for libpam/modules. To not build any library at all, just do not set LIB.
* Revert the last change. The corresponding bsd.lib.mk changes wereru2002-05-121-1/+4
| | | | already backed out.
* Use the simpler NOMAN rather than NOMAN, NOPIC, NOPROFILE, INTERNALLIB.obrien2002-05-111-4/+1
|
* Removed "-fkeep-inline-functions" from CFLAGS, since it now has no effectbde2002-04-291-1/+1
| | | | | | | | | | | | | except to generate spurious warnings about a system header <sys/param.h> having some inline functions (the bswap family). This backs out the main part of rev.1.5 (which was the only part left). The problem fixed by rev.1.5 of the Makefile went away in rev.1.5 of ../common/crtbegin.c when the references to do_ctors() and do_dtors() in the latter were moved from inline asm to C code. This leaves the problem that implementation details cause warnings. Discussed with: jdp
* Do not use __progname directly (except in [gs]etprogname(3)).markm2002-03-292-3/+5
| | | | | | Also, make an internal _getprogname() that is used only inside libc. For libc, getprogname(3) is a weak symbol in case a function of the same name is defined in userland.
* Minor style(9) nit + utilize ELF features for the FreeBSD ID.obrien2002-02-271-4/+4
|
* minor style updatingobrien2001-10-271-4/+3
|
* * Bring back the guts of crt{i,n}.S. This allows C++ exceptions to workobrien2000-10-284-11/+20
| | | | | | | | | | | | | | | | | | | when using the egcs and gcc-devel ports, along with GCC built from stock public FSF sources. With out this change, FreeBSD will be removed from the list of systems GCC 3.0 must be evaluated on before release. With the effort some of us put into getting FreeBSD on this list, we should not turn this effort into a waste, else we might not be worth fighting for in the future. (note that Alpha and IA-64 versions of crt{i,n}.S are needed) * Switch from our own crt{begin,in} to those created from GCC's crtstuff.c. This will allow us to switch to DWARF2 exceptions in the future, along with staying in sync with any future GCC requirements. * Break out our ELF branding bits into a seperate file. Currently this is now included by our crt1.c files (since this functionality was part of our native crtbegin.c). Later crtbrand.o will be merged in the creation of crti.o.
* Take crtbegin.c and crtend.c from the new machine-independentjdp2000-05-203-135/+2
| | | | "common" sister directory.
* This is step 1 in an effort to unify the start-up files for thejdp2000-05-193-39/+60
| | | | | | | | | | | | | | | | | various architectures. Now all the work is done in crtbegin.c. It doesn't contain any assembly language code, so it should work fine on all architectures. (I have tested it on the i386 and the alpha.) The old assembly language files crt[in].S are now empty shells that generate no code or data. They should not be removed any time soon, because the various versions of gcc in src and ports expect them to exist. Next I will move crtbegin.c into a new common machine-independent directory, and adjust the i386-elf Makefile to use that version. After that I will adjust the alpha Makefile to use the common version too. Requested by: obrien
* Change our ELF binary branding to something more acceptable to the Binutilsobrien2000-04-181-0/+14
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | maintainers. After we established our branding method of writing upto 8 characters of the OS name into the ELF header in the padding; the Binutils maintainers and/or SCO (as USL) decided that instead the ELF header should grow two new fields -- EI_OSABI and EI_ABIVERSION. Each of these are an 8-bit unsigned integer. SCO has assigned official values for the EI_OSABI field. In addition to this, the Binutils maintainers and NetBSD decided that a better ELF branding method was to include ABI information in a ".note" ELF section. With this set of changes, we will now create ELF binaries branded using both "official" methods. Due to the complexity of adding a section to a binary, binaries branded with ``brandelf'' will only brand using the EI_OSABI method. Also due to the complexity of pulling a section out of an ELF file vs. poking around in the ELF header, our image activator only looks at the EI_OSABI header field. Note that a new kernel can still properly load old binaries except for Linux static binaries branded in our old method. * * For a short period of time, ``ld'' will also brand ELF binaries * using our old method. This is so people can still use kernel.old * with a new world. This support will be removed before 5.0-RELEASE, * and may not last anywhere upto the actual release. My expiration * time for this is about 6mo. *
* $Id$ -> $FreeBSD$peter1999-08-286-6/+6
|
* Add "-fkeep-inline-functions" to CFLAGS so that higher optimizationjdp1999-03-151-3/+2
| | | | | | | | levels (-O3 and above) won't remove essential code. Many thanks to Dmitrij Tejblum <dima@tejblum.dnttm.rssi.ru> for pointing out that it was the optimizer's removal of this code that caused make world with -O3 to break. With this change, make buildworld now completes.
* Reverse the order of processing object files within an executable orjdp1999-03-131-3/+3
| | | | | | | | | | | | | shared library when invoking global constructors and destructors. For constructors, the object files used to be processed from first to last; now they're done from last to first. (Destructors are done in the opposite order, as required by the C++ standard.) This makes us consistent with standard gcc and egcs compilers. It also eliminates ordering differences between dynamic and static executables. Bump the value of __FreeBSD_version to 400002 to reflect this change.
* Move the code for the ".init" and ".fini" sections outside of ajdp1999-03-123-15/+15
| | | | | | | | | C function so the compiler won't try to emit line numbers for it with "-g", breaking the build. This has the nice side-effect of making crtbegin.o and crtbeginS.o a little bit smaller. Remove "-Wno-unused" from the Makefile. Replace it with "__unused" on particular function and variable declarations.
* Switch to using ".So" as the extension for PIC object files ratherjdp1999-01-091-3/+3
| | | | | | | | than ".so". The old extension conflicted with well-established naming conventions for dynamically loadable modules. The "clean" targets continue to remove ".so" files too, to deal with old systems.
* Strip the leading path from __progname as is done in the a.out case. Alsosteve1998-12-241-3/+9
| | | | | | | bring in stddef.h so we can use NULL instead of 0 for pointer comparisons. Hinted at by: Bruce Evans Reviewed by: John Polstra
OpenPOWER on IntegriCloud