4 Commits

Author	SHA1	Message	Date
Kristof Beyls	fb38729d78	Enable -fuse-init-array for all AArch64 ELF targets by default, not just linux. ... llvm-svn: 198940	2014-01-10 13:44:34 +00:00
Chandler Carruth	05fb585a36	Fix the '-fuse-init-array' option to actually be an option. ... Previously, this flag to CC1 was never exposed at the clang driver layer, and if you happened to enable it (by being on Android or GCC 4.7 platform), you couldn't *disable* it, because there was no 'no' variant. The whole thing was confusingly implemented. Now, the target-specific flag processing gets the driver arg list, and we use standard hasFlag with a default based on the GCC version and/or Android platform. The user can still pass the 'no-' variant to forcibly disable the flag, or pass the positive variant to clang itself to enable the flag. The test has also been substantially cleaned up and extended to cover these use cases. llvm-svn: 168473	2012-11-21 23:40:23 +00:00
Logan Chien	1d8cc65a9b	Enable -fuse-init-array for Android X86/MIPS. ... The dynamic linker of Android does not support .ctors/.dtors. We should emit .init_array and .fini_array regardless the gcc version. NOTE: This patch does not affect the ARM backend, because it is required to generate .init_array and .fini_array for program targeting ARM AAPCS and AEABI. llvm-svn: 168309	2012-11-19 11:45:31 +00:00
Rafael Espindola	66aa045fd9	Add a -fuse-init-array option to cc1 and map to the UseInitArray target ... option. On the driver, check if we are using libraries from gcc 4.7 or newer and if so pass -fuse-init-array to the frontend. The crtbegin*.o files in gcc 4.7 no longer call the constructors listed in .ctors, so we have to use .init_array. llvm-svn: 158694	2012-06-19 01:26:10 +00:00