mirror of
https://github.com/c64scene-ar/llvm-6502.git
synced 2025-09-23 01:25:32 +00:00
autoconf
m4
build_exeext.m4
c_printf_a.m4
check_gnu_make.m4
config_makefile.m4
config_project.m4
cxx_flag_check.m4
find_std_program.m4
func_isinf.m4
func_isnan.m4
func_mmap_file.m4
header_mmap_anonymous.m4
huge_val.m4
libtool.m4
link_options.m4
linux_mixed_64_32.m4
ltdl.m4
need_dev_zero_for_mmap.m4
path_tclsh.m4
rand48.m4
sanity_check.m4
single_cxx_check.m4
visibility_inlines_hidden.m4
AutoRegen.sh
ExportMap.map
LICENSE.TXT
README.TXT
config.guess
config.sub
configure.ac
depcomp
install-sh
ltmain.sh
missing
mkinstalldirs
bindings
cmake
docs
examples
include
lib
projects
runtime
test
tools
unittests
utils
.arcconfig
.clang-format
.gitignore
CMakeLists.txt
CODE_OWNERS.TXT
CREDITS.TXT
LICENSE.TXT
LLVMBuild.txt
Makefile
Makefile.common
Makefile.config.in
Makefile.rules
README.txt
configure
llvm.spec.in
244acf3a4b
Recent versions of the OS X linker support this but follow the existing OS X linker convention of using an underscore in the option name, i.e., -export_dynamic. Rather than changing our configure scripts to check for that alternate spelling, it is simpler to just use the compiler's -rdynamic option and let it deal with translating that to the appropriate linker option. One potential disadvantage of this approach is that the compiler will typically ignore -rdynamic on platforms where it is not supported, so the HAVE_LINK_EXPORT_DYNAMIC in config.h will not necessarily show whether that option has any effect or not. I don't see any in-tree uses of that macro, so I'm assuming it is OK. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@187686 91177308-0d34-0410-b5e6-96231b3b80d8