maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity
llvm-project/lldb/packages/Python/lldbsuite/test/make/Makefile.rules

720 lines
24 KiB
Makefile
Raw Normal View History

Makefile refactoring for the test suite. Added a make directory under test, which hosts the Makefile.rules and modified most of the Makefiles under each test case directories to utilize Mekefile.rules. Added a description of 'make' directory into README-TestSuite file. llvm-svn: 111868
2010-08-24 07:56:08 +08:00
#----------------------------------------------------------------------
# Clients fill in the source files to build
#----------------------------------------------------------------------
# C_SOURCES := main.c
# CXX_SOURCES :=
# OBJC_SOURCES :=
# OBJCXX_SOURCES :=
# DYLIB_C_SOURCES :=
Compile the LLDB tests out-of-tree. This patch is the result of a discussion on lldb-dev, see http://lists.llvm.org/pipermail/lldb-dev/2018-January/013111.html for background. For each test (should be eventually: each test configuration) a separate build directory is created and we execute make VPATH=$srcdir/path/to/test -C $builddir/path/to/test -f $srcdir/path/to/test/Makefile -I $srcdir/path/to/test In order to make this work all LLDB tests need to be updated to find the executable in the test build directory, since CWD still points at the test's source directory, which is a requirement for unittest2. Although we have done extensive testing, I'm expecting that this first attempt will break a few bots. Please DO NOT HESITATE TO REVERT this patch in order to get the bots green again. We will likely have to iterate on this some more. Differential Revision: https://reviews.llvm.org/D42281 llvm-svn: 323803
2018-01-31 02:29:16 +08:00
# DYLIB_OBJC_SOURCES :=
Add usage examples of recently added functionality. llvm-svn: 147907
2012-01-11 09:42:58 +08:00
# DYLIB_CXX_SOURCES :=
#
# Specifying DYLIB_ONLY has the effect of building dylib only, skipping
# the building of the a.out executable program. For example,
# DYLIB_ONLY := YES
#
Add usage example from test/functionalities/archives/Makefile. llvm-svn: 148269
2012-01-17 08:58:08 +08:00
# Also might be of interest:
Add more usage examples. llvm-svn: 147909
2012-01-11 09:59:55 +08:00
# FRAMEWORK_INCLUDES (Darwin only) :=
Allow specifying tool path/prefix for tests with CROSS_COMPILE. CROSS_COMPILE environment variable is a common convention to specify the path and/or prefix to cross compilation tools (e.g. ar, objcopy). Test Plan: dotest.py $DOTEST_OPTS -t -p 'TestBSDArchives.py|TestBreakpointCommandsFromPython.py|TestFormats.py|TestObjCDynamicValue.py' All of these tests now compile successfully and pass running macosx -> linux using a cross compilation toolchain prefixed by CROSS_COMPILE without requiring changing your PATH. They still pass when run locally on macosx. Differential Revision: http://reviews.llvm.org/D9072 llvm-svn: 235320
2015-04-21 02:07:55 +08:00
# CFLAGS_EXTRAS :=
Add more usage examples. llvm-svn: 147909
2012-01-11 09:59:55 +08:00
# LD_EXTRAS :=
Add split symbol support to test makefile & add linux split symbol test case. llvm-svn: 185455
2013-07-03 02:13:13 +08:00
# SPLIT_DEBUG_SYMBOLS := YES
Allow specifying tool path/prefix for tests with CROSS_COMPILE. CROSS_COMPILE environment variable is a common convention to specify the path and/or prefix to cross compilation tools (e.g. ar, objcopy). Test Plan: dotest.py $DOTEST_OPTS -t -p 'TestBSDArchives.py|TestBreakpointCommandsFromPython.py|TestFormats.py|TestObjCDynamicValue.py' All of these tests now compile successfully and pass running macosx -> linux using a cross compilation toolchain prefixed by CROSS_COMPILE without requiring changing your PATH. They still pass when run locally on macosx. Differential Revision: http://reviews.llvm.org/D9072 llvm-svn: 235320
2015-04-21 02:07:55 +08:00
# CROSS_COMPILE :=
Add usage example from test/functionalities/archives/Makefile. llvm-svn: 148269
2012-01-17 08:58:08 +08:00
#
# And test/functionalities/archives/Makefile:
# MAKE_DSYM := NO
# ARCHIVE_NAME := libfoo.a
# ARCHIVE_C_SOURCES := a.c b.c
Makefile refactoring for the test suite. Added a make directory under test, which hosts the Makefile.rules and modified most of the Makefiles under each test case directories to utilize Mekefile.rules. Added a description of 'make' directory into README-TestSuite file. llvm-svn: 111868
2010-08-24 07:56:08 +08:00
# Uncomment line below for debugging shell commands
# SHELL = /bin/sh -x
Compile the LLDB tests out-of-tree. This patch is the result of a discussion on lldb-dev, see http://lists.llvm.org/pipermail/lldb-dev/2018-January/013111.html for background. For each test (should be eventually: each test configuration) a separate build directory is created and we execute make VPATH=$srcdir/path/to/test -C $builddir/path/to/test -f $srcdir/path/to/test/Makefile -I $srcdir/path/to/test In order to make this work all LLDB tests need to be updated to find the executable in the test build directory, since CWD still points at the test's source directory, which is a requirement for unittest2. Although we have done extensive testing, I'm expecting that this first attempt will break a few bots. Please DO NOT HESITATE TO REVERT this patch in order to get the bots green again. We will likely have to iterate on this some more. Differential Revision: https://reviews.llvm.org/D42281 llvm-svn: 323803
2018-01-31 02:29:16 +08:00
SRCDIR := $(shell dirname $(firstword $(MAKEFILE_LIST)))/
Makefile.rules: Use an absolute path to the module cache directory. This change is NFC, but it makes it more obvious in log files what happened. llvm-svn: 340286
2018-08-21 23:46:15 +08:00
BUILDDIR := $(shell pwd)
Compile the LLDB tests out-of-tree. This patch is the result of a discussion on lldb-dev, see http://lists.llvm.org/pipermail/lldb-dev/2018-January/013111.html for background. For each test (should be eventually: each test configuration) a separate build directory is created and we execute make VPATH=$srcdir/path/to/test -C $builddir/path/to/test -f $srcdir/path/to/test/Makefile -I $srcdir/path/to/test In order to make this work all LLDB tests need to be updated to find the executable in the test build directory, since CWD still points at the test's source directory, which is a requirement for unittest2. Although we have done extensive testing, I'm expecting that this first attempt will break a few bots. Please DO NOT HESITATE TO REVERT this patch in order to get the bots green again. We will likely have to iterate on this some more. Differential Revision: https://reviews.llvm.org/D42281 llvm-svn: 323803
2018-01-31 02:29:16 +08:00
THIS_FILE_DIR := $(shell dirname $(lastword $(MAKEFILE_LIST)))/
Updated a relative path in Makefile.rules to reflect the new testsuite location. llvm-svn: 252657
2015-11-11 05:56:04 +08:00
LLDB_BASE_DIR := $(THIS_FILE_DIR)../../../../../
Get test executables compiling on Windows. Many of the test executables use pthreads directly. This isn't portable on Windows, so this patch converts these test to use C++11 threads and mutexes. Since Windows' implementation of std::thread classes throw and catch from header files, this patch also disables exceptions when compiling with clang on Windows. Reviewed by: Todd Fiala, Ed Maste Differential Revision: http://reviews.llvm.org/D4816 llvm-svn: 215562
2014-08-14 01:44:53 +08:00
Android.rules: add support for clang compiler Summary: building executables with the NDK clang requires -target and -gcc-toolchain arguments. Reviewers: eugene, danalbert Subscribers: srhines, lldb-commits Differential Revision: https://reviews.llvm.org/D30574 llvm-svn: 297145
2017-03-07 22:57:37 +08:00
#----------------------------------------------------------------------
# If OS is not defined, use 'uname -s' to determine the OS name.
#
[lit, lldbsuite] Update the lldbsuite to correctly run tests on windows and windows server Summary: The new script to run the lldbtests as part of lit invokes each test by calling dotest.py, however, we cannot rely on the system to always correctly interpret the script as python causing the tests to be unresolved on windows (at least). To fix this, we need to make sure that the first parameter in the command line is the python executable itself. In Makefile.rules, there are a number of windows specific definitions that rely on the HOST_OS being set as Windows_NT but the logic detecting the OS currently does not detect server versions of windows correctly. This change updates the logic to detect windows server as well. Reviewers: asmith, labath, JDevlieghere, zturner Reviewed By: JDevlieghere, zturner Subscribers: zturner, llvm-commits Differential Revision: https://reviews.llvm.org/D46020 llvm-svn: 330740
2018-04-25 01:08:05 +08:00
# uname on Windows gives "windows32" or "server version windows32", but most
# environments standardize on "Windows_NT", so we'll make it consistent here.
# When running tests from Visual Studio, the environment variable isn't
# inherited all the way down to the process spawned for make.
Android.rules: add support for clang compiler Summary: building executables with the NDK clang requires -target and -gcc-toolchain arguments. Reviewers: eugene, danalbert Subscribers: srhines, lldb-commits Differential Revision: https://reviews.llvm.org/D30574 llvm-svn: 297145
2017-03-07 22:57:37 +08:00
#----------------------------------------------------------------------
HOST_OS = $(shell uname -s)
[lit, lldbsuite] Update the lldbsuite to correctly run tests on windows and windows server Summary: The new script to run the lldbtests as part of lit invokes each test by calling dotest.py, however, we cannot rely on the system to always correctly interpret the script as python causing the tests to be unresolved on windows (at least). To fix this, we need to make sure that the first parameter in the command line is the python executable itself. In Makefile.rules, there are a number of windows specific definitions that rely on the HOST_OS being set as Windows_NT but the logic detecting the OS currently does not detect server versions of windows correctly. This change updates the logic to detect windows server as well. Reviewers: asmith, labath, JDevlieghere, zturner Reviewed By: JDevlieghere, zturner Subscribers: zturner, llvm-commits Differential Revision: https://reviews.llvm.org/D46020 llvm-svn: 330740
2018-04-25 01:08:05 +08:00
ifneq (,$(findstring windows32,$(HOST_OS)))
Android.rules: add support for clang compiler Summary: building executables with the NDK clang requires -target and -gcc-toolchain arguments. Reviewers: eugene, danalbert Subscribers: srhines, lldb-commits Differential Revision: https://reviews.llvm.org/D30574 llvm-svn: 297145
2017-03-07 22:57:37 +08:00
HOST_OS = Windows_NT
endif
ifeq "$(OS)" ""
OS = $(HOST_OS)
endif
Force SHELL to be cmd.exe on Windows for the test suite Summary: Windows make will search for other shells and choose those over cmd if available (e.g. C:\cygdrive\bin\sh.exe). This shell has numerous issues with path handling (/ vs \\ vs \ and C:). So default to using cmd.exe which is known to work. Reviewers: zturner, sas, xiaobai Reviewed By: zturner Differential Revision: https://reviews.llvm.org/D54510 llvm-svn: 346993
2018-11-16 04:56:44 +08:00
#----------------------------------------------------------------------
# If OS is Windows, force SHELL to be cmd
#
# Some versions of make on Windows will search for other shells such as
# C:\cygwin\bin\sh.exe. This shell fails for numerous different reasons
# so default to using cmd.exe.
#----------------------------------------------------------------------
ifeq "$(OS)" "Windows_NT"
SHELL = $(WINDIR)\system32\cmd.exe
endif
[lldbsuite] Invoke sed on Windows to determine the cache dir for clang Summary: In order to invoke sed on Windows, we need to quote the command correctly. Since we already have commands which do that, move the definitions at the beginning of the file and then re-use them for each command. Reviewers: aprantl, zturner Subscribers: teemperor, lldb-commits Differential Revision: https://reviews.llvm.org/D54709 llvm-svn: 347243
2018-11-20 02:41:33 +08:00
#----------------------------------------------------------------------
# If the OS is Windows use double-quotes in commands
#
# For other operating systems, single-quotes work fine, but on Windows
# we strictly required double-quotes
#----------------------------------------------------------------------
ifeq "$(HOST_OS)" "Windows_NT"
JOIN_CMD = &
QUOTE = "
FIXUP_SYNTAX_HIGHLIGHTING_IN_MY_EDITOR = "
else
JOIN_CMD = ;
QUOTE = '
FIXUP_SYNTAX_HIGHLIGHTING_IN_MY_EDITOR = '
endif
Added the ability for the "make" command to take a triple: % cd lldb/test/lang/c/array_types % make TRIPLE=x86_64-apple-ios % make clean % make TRIPLE=x86_64-apple-ios8.1 % make clean % make TRIPLE=armv7-apple-ios % make clean % make TRIPLE=armv7-apple-ios8.1 % make clean The TRIPLE variable will automatically set the following variables: SDKROOT if it isn't specified manually ARCH will be set to the architecture from the triple CFLAGS will include the extras needed for the triple which are set in TRIPLE_CFLAGS TRIPLE_VENDOR set to the triple vendor ("apple" in the above cases) TRIPLE_OS set to the triple OS ("ios" in the above cases) TRIPLE_VERSION set to the version that was specified, or automatically set to the SDK version if it is missing This allows you to change directory into any test case on MacOSX and quickly build for desktop: % make iOS simulator: % make TRIPLE=x86_64-apple-ios or iOS device: % make TRIPLE=armv7-apple-ios llvm-svn: 238869
2015-06-03 05:38:10 +08:00
#----------------------------------------------------------------------
# If TRIPLE is not defined try to set the ARCH, CC, CFLAGS, and more
# from the triple alone
#----------------------------------------------------------------------
testsuite/android: build test executables with the android ndk directly Summary: This teaches the test makefiles about the Android NDK, so we are able to run the tests without first going through the make_standalone_toolchain script. The motivation for this is the ability to run both libc++ and libstdc++ tests together, which previously was not possible because make_standalone_toolchain bakes in the STL to use during toolchain creation time. The support for this is not present yet -- this change only make sure we don't regress for existing funcionality (gcc w/ libstdc++). Clang and libc++ support will be added later. I've checked that the mips android targets compile after this change, but I have no way of checking whether this breaks anything. If you are reading this and it broke you, let me know. Reviewers: tberghammer, danalbert Subscribers: srhines, lldb-commits Differential Revision: https://reviews.llvm.org/D30410 llvm-svn: 296869
2017-03-03 21:49:34 +08:00
ARCH_CFLAGS :=
Added the ability for the "make" command to take a triple: % cd lldb/test/lang/c/array_types % make TRIPLE=x86_64-apple-ios % make clean % make TRIPLE=x86_64-apple-ios8.1 % make clean % make TRIPLE=armv7-apple-ios % make clean % make TRIPLE=armv7-apple-ios8.1 % make clean The TRIPLE variable will automatically set the following variables: SDKROOT if it isn't specified manually ARCH will be set to the architecture from the triple CFLAGS will include the extras needed for the triple which are set in TRIPLE_CFLAGS TRIPLE_VENDOR set to the triple vendor ("apple" in the above cases) TRIPLE_OS set to the triple OS ("ios" in the above cases) TRIPLE_VERSION set to the version that was specified, or automatically set to the SDK version if it is missing This allows you to change directory into any test case on MacOSX and quickly build for desktop: % make iOS simulator: % make TRIPLE=x86_64-apple-ios or iOS device: % make TRIPLE=armv7-apple-ios llvm-svn: 238869
2015-06-03 05:38:10 +08:00
ifneq "$(TRIPLE)" ""
triple_space = $(subst -, ,$(TRIPLE))
ARCH =$(word 1, $(triple_space))
TRIPLE_VENDOR =$(word 2, $(triple_space))
Teach LLDB how to directly launch processes on the iOS simulator This allows for command-line debugging of iOS simulator binaries (as long as UI is not required, or a full UI simulator has previously been otherwise launched), as well as execution of the LLDB test suite on the iOS simulator This is known to compile on OSX 10.11 GM - feedback from people on other platforms and/or older versions of OSX as to the buildability of this code is greatly appreciated llvm-svn: 252112
2015-11-05 08:46:25 +08:00
triple_os_and_version =$(shell echo $(word 3, $(triple_space)) | sed 's/\([a-z]*\)\(.*\)/\1 \2/')
Added the ability for the "make" command to take a triple: % cd lldb/test/lang/c/array_types % make TRIPLE=x86_64-apple-ios % make clean % make TRIPLE=x86_64-apple-ios8.1 % make clean % make TRIPLE=armv7-apple-ios % make clean % make TRIPLE=armv7-apple-ios8.1 % make clean The TRIPLE variable will automatically set the following variables: SDKROOT if it isn't specified manually ARCH will be set to the architecture from the triple CFLAGS will include the extras needed for the triple which are set in TRIPLE_CFLAGS TRIPLE_VENDOR set to the triple vendor ("apple" in the above cases) TRIPLE_OS set to the triple OS ("ios" in the above cases) TRIPLE_VERSION set to the version that was specified, or automatically set to the SDK version if it is missing This allows you to change directory into any test case on MacOSX and quickly build for desktop: % make iOS simulator: % make TRIPLE=x86_64-apple-ios or iOS device: % make TRIPLE=armv7-apple-ios llvm-svn: 238869
2015-06-03 05:38:10 +08:00
TRIPLE_OS =$(word 1, $(triple_os_and_version))
TRIPLE_VERSION =$(word 2, $(triple_os_and_version))
ifeq "$(TRIPLE_VENDOR)" "apple"
ifeq "$(TRIPLE_OS)" "ios"
[lldbsuite] Invoke sed on Windows to determine the cache dir for clang Summary: In order to invoke sed on Windows, we need to quote the command correctly. Since we already have commands which do that, move the definitions at the beginning of the file and then re-use them for each command. Reviewers: aprantl, zturner Subscribers: teemperor, lldb-commits Differential Revision: https://reviews.llvm.org/D54709 llvm-svn: 347243
2018-11-20 02:41:33 +08:00
CODESIGN := codesign
ifeq "$(SDKROOT)" ""
Added the ability for the "make" command to take a triple: % cd lldb/test/lang/c/array_types % make TRIPLE=x86_64-apple-ios % make clean % make TRIPLE=x86_64-apple-ios8.1 % make clean % make TRIPLE=armv7-apple-ios % make clean % make TRIPLE=armv7-apple-ios8.1 % make clean The TRIPLE variable will automatically set the following variables: SDKROOT if it isn't specified manually ARCH will be set to the architecture from the triple CFLAGS will include the extras needed for the triple which are set in TRIPLE_CFLAGS TRIPLE_VENDOR set to the triple vendor ("apple" in the above cases) TRIPLE_OS set to the triple OS ("ios" in the above cases) TRIPLE_VERSION set to the version that was specified, or automatically set to the SDK version if it is missing This allows you to change directory into any test case on MacOSX and quickly build for desktop: % make iOS simulator: % make TRIPLE=x86_64-apple-ios or iOS device: % make TRIPLE=armv7-apple-ios llvm-svn: 238869
2015-06-03 05:38:10 +08:00
# Set SDKROOT if it wasn't set
ifneq (,$(findstring arm,$(ARCH)))
SDKROOT = $(shell xcrun --sdk iphoneos --show-sdk-path)
Fixed the logic to determine the TRIPLE_VERSION correctly when it isn't specified. llvm-svn: 238871
2015-06-03 05:42:31 +08:00
ifeq "$(TRIPLE_VERSION)" ""
TRIPLE_VERSION =$(shell echo $(notdir $(SDKROOT)) | sed -e 's/.*\([0-9]\.[0-9]\).*/\1/')
endif
testsuite/android: build test executables with the android ndk directly Summary: This teaches the test makefiles about the Android NDK, so we are able to run the tests without first going through the make_standalone_toolchain script. The motivation for this is the ability to run both libc++ and libstdc++ tests together, which previously was not possible because make_standalone_toolchain bakes in the STL to use during toolchain creation time. The support for this is not present yet -- this change only make sure we don't regress for existing funcionality (gcc w/ libstdc++). Clang and libc++ support will be added later. I've checked that the mips android targets compile after this change, but I have no way of checking whether this breaks anything. If you are reading this and it broke you, let me know. Reviewers: tberghammer, danalbert Subscribers: srhines, lldb-commits Differential Revision: https://reviews.llvm.org/D30410 llvm-svn: 296869
2017-03-03 21:49:34 +08:00
ARCH_CFLAGS :=-mios-version-min=$(TRIPLE_VERSION) -isysroot "$(SDKROOT)"
Added the ability for the "make" command to take a triple: % cd lldb/test/lang/c/array_types % make TRIPLE=x86_64-apple-ios % make clean % make TRIPLE=x86_64-apple-ios8.1 % make clean % make TRIPLE=armv7-apple-ios % make clean % make TRIPLE=armv7-apple-ios8.1 % make clean The TRIPLE variable will automatically set the following variables: SDKROOT if it isn't specified manually ARCH will be set to the architecture from the triple CFLAGS will include the extras needed for the triple which are set in TRIPLE_CFLAGS TRIPLE_VENDOR set to the triple vendor ("apple" in the above cases) TRIPLE_OS set to the triple OS ("ios" in the above cases) TRIPLE_VERSION set to the version that was specified, or automatically set to the SDK version if it is missing This allows you to change directory into any test case on MacOSX and quickly build for desktop: % make iOS simulator: % make TRIPLE=x86_64-apple-ios or iOS device: % make TRIPLE=armv7-apple-ios llvm-svn: 238869
2015-06-03 05:38:10 +08:00
else
SDKROOT = $(shell xcrun --sdk iphonesimulator --show-sdk-path)
Fixed the logic to determine the TRIPLE_VERSION correctly when it isn't specified. llvm-svn: 238871
2015-06-03 05:42:31 +08:00
ifeq "$(TRIPLE_VERSION)" ""
TRIPLE_VERSION =$(shell echo $(notdir $(SDKROOT)) | sed -e 's/.*\([0-9]\.[0-9]\).*/\1/')
endif
testsuite/android: build test executables with the android ndk directly Summary: This teaches the test makefiles about the Android NDK, so we are able to run the tests without first going through the make_standalone_toolchain script. The motivation for this is the ability to run both libc++ and libstdc++ tests together, which previously was not possible because make_standalone_toolchain bakes in the STL to use during toolchain creation time. The support for this is not present yet -- this change only make sure we don't regress for existing funcionality (gcc w/ libstdc++). Clang and libc++ support will be added later. I've checked that the mips android targets compile after this change, but I have no way of checking whether this breaks anything. If you are reading this and it broke you, let me know. Reviewers: tberghammer, danalbert Subscribers: srhines, lldb-commits Differential Revision: https://reviews.llvm.org/D30410 llvm-svn: 296869
2017-03-03 21:49:34 +08:00
ARCH_CFLAGS :=-mios-simulator-version-min=$(TRIPLE_VERSION) -isysroot "$(SDKROOT)"
Added the ability for the "make" command to take a triple: % cd lldb/test/lang/c/array_types % make TRIPLE=x86_64-apple-ios % make clean % make TRIPLE=x86_64-apple-ios8.1 % make clean % make TRIPLE=armv7-apple-ios % make clean % make TRIPLE=armv7-apple-ios8.1 % make clean The TRIPLE variable will automatically set the following variables: SDKROOT if it isn't specified manually ARCH will be set to the architecture from the triple CFLAGS will include the extras needed for the triple which are set in TRIPLE_CFLAGS TRIPLE_VENDOR set to the triple vendor ("apple" in the above cases) TRIPLE_OS set to the triple OS ("ios" in the above cases) TRIPLE_VERSION set to the version that was specified, or automatically set to the SDK version if it is missing This allows you to change directory into any test case on MacOSX and quickly build for desktop: % make iOS simulator: % make TRIPLE=x86_64-apple-ios or iOS device: % make TRIPLE=armv7-apple-ios llvm-svn: 238869
2015-06-03 05:38:10 +08:00
endif
endif
endif
Initial patchset to get the testsuite running against armv7 and arm64 iOS devices. Normal customer devices won't be able to run these tests, we're hoping to get a public facing bot set up at some point. Both devices pass the testsuite without any errors or failures. I have seen some instability with the armv7 test runs, I may submit additional patches to address this. arm64 looks good. I'll be watching the bots for the rest of today; if any problems are introduced by this patch I'll revert it - if anyone sees a problem with their bot that I don't see, please do the same. I know it's a rather large patch. One change I had to make specifically for iOS devices was that debugserver can't create files. There were several tests that launch the inferior process redirecting its output to a file, then they retrieve the file. They were not trying to test file redirection in these tests, so I rewrote those to write their output to a file directly. llvm-svn: 314132
2017-09-26 02:19:39 +08:00
ifeq "$(TRIPLE_OS)" "watchos"
Makefile.rules: Don't use code signing on macOS; it isn't necessary. llvm-svn: 345768
2018-11-01 03:42:02 +08:00
CODESIGN := codesign
ifeq "$(SDKROOT)" ""
Initial patchset to get the testsuite running against armv7 and arm64 iOS devices. Normal customer devices won't be able to run these tests, we're hoping to get a public facing bot set up at some point. Both devices pass the testsuite without any errors or failures. I have seen some instability with the armv7 test runs, I may submit additional patches to address this. arm64 looks good. I'll be watching the bots for the rest of today; if any problems are introduced by this patch I'll revert it - if anyone sees a problem with their bot that I don't see, please do the same. I know it's a rather large patch. One change I had to make specifically for iOS devices was that debugserver can't create files. There were several tests that launch the inferior process redirecting its output to a file, then they retrieve the file. They were not trying to test file redirection in these tests, so I rewrote those to write their output to a file directly. llvm-svn: 314132
2017-09-26 02:19:39 +08:00
# Set SDKROOT if it wasn't set
ifneq (,$(findstring arm,$(ARCH)))
SDKROOT = $(shell xcrun --sdk watchos --show-sdk-path)
ifeq "$(TRIPLE_VERSION)" ""
TRIPLE_VERSION =$(shell echo $(notdir $(SDKROOT)) | sed -e 's/.*\([0-9]\.[0-9]\).*/\1/')
endif
ARCH_CFLAGS :=-mwatchos-version-min=$(TRIPLE_VERSION) -isysroot "$(SDKROOT)"
else
SDKROOT = $(shell xcrun --sdk watchsimulator --show-sdk-path)
ifeq "$(TRIPLE_VERSION)" ""
TRIPLE_VERSION =$(shell echo $(notdir $(SDKROOT)) | sed -e 's/.*\([0-9]\.[0-9]\).*/\1/')
endif
ARCH_CFLAGS :=-mwatchos-simulator-version-min=$(TRIPLE_VERSION) -isysroot "$(SDKROOT)"
endif
endif
endif
Added the ability for the "make" command to take a triple: % cd lldb/test/lang/c/array_types % make TRIPLE=x86_64-apple-ios % make clean % make TRIPLE=x86_64-apple-ios8.1 % make clean % make TRIPLE=armv7-apple-ios % make clean % make TRIPLE=armv7-apple-ios8.1 % make clean The TRIPLE variable will automatically set the following variables: SDKROOT if it isn't specified manually ARCH will be set to the architecture from the triple CFLAGS will include the extras needed for the triple which are set in TRIPLE_CFLAGS TRIPLE_VENDOR set to the triple vendor ("apple" in the above cases) TRIPLE_OS set to the triple OS ("ios" in the above cases) TRIPLE_VERSION set to the version that was specified, or automatically set to the SDK version if it is missing This allows you to change directory into any test case on MacOSX and quickly build for desktop: % make iOS simulator: % make TRIPLE=x86_64-apple-ios or iOS device: % make TRIPLE=armv7-apple-ios llvm-svn: 238869
2015-06-03 05:38:10 +08:00
endif
endif
testsuite/android: build test executables with the android ndk directly Summary: This teaches the test makefiles about the Android NDK, so we are able to run the tests without first going through the make_standalone_toolchain script. The motivation for this is the ability to run both libc++ and libstdc++ tests together, which previously was not possible because make_standalone_toolchain bakes in the STL to use during toolchain creation time. The support for this is not present yet -- this change only make sure we don't regress for existing funcionality (gcc w/ libstdc++). Clang and libc++ support will be added later. I've checked that the mips android targets compile after this change, but I have no way of checking whether this breaks anything. If you are reading this and it broke you, let me know. Reviewers: tberghammer, danalbert Subscribers: srhines, lldb-commits Differential Revision: https://reviews.llvm.org/D30410 llvm-svn: 296869
2017-03-03 21:49:34 +08:00
ifeq "$(OS)" "Android"
include $(THIS_FILE_DIR)/Android.rules
endif
Added the ability for the "make" command to take a triple: % cd lldb/test/lang/c/array_types % make TRIPLE=x86_64-apple-ios % make clean % make TRIPLE=x86_64-apple-ios8.1 % make clean % make TRIPLE=armv7-apple-ios % make clean % make TRIPLE=armv7-apple-ios8.1 % make clean The TRIPLE variable will automatically set the following variables: SDKROOT if it isn't specified manually ARCH will be set to the architecture from the triple CFLAGS will include the extras needed for the triple which are set in TRIPLE_CFLAGS TRIPLE_VENDOR set to the triple vendor ("apple" in the above cases) TRIPLE_OS set to the triple OS ("ios" in the above cases) TRIPLE_VERSION set to the version that was specified, or automatically set to the SDK version if it is missing This allows you to change directory into any test case on MacOSX and quickly build for desktop: % make iOS simulator: % make TRIPLE=x86_64-apple-ios or iOS device: % make TRIPLE=armv7-apple-ios llvm-svn: 238869
2015-06-03 05:38:10 +08:00
Fix OS default in Makefile.rules for Windows. http://reviews.llvm.org/D9043 llvm-svn: 235056
2015-04-16 07:38:23 +08:00
#----------------------------------------------------------------------
# If ARCH is not defined, default to x86_64.
Added a simple test case to set breakpoints on objc class/instance methods. Modified Makefile.rules to allow for overwriting the ARCH make variable. llvm-svn: 114118
2010-09-17 04:54:06 +08:00
#----------------------------------------------------------------------
ifeq "$(ARCH)" ""
Link test executables with LLD on Windows. Clang generates DWARF debug info with section names longer than 8 characters. This is only supported by an extension to PE/COFF which the MSVC linker doesn't implement. So trying to link DWARF-enabled object files with MSVC will lead to corrupt debug information in the executable. llvm-svn: 223088
2014-12-02 07:13:41 +08:00
ifeq "$(OS)" "Windows_NT"
ARCH = x86
else
Added a simple test case to set breakpoints on objc class/instance methods. Modified Makefile.rules to allow for overwriting the ARCH make variable. llvm-svn: 114118
2010-09-17 04:54:06 +08:00
ARCH = x86_64
endif
Link test executables with LLD on Windows. Clang generates DWARF debug info with section names longer than 8 characters. This is only supported by an extension to PE/COFF which the MSVC linker doesn't implement. So trying to link DWARF-enabled object files with MSVC will lead to corrupt debug information in the executable. llvm-svn: 223088
2014-12-02 07:13:41 +08:00
endif
Added a simple test case to set breakpoints on objc class/instance methods. Modified Makefile.rules to allow for overwriting the ARCH make variable. llvm-svn: 114118
2010-09-17 04:54:06 +08:00
Make CC defaults to gcc. The cxx_compiler and cxx_linker functions rely on substituting "g++" for "gcc". llvm-svn: 123461
2011-01-15 04:46:49 +08:00
#----------------------------------------------------------------------
Make clang the default compiler for building the test programs. llvm-svn: 138391
2011-08-24 05:54:10 +08:00
# CC defaults to clang.
The plugin impl of getCompiler() should be in unison with the Makefile.rules change. llvm-svn: 138454
2011-08-25 02:12:53 +08:00
#
# If you change the defaults of CC, be sure to also change it in the file
# test/plugins/builder_base.py, which provides a Python way to return the
# value of the make variable CC -- getCompiler().
#
Added comments. llvm-svn: 123463
2011-01-15 04:55:13 +08:00
# See also these functions:
# o cxx_compiler
# o cxx_linker
Make CC defaults to gcc. The cxx_compiler and cxx_linker functions rely on substituting "g++" for "gcc". llvm-svn: 123461
2011-01-15 04:46:49 +08:00
#----------------------------------------------------------------------
Make clang the default compiler for building the test programs. llvm-svn: 138391
2011-08-24 05:54:10 +08:00
CC ?= clang
Make CC defaults to gcc. The cxx_compiler and cxx_linker functions rely on substituting "g++" for "gcc". llvm-svn: 123461
2011-01-15 04:46:49 +08:00
ifeq "$(CC)" "cc"
test Makefile.rules - pick a more sensible default CC on Linux Differential Revision: http://reviews.llvm.org/D9920 llvm-svn: 238282
2015-05-27 12:42:54 +08:00
ifneq "$(shell which clang)" ""
CC = clang
else ifneq "$(shell which clang-3.5)" ""
CC = clang-3.5
else ifneq "$(shell which gcc)" ""
CC = gcc
endif
Make CC defaults to gcc. The cxx_compiler and cxx_linker functions rely on substituting "g++" for "gcc". llvm-svn: 123461
2011-01-15 04:46:49 +08:00
endif
Update test scripts and Makefiles to allow testing with GCC: - introduce new variable ARCHFLAG in make/Makefile.rules to switch between "-arch" on Mac and "-m" everywhere else - update testcase makefiles to use LD_EXTRAS instead of LDFLAGS (the former interacts with Makefile.rules badly) - special treatment for gcc 4.6: replace "-std=c++11" with "-std=c++0x" as the former is not handled correctly - remove hardcoded "-arch" from test Makefile This patch should not have any effect on lldb on Mac OS X. llvm-svn: 173402
2013-01-25 08:31:48 +08:00
#----------------------------------------------------------------------
# ARCHFLAG is the flag used to tell the compiler which architecture
# to compile for. The default is the flag that clang accepts.
#----------------------------------------------------------------------
Make -arch work on MacOSX. llvm-svn: 235065
2015-04-16 09:18:05 +08:00
ARCHFLAG ?= -arch
Update test scripts and Makefiles to allow testing with GCC: - introduce new variable ARCHFLAG in make/Makefile.rules to switch between "-arch" on Mac and "-m" everywhere else - update testcase makefiles to use LD_EXTRAS instead of LDFLAGS (the former interacts with Makefile.rules badly) - special treatment for gcc 4.6: replace "-std=c++11" with "-std=c++0x" as the former is not handled correctly - remove hardcoded "-arch" from test Makefile This patch should not have any effect on lldb on Mac OS X. llvm-svn: 173402
2013-01-25 08:31:48 +08:00
Makefile refactoring for the test suite. Added a make directory under test, which hosts the Makefile.rules and modified most of the Makefiles under each test case directories to utilize Mekefile.rules. Added a description of 'make' directory into README-TestSuite file. llvm-svn: 111868
2010-08-24 07:56:08 +08:00
#----------------------------------------------------------------------
# Change any build/tool options needed
#----------------------------------------------------------------------
Add Linux rules to test makefile llvm-svn: 133456
2011-06-21 03:06:04 +08:00
ifeq "$(OS)" "Darwin"
[dotest] Use in-tree dsymutil on Darwin Summary: With the upstream implementation of dsymutil containing almost all functionality from the one shipped with Xcode, we want to use the in-tree version for running the test suite. This will also allow us to re-enable TestUnicodeSymbols which was failing because of the discrepancy in how Unicode symbols were hashed in lldb and older versions of dsymutil. Reviewers: aprantl, davide, jingham, labath Subscribers: mgorny, llvm-commits, lldb-commits Differential Revision: https://reviews.llvm.org/D45518 llvm-svn: 329889
2018-04-12 17:25:32 +08:00
DS := $(DSYMUTIL)
Add Linux rules to test makefile llvm-svn: 133456
2011-06-21 03:06:04 +08:00
DSFLAGS =
DSYM = $(EXE).dSYM
Allow specifying tool path/prefix for tests with CROSS_COMPILE. CROSS_COMPILE environment variable is a common convention to specify the path and/or prefix to cross compilation tools (e.g. ar, objcopy). Test Plan: dotest.py $DOTEST_OPTS -t -p 'TestBSDArchives.py|TestBreakpointCommandsFromPython.py|TestFormats.py|TestObjCDynamicValue.py' All of these tests now compile successfully and pass running macosx -> linux using a cross compilation toolchain prefixed by CROSS_COMPILE without requiring changing your PATH. They still pass when run locally on macosx. Differential Revision: http://reviews.llvm.org/D9072 llvm-svn: 235320
2015-04-21 02:07:55 +08:00
AR := $(CROSS_COMPILE)libtool
rdar://problem/10680957 Need a test case that tests DWARF with .o in .a files test/functionalities/archives: Produces libfoo.a from a.o and b.o. Test breaking inside functions defined inside the libfoo.a BSD Archive. test/make/makefile.rules: Some additional rules to sepcify archive building. For example: ARCHIVE_NAME := libfoo.a ARCHIVE_C_SOURCES := a.c b.c llvm-svn: 148066
2012-01-13 07:09:42 +08:00
ARFLAGS := -static -o
Update test scripts and Makefiles to allow testing with GCC: - introduce new variable ARCHFLAG in make/Makefile.rules to switch between "-arch" on Mac and "-m" everywhere else - update testcase makefiles to use LD_EXTRAS instead of LDFLAGS (the former interacts with Makefile.rules badly) - special treatment for gcc 4.6: replace "-std=c++11" with "-std=c++0x" as the former is not handled correctly - remove hardcoded "-arch" from test Makefile This patch should not have any effect on lldb on Mac OS X. llvm-svn: 173402
2013-01-25 08:31:48 +08:00
else
Allow specifying tool path/prefix for tests with CROSS_COMPILE. CROSS_COMPILE environment variable is a common convention to specify the path and/or prefix to cross compilation tools (e.g. ar, objcopy). Test Plan: dotest.py $DOTEST_OPTS -t -p 'TestBSDArchives.py|TestBreakpointCommandsFromPython.py|TestFormats.py|TestObjCDynamicValue.py' All of these tests now compile successfully and pass running macosx -> linux using a cross compilation toolchain prefixed by CROSS_COMPILE without requiring changing your PATH. They still pass when run locally on macosx. Differential Revision: http://reviews.llvm.org/D9072 llvm-svn: 235320
2015-04-21 02:07:55 +08:00
AR := $(CROSS_COMPILE)ar
Update test scripts and Makefiles to allow testing with GCC: - introduce new variable ARCHFLAG in make/Makefile.rules to switch between "-arch" on Mac and "-m" everywhere else - update testcase makefiles to use LD_EXTRAS instead of LDFLAGS (the former interacts with Makefile.rules badly) - special treatment for gcc 4.6: replace "-std=c++11" with "-std=c++0x" as the former is not handled correctly - remove hardcoded "-arch" from test Makefile This patch should not have any effect on lldb on Mac OS X. llvm-svn: 173402
2013-01-25 08:31:48 +08:00
# On non-Apple platforms, -arch becomes -m
ARCHFLAG := -m
Get test executables compiling on Windows. Many of the test executables use pthreads directly. This isn't portable on Windows, so this patch converts these test to use C++11 threads and mutexes. Since Windows' implementation of std::thread classes throw and catch from header files, this patch also disables exceptions when compiling with clang on Windows. Reviewed by: Todd Fiala, Ed Maste Differential Revision: http://reviews.llvm.org/D4816 llvm-svn: 215562
2014-08-14 01:44:53 +08:00
# i386, i686, x86 -> 32
Make CMake choose the target architecture according to the build. Previously, CMake was invoking the test runner and not specifying what architecture to use when building test executables. The Makefiles for the test executables then had logic to choose x64 by default. This doesn't work on Windows because the test compiler would then try to link against the 64-bit MSVCRT and not find them since only the 32-bit MSVCRT was in the path. This patch addresses this by figuring out, at CMake time, whether or not you are building LLDB with a 64 or 32-bit toolchain. Then, it explicitly passes this value to the test runner, causing the test runner to build tests whose architecture matches that of LLDB itself. This can still be overridden by setting the CMake variable LLDB_TEST_EXECUTABLE_ARCH=(x64|x86) llvm-svn: 214443
2014-08-01 05:07:41 +08:00
# amd64, x86_64, x64 -> 64
On FreeBSD "x86_64" is spelled "amd64" llvm-svn: 201802
2014-02-21 02:40:01 +08:00
ifeq "$(ARCH)" "amd64"
Make CMake choose the target architecture according to the build. Previously, CMake was invoking the test runner and not specifying what architecture to use when building test executables. The Makefiles for the test executables then had logic to choose x64 by default. This doesn't work on Windows because the test compiler would then try to link against the 64-bit MSVCRT and not find them since only the 32-bit MSVCRT was in the path. This patch addresses this by figuring out, at CMake time, whether or not you are building LLDB with a 64 or 32-bit toolchain. Then, it explicitly passes this value to the test runner, causing the test runner to build tests whose architecture matches that of LLDB itself. This can still be overridden by setting the CMake variable LLDB_TEST_EXECUTABLE_ARCH=(x64|x86) llvm-svn: 214443
2014-08-01 05:07:41 +08:00
override ARCH := $(subst amd64,64,$(ARCH))
On FreeBSD "x86_64" is spelled "amd64" llvm-svn: 201802
2014-02-21 02:40:01 +08:00
endif
Update test scripts and Makefiles to allow testing with GCC: - introduce new variable ARCHFLAG in make/Makefile.rules to switch between "-arch" on Mac and "-m" everywhere else - update testcase makefiles to use LD_EXTRAS instead of LDFLAGS (the former interacts with Makefile.rules badly) - special treatment for gcc 4.6: replace "-std=c++11" with "-std=c++0x" as the former is not handled correctly - remove hardcoded "-arch" from test Makefile This patch should not have any effect on lldb on Mac OS X. llvm-svn: 173402
2013-01-25 08:31:48 +08:00
ifeq "$(ARCH)" "x86_64"
Make CMake choose the target architecture according to the build. Previously, CMake was invoking the test runner and not specifying what architecture to use when building test executables. The Makefiles for the test executables then had logic to choose x64 by default. This doesn't work on Windows because the test compiler would then try to link against the 64-bit MSVCRT and not find them since only the 32-bit MSVCRT was in the path. This patch addresses this by figuring out, at CMake time, whether or not you are building LLDB with a 64 or 32-bit toolchain. Then, it explicitly passes this value to the test runner, causing the test runner to build tests whose architecture matches that of LLDB itself. This can still be overridden by setting the CMake variable LLDB_TEST_EXECUTABLE_ARCH=(x64|x86) llvm-svn: 214443
2014-08-01 05:07:41 +08:00
override ARCH := $(subst x86_64,64,$(ARCH))
endif
ifeq "$(ARCH)" "x64"
override ARCH := $(subst x64,64,$(ARCH))
Update test scripts and Makefiles to allow testing with GCC: - introduce new variable ARCHFLAG in make/Makefile.rules to switch between "-arch" on Mac and "-m" everywhere else - update testcase makefiles to use LD_EXTRAS instead of LDFLAGS (the former interacts with Makefile.rules badly) - special treatment for gcc 4.6: replace "-std=c++11" with "-std=c++0x" as the former is not handled correctly - remove hardcoded "-arch" from test Makefile This patch should not have any effect on lldb on Mac OS X. llvm-svn: 173402
2013-01-25 08:31:48 +08:00
endif
Get test executables compiling on Windows. Many of the test executables use pthreads directly. This isn't portable on Windows, so this patch converts these test to use C++11 threads and mutexes. Since Windows' implementation of std::thread classes throw and catch from header files, this patch also disables exceptions when compiling with clang on Windows. Reviewed by: Todd Fiala, Ed Maste Differential Revision: http://reviews.llvm.org/D4816 llvm-svn: 215562
2014-08-14 01:44:53 +08:00
ifeq "$(ARCH)" "x86"
override ARCH := $(subst x86,32,$(ARCH))
endif
Update test scripts and Makefiles to allow testing with GCC: - introduce new variable ARCHFLAG in make/Makefile.rules to switch between "-arch" on Mac and "-m" everywhere else - update testcase makefiles to use LD_EXTRAS instead of LDFLAGS (the former interacts with Makefile.rules badly) - special treatment for gcc 4.6: replace "-std=c++11" with "-std=c++0x" as the former is not handled correctly - remove hardcoded "-arch" from test Makefile This patch should not have any effect on lldb on Mac OS X. llvm-svn: 173402
2013-01-25 08:31:48 +08:00
ifeq "$(ARCH)" "i386"
Make CMake choose the target architecture according to the build. Previously, CMake was invoking the test runner and not specifying what architecture to use when building test executables. The Makefiles for the test executables then had logic to choose x64 by default. This doesn't work on Windows because the test compiler would then try to link against the 64-bit MSVCRT and not find them since only the 32-bit MSVCRT was in the path. This patch addresses this by figuring out, at CMake time, whether or not you are building LLDB with a 64 or 32-bit toolchain. Then, it explicitly passes this value to the test runner, causing the test runner to build tests whose architecture matches that of LLDB itself. This can still be overridden by setting the CMake variable LLDB_TEST_EXECUTABLE_ARCH=(x64|x86) llvm-svn: 214443
2014-08-01 05:07:41 +08:00
override ARCH := $(subst i386,32,$(ARCH))
endif
ifeq "$(ARCH)" "i686"
override ARCH := $(subst i686,32,$(ARCH))
Update test scripts and Makefiles to allow testing with GCC: - introduce new variable ARCHFLAG in make/Makefile.rules to switch between "-arch" on Mac and "-m" everywhere else - update testcase makefiles to use LD_EXTRAS instead of LDFLAGS (the former interacts with Makefile.rules badly) - special treatment for gcc 4.6: replace "-std=c++11" with "-std=c++0x" as the former is not handled correctly - remove hardcoded "-arch" from test Makefile This patch should not have any effect on lldb on Mac OS X. llvm-svn: 173402
2013-01-25 08:31:48 +08:00
endif
Add powerpc support for the test suite. Reviewed by Ed Maste at MeetBSD. llvm-svn: 221787
2014-11-12 23:13:58 +08:00
ifeq "$(ARCH)" "powerpc"
override ARCH := $(subst powerpc,32,$(ARCH))
endif
ifeq "$(ARCH)" "powerpc64"
override ARCH := $(subst powerpc64,64,$(ARCH))
endif
Add float/vector registers for ppc64le Summary: Add read and write functions for VSX, VMX and float registers and fix watchpoint size Reviewers: clayborg Reviewed By: clayborg Subscribers: eugene, labath, clayborg, nemanjai, kbarton, JDevlieghere, anajuliapc, gut, lbianc, lldb-commits Differential Revision: https://reviews.llvm.org/D39487 Patch by: Alexandre Yukio Yamashita <alexandre.yamashita@eldorado.org.br> llvm-svn: 317329
2017-11-03 23:22:36 +08:00
ifeq "$(ARCH)" "powerpc64le"
override ARCH := $(subst powerpc64le,64,$(ARCH))
endif
Create NativeRegisterContext for android-arm64 Differential revision: http://reviews.llvm.org/D8058 llvm-svn: 232160
2015-03-13 19:36:47 +08:00
ifeq "$(ARCH)" "aarch64"
override ARCH :=
override ARCHFLAG :=
endif
Disable forcing -marm (A32 instruction set) while running testsuite on arm targets. Differential revision: http://reviews.llvm.org/D14823 llvm-svn: 253973
2015-11-24 18:35:03 +08:00
ifeq "$(ARCH)" "arm"
override ARCH :=
override ARCHFLAG :=
endif
Support Linux on SystemZ as platform This patch adds support for Linux on SystemZ: - A new ArchSpec value of eCore_s390x_generic - A new directory Plugins/ABI/SysV-s390x providing an ABI implementation - Register context support - Native Linux support including watchpoint support - ELF core file support - Misc. support throughout the code base (e.g. breakpoint opcodes) - Test case updates to support the platform This should provide complete support for debugging the SystemZ platform. Not yet supported are optional features like transaction support (zEC12) or SIMD vector support (z13). There is no instruction emulation, since our ABI requires that all code provide correct DWARF CFI at all PC locations in .eh_frame to support unwinding (i.e. -fasynchronous-unwind-tables is on by default). The implementation follows existing platforms in a mostly straightforward manner. A couple of things that are different: - We do not use PTRACE_PEEKUSER / PTRACE_POKEUSER to access single registers, since some registers (access register) reside at offsets in the user area that are multiples of 4, but the PTRACE_PEEKUSER interface only allows accessing aligned 8-byte blocks in the user area. Instead, we use a s390 specific ptrace interface PTRACE_PEEKUSR_AREA / PTRACE_POKEUSR_AREA that allows accessing a whole block of the user area in one go, so in effect allowing to treat parts of the user area as register sets. - SystemZ hardware does not provide any means to implement read watchpoints, only write watchpoints. In fact, we can only support a *single* write watchpoint (but this can span a range of arbitrary size). In LLDB this means we support only a single watchpoint. I've set all test cases that require read watchpoints (or multiple watchpoints) to expected failure on the platform. [ Note that there were two test cases that install a read/write watchpoint even though they nowhere rely on the "read" property. I've changed those to simply use plain write watchpoints. ] Differential Revision: http://reviews.llvm.org/D18978 llvm-svn: 266308
2016-04-14 22:28:34 +08:00
ifeq "$(ARCH)" "s390x"
override ARCH :=
override ARCHFLAG :=
endif
[LLDB][MIPS] Change ARCHFLAG for MIPS SUMMARY: For MIPS, ARCH is specified without m. Reviewers: clayborg Subscribers: nitesh.jain, mohit.bhakkad, sagar, bhushan and lldb-commits Differential Revision: http://reviews.llvm.org/D14978 llvm-svn: 254376
2015-12-01 13:24:17 +08:00
ifeq "$(findstring mips,$(ARCH))" "mips"
override ARCHFLAG := -
endif
Add split symbol support to test makefile & add linux split symbol test case. llvm-svn: 185455
2013-07-03 02:13:13 +08:00
ifeq "$(SPLIT_DEBUG_SYMBOLS)" "YES"
DSYM = $(EXE).debug
endif
Add Linux rules to test makefile llvm-svn: 133456
2011-06-21 03:06:04 +08:00
endif
[DWARFASTParserClang] Strengthen incomplete type handling. Summary: This change fixes pr24916. As associated test has been added. Reviewers: clayborg Subscribers: zturner, lldb-commits Differential Revision: http://reviews.llvm.org/D13224 llvm-svn: 249629
2015-10-08 06:11:52 +08:00
LIMIT_DEBUG_INFO_FLAGS =
[TestCPPAuto] On linux, we need -fno-limit-debug-info. Summary: Also xfailed for GCC as there is an problem with debug info generation. Reviewers: granata.enrico Subscribers: lldb-commits Differential Revision: http://reviews.llvm.org/D15657 llvm-svn: 256067
2015-12-19 08:52:29 +08:00
NO_LIMIT_DEBUG_INFO_FLAGS =
Adds a test to detect when clang omits specialized generic types from debug information when using precompiled headers and -gmodules. llvm-svn: 266791
2016-04-20 02:20:11 +08:00
MODULE_DEBUG_INFO_FLAGS =
[DWARFASTParserClang] Strengthen incomplete type handling. Summary: This change fixes pr24916. As associated test has been added. Reviewers: clayborg Subscribers: zturner, lldb-commits Differential Revision: http://reviews.llvm.org/D13224 llvm-svn: 249629
2015-10-08 06:11:52 +08:00
ifneq (,$(findstring clang,$(CC)))
LIMIT_DEBUG_INFO_FLAGS += -flimit-debug-info
[TestCPPAuto] On linux, we need -fno-limit-debug-info. Summary: Also xfailed for GCC as there is an problem with debug info generation. Reviewers: granata.enrico Subscribers: lldb-commits Differential Revision: http://reviews.llvm.org/D15657 llvm-svn: 256067
2015-12-19 08:52:29 +08:00
NO_LIMIT_DEBUG_INFO_FLAGS += -fno-limit-debug-info
Adds a test to detect when clang omits specialized generic types from debug information when using precompiled headers and -gmodules. llvm-svn: 266791
2016-04-20 02:20:11 +08:00
MODULE_DEBUG_INFO_FLAGS += -gmodules
[DWARFASTParserClang] Strengthen incomplete type handling. Summary: This change fixes pr24916. As associated test has been added. Reviewers: clayborg Subscribers: zturner, lldb-commits Differential Revision: http://reviews.llvm.org/D13224 llvm-svn: 249629
2015-10-08 06:11:52 +08:00
endif
Read macro info from .debug_macro section and use it for expression evaluation. Summary: DWARF 5 proposes a reinvented .debug_macro section. This change follows that spec. Currently, only GCC produces the .debug_macro section and hence the added test is annottated with expectedFailureClang. Reviewers: spyffe, clayborg, tberghammer Subscribers: lldb-commits Differential Revision: http://reviews.llvm.org/D15437 llvm-svn: 255729
2015-12-16 08:22:08 +08:00
DEBUG_INFO_FLAG ?= -g
CFLAGS ?= $(DEBUG_INFO_FLAG) -O0 -fno-builtin
Make -arch work on MacOSX. llvm-svn: 235065
2015-04-16 09:18:05 +08:00
ifeq "$(OS)" "Darwin"
Makefile.rules: move CFLAGS_EXTRAS to the end of compile line This makes sure that any options specified there override generic compiler options. This fixes TestBreakpointIt.py llvm-svn: 316629
2017-10-26 07:56:17 +08:00
CFLAGS += $(ARCHFLAG) $(ARCH) $(FRAMEWORK_INCLUDES) -I$(LLDB_BASE_DIR)include
Make -arch work on MacOSX. llvm-svn: 235065
2015-04-16 09:18:05 +08:00
else
Makefile.rules: move CFLAGS_EXTRAS to the end of compile line This makes sure that any options specified there override generic compiler options. This fixes TestBreakpointIt.py llvm-svn: 316629
2017-10-26 07:56:17 +08:00
CFLAGS += $(ARCHFLAG)$(ARCH) $(FRAMEWORK_INCLUDES) -I$(LLDB_BASE_DIR)include
Make -arch work on MacOSX. llvm-svn: 235065
2015-04-16 09:18:05 +08:00
endif
Teach LLDB how to directly launch processes on the iOS simulator This allows for command-line debugging of iOS simulator binaries (as long as UI is not required, or a full UI simulator has previously been otherwise launched), as well as execution of the LLDB test suite on the iOS simulator This is known to compile on OSX 10.11 GM - feedback from people on other platforms and/or older versions of OSX as to the buildability of this code is greatly appreciated llvm-svn: 252112
2015-11-05 08:46:25 +08:00
Compile the LLDB tests out-of-tree. This patch is the result of a discussion on lldb-dev, see http://lists.llvm.org/pipermail/lldb-dev/2018-January/013111.html for background. For each test (should be eventually: each test configuration) a separate build directory is created and we execute make VPATH=$srcdir/path/to/test -C $builddir/path/to/test -f $srcdir/path/to/test/Makefile -I $srcdir/path/to/test In order to make this work all LLDB tests need to be updated to find the executable in the test build directory, since CWD still points at the test's source directory, which is a requirement for unittest2. Although we have done extensive testing, I'm expecting that this first attempt will break a few bots. Please DO NOT HESITATE TO REVERT this patch in order to get the bots green again. We will likely have to iterate on this some more. Differential Revision: https://reviews.llvm.org/D42281 llvm-svn: 323803
2018-01-31 02:29:16 +08:00
CFLAGS += -I$(SRCDIR) -include $(THIS_FILE_DIR)test_common.h -I$(THIS_FILE_DIR)
Makefile.rules: compile all tests with -fno-limit-debug-info Summary: This flag is on by default for darwin and freebsd, but off for linux. Without it, clang will sometimes not emit debug info for types like std::string. Whether it does this, and which tests will fail because of that depends on the linux distro and c++ library version. A bunch of tests were already setting these flags manually, but here instead I take a whole sale approach and enable this flag for all tests. Any test which does not want to have this flag (right now we have one such test) can turn it off explicitly via CFLAGS_EXTRAS+=$(LIMIT_DEBUG_INFO_FLAGS) This fixes a bunch of data formatter tests on red-hat. Reviewers: davide, jankratochvil Subscribers: emaste, aprantl, krytarowski, JDevlieghere, lldb-commits Differential Revision: https://reviews.llvm.org/D40717 llvm-svn: 319653
2017-12-04 21:31:56 +08:00
CFLAGS += $(NO_LIMIT_DEBUG_INFO_FLAGS) $(ARCH_CFLAGS) $(CFLAGS_EXTRAS)
Update test scripts and Makefiles to allow testing with GCC: - introduce new variable ARCHFLAG in make/Makefile.rules to switch between "-arch" on Mac and "-m" everywhere else - update testcase makefiles to use LD_EXTRAS instead of LDFLAGS (the former interacts with Makefile.rules badly) - special treatment for gcc 4.6: replace "-std=c++11" with "-std=c++0x" as the former is not handled correctly - remove hardcoded "-arch" from test Makefile This patch should not have any effect on lldb on Mac OS X. llvm-svn: 173402
2013-01-25 08:31:48 +08:00
This commit reworks how the thread plan's ShouldStopHere mechanism works, so that it is useful not only for customizing "step-in" behavior (e.g. step-in doesn't step into code with no debug info), but also the behavior of step-in/step-out and step-over when they step out of the frame they started in. I also added as a proof of concept of this reworking a mode for stepping where stepping out of a frame into a frame with no debug information will continue stepping out till it arrives at a frame that does have debug information. This is useful when you are debugging callback based code where the callbacks are separated from the code that initiated them by some library glue you don't care about, among other things. llvm-svn: 203747
2014-03-13 10:47:14 +08:00
# Use this one if you want to build one part of the result without debug information:
Make -arch work on MacOSX. llvm-svn: 235065
2015-04-16 09:18:05 +08:00
ifeq "$(OS)" "Darwin"
Makefile.rules: move CFLAGS_EXTRAS to the end of compile line This makes sure that any options specified there override generic compiler options. This fixes TestBreakpointIt.py llvm-svn: 316629
2017-10-26 07:56:17 +08:00
CFLAGS_NO_DEBUG = -O0 $(ARCHFLAG) $(ARCH) $(FRAMEWORK_INCLUDES) $(ARCH_CFLAGS) $(CFLAGS_EXTRAS)
Make -arch work on MacOSX. llvm-svn: 235065
2015-04-16 09:18:05 +08:00
else
Makefile.rules: move CFLAGS_EXTRAS to the end of compile line This makes sure that any options specified there override generic compiler options. This fixes TestBreakpointIt.py llvm-svn: 316629
2017-10-26 07:56:17 +08:00
CFLAGS_NO_DEBUG = -O0 $(ARCHFLAG)$(ARCH) $(FRAMEWORK_INCLUDES) $(ARCH_CFLAGS) $(CFLAGS_EXTRAS)
Make -arch work on MacOSX. llvm-svn: 235065
2015-04-16 09:18:05 +08:00
endif
This commit reworks how the thread plan's ShouldStopHere mechanism works, so that it is useful not only for customizing "step-in" behavior (e.g. step-in doesn't step into code with no debug info), but also the behavior of step-in/step-out and step-over when they step out of the frame they started in. I also added as a proof of concept of this reworking a mode for stepping where stepping out of a frame into a frame with no debug information will continue stepping out till it arrives at a frame that does have debug information. This is useful when you are debugging callback based code where the callbacks are separated from the code that initiated them by some library glue you don't care about, among other things. llvm-svn: 203747
2014-03-13 10:47:14 +08:00
Run tests with dwo symbol files dwo symbol files are generated when code compiled with the "-gsplit-dwarf" command option (https://gcc.gnu.org/wiki/DebugFission). This CL modifies the test system to run tests with inferiors compile with the "-gsplit-dwarf" Differential revision: http://reviews.llvm.org/D13300 llvm-svn: 249530
2015-10-07 18:02:17 +08:00
ifeq "$(MAKE_DWO)" "YES"
CFLAGS += -gsplit-dwarf
endif
Makefile.rules: Use a shared clang module cache directory. Just to be safe, up until now each test used its own Clang module cache directory. Since the compiler within one testsuite doesn't change it is just as safe to share a clang module directory inside the LLDB test build directory. This saves us from compiling tens of gigabytes of redundant Darwin and Foundation .pcm files and also speeds up running the test suite quite significantly. rdar://problem/36002081 Differential Revision: https://reviews.llvm.org/D54601 llvm-svn: 347056
2018-11-17 00:19:07 +08:00
# Use a shared module cache when building in the default test build directory.
[lldbsuite] Invoke sed on Windows to determine the cache dir for clang Summary: In order to invoke sed on Windows, we need to quote the command correctly. Since we already have commands which do that, move the definitions at the beginning of the file and then re-use them for each command. Reviewers: aprantl, zturner Subscribers: teemperor, lldb-commits Differential Revision: https://reviews.llvm.org/D54709 llvm-svn: 347243
2018-11-20 02:41:33 +08:00
CLANG_MODULE_CACHE_DIR := $(shell echo "$(BUILDDIR)" | sed $(QUOTE)s/lldb-test-build.noindex.*/lldb-test-build.noindex\/module-cache-clang/$(QUOTE))
Makefile.rules: Use a shared clang module cache directory. Just to be safe, up until now each test used its own Clang module cache directory. Since the compiler within one testsuite doesn't change it is just as safe to share a clang module directory inside the LLDB test build directory. This saves us from compiling tens of gigabytes of redundant Darwin and Foundation .pcm files and also speeds up running the test suite quite significantly. rdar://problem/36002081 Differential Revision: https://reviews.llvm.org/D54601 llvm-svn: 347056
2018-11-17 00:19:07 +08:00
Makefile.rules: Degrade gracefully on Windows machines without sed. llvm-svn: 347104
2018-11-17 06:44:57 +08:00
ifeq "$(findstring lldb-test-build.noindex, $(BUILDDIR))" ""
CLANG_MODULE_CACHE_DIR := $(BUILDDIR)/module-cache
$(warning failed to set the shared clang module cache dir)
Makefile.rules: Use a shared clang module cache directory. Just to be safe, up until now each test used its own Clang module cache directory. Since the compiler within one testsuite doesn't change it is just as safe to share a clang module directory inside the LLDB test build directory. This saves us from compiling tens of gigabytes of redundant Darwin and Foundation .pcm files and also speeds up running the test suite quite significantly. rdar://problem/36002081 Differential Revision: https://reviews.llvm.org/D54601 llvm-svn: 347056
2018-11-17 00:19:07 +08:00
endif
Use test-specific module caches to avoid stale header conflicts Stale global module caches cause problems for the bots. The modules become invalid when clang headers are updated by version control, and tests which use these modules fail to compile, e.g: fatal error: file '.../__stddef_max_align_t.h' has been modified since the module file '/var/.../Darwin.pcm' was built note: please rebuild precompiled header '/var/.../Darwin.pcm' Eventually we should transition to having just a single module cache to speed tests up. This patch should be just enough to fix the spurious bot failures due to stale caches. rdar://36479805, also related to llvm.org/PR36048 Differential Revision: https://reviews.llvm.org/D42277 llvm-svn: 323450
2018-01-26 02:01:27 +08:00
MANDATORY_MODULE_BUILD_CFLAGS := -fmodules -gmodules -fmodules-cache-path=$(CLANG_MODULE_CACHE_DIR)
Add "-gmodules" support to the test suite. This change adds the capability of building test inferiors with the -gmodules flag to enable module debug info support. Windows is excluded per @zturner. Reviewers: granata.enrico, aprantl, zturner, labath Subscribers: zturner, labath, lldb-commits Differential Revision: http://reviews.llvm.org/D19998 llvm-svn: 270848
2016-05-26 21:57:03 +08:00
ifeq "$(MAKE_GMODULES)" "YES"
Use test-specific module caches to avoid stale header conflicts Stale global module caches cause problems for the bots. The modules become invalid when clang headers are updated by version control, and tests which use these modules fail to compile, e.g: fatal error: file '.../__stddef_max_align_t.h' has been modified since the module file '/var/.../Darwin.pcm' was built note: please rebuild precompiled header '/var/.../Darwin.pcm' Eventually we should transition to having just a single module cache to speed tests up. This patch should be just enough to fix the spurious bot failures due to stale caches. rdar://36479805, also related to llvm.org/PR36048 Differential Revision: https://reviews.llvm.org/D42277 llvm-svn: 323450
2018-01-26 02:01:27 +08:00
CFLAGS += $(MANDATORY_MODULE_BUILD_CFLAGS)
Enable C++ tests to run in the -gmodules configuration on Darwin. This addresses PR36048 (http://llvm.org/bugs/show_bug.cgi?id=36048) rdar://problem/36776281 llvm-svn: 343545
2018-10-02 06:27:42 +08:00
CXXFLAGS += $(MANDATORY_MODULE_BUILD_CFLAGS)
ifeq "$(OS)" "Darwin"
CXXFLAGS += -fcxx-modules
endif
Add "-gmodules" support to the test suite. This change adds the capability of building test inferiors with the -gmodules flag to enable module debug info support. Windows is excluded per @zturner. Reviewers: granata.enrico, aprantl, zturner, labath Subscribers: zturner, labath, lldb-commits Differential Revision: http://reviews.llvm.org/D19998 llvm-svn: 270848
2016-05-26 21:57:03 +08:00
endif
Android.rules: Use libc++ by default libstdc++ will soon be dropped from the android NDK. This patch makes sure we are prepared for that by using libc++ in tests by default (i.e., except for libstdc++ data formatter tests). Only a couple of small tweaks were needed to make this work: - Add the libc++ include paths to CXXFLAGS only. This was necessary to make the tests compile with -fmodules. The modules tests have been disabled, but this way, they will be ready for them if they are enabled. - in one test I had to add an explicit std::string copy to make sure the copy constructor is there for the expression evaluator to find it. llvm-svn: 335344
2018-06-22 21:13:29 +08:00
CXXFLAGS += -std=c++11 $(CFLAGS) $(ARCH_CXXFLAGS)
Simplify lang/objc/self/Makefile, plus it's wrong. :-) For Makefile.rules, the modification of CFLAGS (addition of -arch $(ARCH) for Darwin) needs to come before the consuming of CFLAGS, not after. llvm-svn: 137140
2011-08-10 04:07:16 +08:00
LD = $(CC)
LDFLAGS ?= $(CFLAGS)
testsuite/android: build test executables with the android ndk directly Summary: This teaches the test makefiles about the Android NDK, so we are able to run the tests without first going through the make_standalone_toolchain script. The motivation for this is the ability to run both libc++ and libstdc++ tests together, which previously was not possible because make_standalone_toolchain bakes in the STL to use during toolchain creation time. The support for this is not present yet -- this change only make sure we don't regress for existing funcionality (gcc w/ libstdc++). Clang and libc++ support will be added later. I've checked that the mips android targets compile after this change, but I have no way of checking whether this breaks anything. If you are reading this and it broke you, let me know. Reviewers: tberghammer, danalbert Subscribers: srhines, lldb-commits Differential Revision: https://reviews.llvm.org/D30410 llvm-svn: 296869
2017-03-03 21:49:34 +08:00
LDFLAGS += $(LD_EXTRAS) $(ARCH_LDFLAGS)
Initial patchset to get the testsuite running against armv7 and arm64 iOS devices. Normal customer devices won't be able to run these tests, we're hoping to get a public facing bot set up at some point. Both devices pass the testsuite without any errors or failures. I have seen some instability with the armv7 test runs, I may submit additional patches to address this. arm64 looks good. I'll be watching the bots for the rest of today; if any problems are introduced by this patch I'll revert it - if anyone sees a problem with their bot that I don't see, please do the same. I know it's a rather large patch. One change I had to make specifically for iOS devices was that debugserver can't create files. There were several tests that launch the inferior process redirecting its output to a file, then they retrieve the file. They were not trying to test file redirection in these tests, so I rewrote those to write their output to a file directly. llvm-svn: 314132
2017-09-26 02:19:39 +08:00
ifeq (,$(filter $(OS), Windows_NT Android Darwin))
Merge ENABLE_THREADS and ENABLE_STD_THREADS markers Both of these markers are used in the test suit for annotating when a test needs multi threaded support. Previously they had slightly different meening but they converged to the point where they are used interchangably. This CL removes the ENABLE_STD_THREADS one to simplify the test suite and avoid some confusion. Differential revision: http://reviews.llvm.org/D15498 llvm-svn: 255641
2015-12-15 20:11:00 +08:00
ifneq (,$(filter YES,$(ENABLE_THREADS)))
Using -pthread instead of -lpthread to appease GCC. llvm-svn: 237864
2015-05-21 08:19:15 +08:00
LDFLAGS += -pthread
Missing `-lpthread` causes gcc test failure. Summary: `-lpthread` was removed for `g++ -std=c++11` on Linux due to llvm.org/pr21553, but the original issue doesn't seem to be reproducible anymore. Even if it were, it had nothing to do with compiling inferiors. Reviewers: sbest, sivachandra, chying Subscribers: lldb-commits Differential Revision: http://reviews.llvm.org/D8991 llvm-svn: 234770
2015-04-14 02:21:31 +08:00
endif
Get test executables compiling on Windows. Many of the test executables use pthreads directly. This isn't portable on Windows, so this patch converts these test to use C++11 threads and mutexes. Since Windows' implementation of std::thread classes throw and catch from header files, this patch also disables exceptions when compiling with clang on Windows. Reviewed by: Todd Fiala, Ed Maste Differential Revision: http://reviews.llvm.org/D4816 llvm-svn: 215562
2014-08-14 01:44:53 +08:00
endif
Simplify lang/objc/self/Makefile, plus it's wrong. :-) For Makefile.rules, the modification of CFLAGS (addition of -arch $(ARCH) for Darwin) needs to come before the consuming of CFLAGS, not after. llvm-svn: 137140
2011-08-10 04:07:16 +08:00
OBJECTS =
EXE ?= a.out
Add Linux rules to test makefile llvm-svn: 133456
2011-06-21 03:06:04 +08:00
ifneq "$(DYLIB_NAME)" ""
ifeq "$(OS)" "Darwin"
DYLIB_FILENAME = lib$(DYLIB_NAME).dylib
Update TestLoadUnload to use base Makefile. Summary: The current Makefile scheme only allows one dylib to be specified in each make invocation, so TestLoadUnload had a custom Makefile that's unrelated to the base Makefile.rules. This change uses recursive make invocations to bypass the single dylib restriction. See D11202 for more context. Reviewers: clayborg Subscribers: chaoren, lldb-commits Differential Revision: http://reviews.llvm.org/D11367 llvm-svn: 242813
2015-07-22 01:50:16 +08:00
DYLIB_EXECUTABLE_PATH ?= @executable_path
Missing `-lpthread` causes gcc test failure. Summary: `-lpthread` was removed for `g++ -std=c++11` on Linux due to llvm.org/pr21553, but the original issue doesn't seem to be reproducible anymore. Even if it were, it had nothing to do with compiling inferiors. Reviewers: sbest, sivachandra, chying Subscribers: lldb-commits Differential Revision: http://reviews.llvm.org/D8991 llvm-svn: 234770
2015-04-14 02:21:31 +08:00
else ifeq "$(OS)" "Windows_NT"
DYLIB_FILENAME = $(DYLIB_NAME).dll
Add Linux rules to test makefile llvm-svn: 133456
2011-06-21 03:06:04 +08:00
else
DYLIB_FILENAME = lib$(DYLIB_NAME).so
endif
endif
Makefile refactoring for the test suite. Added a make directory under test, which hosts the Makefile.rules and modified most of the Makefiles under each test case directories to utilize Mekefile.rules. Added a description of 'make' directory into README-TestSuite file. llvm-svn: 111868
2010-08-24 07:56:08 +08:00
The cxx_compiler function should not blindly return clang++ as the C++ compiler if $(CC) contains "clang". Instead, it should perform a textual replacement of $(CC) from "clang" to "clang++". The same is true for "llvm-gcc" to "llvm-g++" and for "gcc" to "g++". This way, we keep the path component of the $(CC) passed in from the user and do not end up with a mixed toolchains with different paths. Ditto for a newly added function called cxx_linker. llvm-svn: 123451
2011-01-15 02:19:53 +08:00
# Function that returns the counterpart C++ compiler, given $(CC) as arg.
Re-landing a cleaned up implementation of r284550 This time it should actually work. The previous implementaiton was not getting the linker or compiler flag set correctly in all the right situations. By moving the check down and basing it of whether or not CXX is set I we can have the logic to add the flags exist only once for the linker and once for the compiler instead of duplicating it. llvm-svn: 284756
2016-10-21 02:01:19 +08:00
cxx_compiler_notdir = $(if $(findstring icc,$(1)), \
$(subst icc,icpc,$(1)), \
$(if $(findstring llvm-gcc,$(1)), \
$(subst llvm-gcc,llvm-g++,$(1)), \
$(if $(findstring gcc,$(1)), \
$(subst gcc,g++,$(1)), \
$(subst cc,c++,$(1)))))
Patch from Todd Fiala for http://llvm.org/bugs/show_bug.cgi?id=17961 llvm-svn: 195500
2013-11-23 05:05:25 +08:00
cxx_compiler = $(if $(findstring /,$(1)),$(join $(dir $(1)), $(call cxx_compiler_notdir,$(notdir $(1)))),$(call cxx_compiler_notdir,$(1)))
The cxx_compiler function should not blindly return clang++ as the C++ compiler if $(CC) contains "clang". Instead, it should perform a textual replacement of $(CC) from "clang" to "clang++". The same is true for "llvm-gcc" to "llvm-g++" and for "gcc" to "g++". This way, we keep the path component of the $(CC) passed in from the user and do not end up with a mixed toolchains with different paths. Ditto for a newly added function called cxx_linker. llvm-svn: 123451
2011-01-15 02:19:53 +08:00
# Function that returns the C++ linker, given $(CC) as arg.
Re-landing a cleaned up implementation of r284550 This time it should actually work. The previous implementaiton was not getting the linker or compiler flag set correctly in all the right situations. By moving the check down and basing it of whether or not CXX is set I we can have the logic to add the flags exist only once for the linker and once for the compiler instead of duplicating it. llvm-svn: 284756
2016-10-21 02:01:19 +08:00
cxx_linker_notdir = $(if $(findstring icc,$(1)), \
$(subst icc,icpc,$(1)), \
$(if $(findstring llvm-gcc,$(1)), \
$(subst llvm-gcc,llvm-g++,$(1)), \
$(if $(findstring gcc,$(1)), \
$(subst gcc,g++,$(1)), \
$(subst cc,c++,$(1)))))
Patch from Todd Fiala for http://llvm.org/bugs/show_bug.cgi?id=17961 llvm-svn: 195500
2013-11-23 05:05:25 +08:00
cxx_linker = $(if $(findstring /,$(1)),$(join $(dir $(1)), $(call cxx_linker_notdir,$(notdir $(1)))),$(call cxx_linker_notdir,$(1)))
Added a utility function to return the counterpart C++ compiler of $(CC) and use it inside Makefile.rules to return clang++ on clang and llvm-g++ on llvm-gcc. Removed CPLUSPLUSFLAGS which is simply wrong and CPPFLAGS which is unnecessary. llvm-svn: 115125
2010-09-30 09:22:34 +08:00
Correct makefile.rules to use arm/aarch64 target specific AR and OBJCOPY Differential revision: https://reviews.llvm.org/D20386 llvm-svn: 278947
2016-08-18 00:45:34 +08:00
ifneq "$(OS)" "Darwin"
CLANG_OR_GCC := $(strip $(if $(findstring clang,$(CC)), \
$(findstring clang,$(CC)), \
$(if $(findstring gcc,$(CC)), \
$(findstring gcc,$(CC)), \
cc)))
CC_LASTWORD := $(strip $(lastword $(subst -, ,$(CC))))
replace_with = $(strip $(if $(findstring $(3),$(CC_LASTWORD)), \
$(subst $(3),$(1),$(2)), \
$(subst $(3),$(1),$(subst -$(CC_LASTWORD),,$(2)))))
ifeq "$(notdir $(CC))" "$(CC)"
replace_cc_with = $(call replace_with,$(1),$(CC),$(CLANG_OR_GCC))
else
replace_cc_with = $(join $(dir $(CC)),$(call replace_with,$(1),$(notdir $(CC)),$(CLANG_OR_GCC)))
endif
OBJCOPY ?= $(call replace_cc_with,objcopy)
ARCHIVER ?= $(call replace_cc_with,ar)
override AR = $(ARCHIVER)
endif
ifdef PIE
[lldbsuite] Invoke sed on Windows to determine the cache dir for clang Summary: In order to invoke sed on Windows, we need to quote the command correctly. Since we already have commands which do that, move the definitions at the beginning of the file and then re-use them for each command. Reviewers: aprantl, zturner Subscribers: teemperor, lldb-commits Differential Revision: https://reviews.llvm.org/D54709 llvm-svn: 347243
2018-11-20 02:41:33 +08:00
LDFLAGS += -pie
Correct makefile.rules to use arm/aarch64 target specific AR and OBJCOPY Differential revision: https://reviews.llvm.org/D20386 llvm-svn: 278947
2016-08-18 00:45:34 +08:00
endif
Revert rL277429: Correct makefile.rules to use toolchain specific AR and OBJCOPY This commit is causing problems on gcc-* compiler with version number sufix. Requires a new solution will post a follow up patch. Differential revision: https://reviews.llvm.org/D20386 llvm-svn: 277453
2016-08-02 21:17:49 +08:00
Get test executables compiling on Windows. Many of the test executables use pthreads directly. This isn't portable on Windows, so this patch converts these test to use C++11 threads and mutexes. Since Windows' implementation of std::thread classes throw and catch from header files, this patch also disables exceptions when compiling with clang on Windows. Reviewed by: Todd Fiala, Ed Maste Differential Revision: http://reviews.llvm.org/D4816 llvm-svn: 215562
2014-08-14 01:44:53 +08:00
#----------------------------------------------------------------------
Link test executables with LLD on Windows. Clang generates DWARF debug info with section names longer than 8 characters. This is only supported by an extension to PE/COFF which the MSVC linker doesn't implement. So trying to link DWARF-enabled object files with MSVC will lead to corrupt debug information in the executable. llvm-svn: 223088
2014-12-02 07:13:41 +08:00
# Windows specific options
Get test executables compiling on Windows. Many of the test executables use pthreads directly. This isn't portable on Windows, so this patch converts these test to use C++11 threads and mutexes. Since Windows' implementation of std::thread classes throw and catch from header files, this patch also disables exceptions when compiling with clang on Windows. Reviewed by: Todd Fiala, Ed Maste Differential Revision: http://reviews.llvm.org/D4816 llvm-svn: 215562
2014-08-14 01:44:53 +08:00
#----------------------------------------------------------------------
ifeq "$(OS)" "Windows_NT"
ifneq (,$(findstring clang,$(CC)))
Link test executables with LLD on Windows. Clang generates DWARF debug info with section names longer than 8 characters. This is only supported by an extension to PE/COFF which the MSVC linker doesn't implement. So trying to link DWARF-enabled object files with MSVC will lead to corrupt debug information in the executable. llvm-svn: 223088
2014-12-02 07:13:41 +08:00
# Clang for Windows doesn't support C++ Exceptions
Get test executables compiling on Windows. Many of the test executables use pthreads directly. This isn't portable on Windows, so this patch converts these test to use C++11 threads and mutexes. Since Windows' implementation of std::thread classes throw and catch from header files, this patch also disables exceptions when compiling with clang on Windows. Reviewed by: Todd Fiala, Ed Maste Differential Revision: http://reviews.llvm.org/D4816 llvm-svn: 215562
2014-08-14 01:44:53 +08:00
CXXFLAGS += -fno-exceptions
CXXFLAGS += -D_HAS_EXCEPTIONS=0
Make the LLDB test suite work with MSVC 2017 on Windows. llvm-svn: 297405
2017-03-10 03:54:23 +08:00
# MSVC 2015 or higher is required, which depends on c++14, so
# append these values unconditionally.
CXXFLAGS += -fms-compatibility-version=19.0
override CXXFLAGS := $(subst -std=c++11,-std=c++14,$(CXXFLAGS))
Link test executables with LLD on Windows. Clang generates DWARF debug info with section names longer than 8 characters. This is only supported by an extension to PE/COFF which the MSVC linker doesn't implement. So trying to link DWARF-enabled object files with MSVC will lead to corrupt debug information in the executable. llvm-svn: 223088
2014-12-02 07:13:41 +08:00
# The MSVC linker doesn't understand long section names
# generated by the clang compiler.
LDFLAGS += -fuse-ld=lld
Get test executables compiling on Windows. Many of the test executables use pthreads directly. This isn't portable on Windows, so this patch converts these test to use C++11 threads and mutexes. Since Windows' implementation of std::thread classes throw and catch from header files, this patch also disables exceptions when compiling with clang on Windows. Reviewed by: Todd Fiala, Ed Maste Differential Revision: http://reviews.llvm.org/D4816 llvm-svn: 215562
2014-08-14 01:44:53 +08:00
endif
endif
Fix global makefiles for the tests to support android Two changes are required to compile the tests for android * Disable the usage of -lpthread as it is included by default on android * Add -pie to the linker flags because android only support position independent executables Differential revision: http://reviews.llvm.org/D7856 llvm-svn: 230487
2015-02-25 21:02:08 +08:00
#----------------------------------------------------------------------
Fix Makefiles in the data-formatter-stl tests - specify compiler flag -stdlib=libstdc++ only if using clang (not supported in gcc) llvm-svn: 183333
2013-06-06 03:32:34 +08:00
# C++ standard library options
#----------------------------------------------------------------------
ifeq (1,$(USE_LIBSTDCPP))
# Clang requires an extra flag: -stdlib=libstdc++
ifneq (,$(findstring clang,$(CC)))
Fix libstdc++ failure where <atomic> is not able to be imported on Darwin systems. The adding of <atomic> to test_common.h broke 12 tests on Darwin. We work around this by not including <atomic> when building on darwin for libstdc++ tests. llvm-svn: 269372
2016-05-13 06:33:02 +08:00
CXXFLAGS += -stdlib=libstdc++ -DLLDB_USING_LIBSTDCPP
Fix Makefiles in the data-formatter-stl tests - specify compiler flag -stdlib=libstdc++ only if using clang (not supported in gcc) llvm-svn: 183333
2013-06-06 03:32:34 +08:00
LDFLAGS += -stdlib=libstdc++
endif
endif
Added a new makefile setting that can be set in LLDB makefiles: USE_LIBCPP. This will enable libc++ support. Improved the makefile "clean" to include deleting all ".d.[0-9]+" files. Added options to the "lldb/examples/lookup" example and made it build using the LLDB_BUILD_DIR. If this is not set, it will default to "/Applications/Xcode.app/Contents/SharedFrameworks" on Darwin. Added options to the "lldb/examples/function" example and made it build using the LLDB_BUILD_DIR. llvm-svn: 183949
2013-06-14 05:27:14 +08:00
ifeq (1,$(USE_LIBCPP))
Centralize libc++ test skipping logic Summary: This aims to replace the different decorators we've had on each libc++ test with a single solution. Each libc++ will be assigned to the "libc++" category and a single central piece of code will decide whether we are actually able to run libc++ test in the given configuration by enabling or disabling the category (while giving the user the opportunity to override this). I started this effort because I wanted to get libc++ tests running on android, and none of the existing decorators worked for this use case: - skipIfGcc - incorrect, we can build libc++ executables on android with gcc (in fact, after this, we can now do it on linux as well) - lldbutil.skip_if_library_missing - this checks whether libc++.so is loaded in the proces, which fails in case of a statically linked libc++ (this makes copying executables to the remote target easier to manage). To make this work I needed to split out the pseudo_barrier code from the force-included file, as libc++'s atomic does not play well with gcc on linux, and this made every test fail, even though we need the code only in the threading tests. So far, I am only annotating one of the tests with this category. If this does not break anything, I'll proceed to update the rest. Reviewers: jingham, zturner, EricWF Subscribers: srhines, lldb-commits Differential Revision: https://reviews.llvm.org/D30984 llvm-svn: 299028
2017-03-30 05:01:14 +08:00
CXXFLAGS += -DLLDB_USING_LIBCPP
ifeq "$(OS)" "Linux"
ifneq (,$(findstring clang,$(CC)))
Android.rules: Add libc++ support Summary: This adds support for building libc++ tests when targetting android. The tests are still not passing due to several other problems, but this way we can at least build them. Reviewers: eugene, EricWF, danalbert Subscribers: srhines, lldb-commits Differential Revision: https://reviews.llvm.org/D30737 llvm-svn: 297616
2017-03-13 20:07:48 +08:00
CXXFLAGS += -stdlib=libc++
On Linux, if you can't actually locate the libc++ install, do not attempt to use it The failure mode when one gets this wrong is quite gnarly to then walk oneself out of, and if you can't actually find the library, trying to build against it is fairly pointless anyway This + my previous skip_if_library_missing change should make running the libc++ tests on a Linux machine without it much more seamless llvm-svn: 248057
2015-09-19 06:26:34 +08:00
LDFLAGS += -stdlib=libc++
Centralize libc++ test skipping logic Summary: This aims to replace the different decorators we've had on each libc++ test with a single solution. Each libc++ will be assigned to the "libc++" category and a single central piece of code will decide whether we are actually able to run libc++ test in the given configuration by enabling or disabling the category (while giving the user the opportunity to override this). I started this effort because I wanted to get libc++ tests running on android, and none of the existing decorators worked for this use case: - skipIfGcc - incorrect, we can build libc++ executables on android with gcc (in fact, after this, we can now do it on linux as well) - lldbutil.skip_if_library_missing - this checks whether libc++.so is loaded in the proces, which fails in case of a statically linked libc++ (this makes copying executables to the remote target easier to manage). To make this work I needed to split out the pseudo_barrier code from the force-included file, as libc++'s atomic does not play well with gcc on linux, and this made every test fail, even though we need the code only in the threading tests. So far, I am only annotating one of the tests with this category. If this does not break anything, I'll proceed to update the rest. Reviewers: jingham, zturner, EricWF Subscribers: srhines, lldb-commits Differential Revision: https://reviews.llvm.org/D30984 llvm-svn: 299028
2017-03-30 05:01:14 +08:00
else
CXXFLAGS += -isystem /usr/include/c++/v1
LDFLAGS += -lc++
On Linux, if you can't actually locate the libc++ install, do not attempt to use it The failure mode when one gets this wrong is quite gnarly to then walk oneself out of, and if you can't actually find the library, trying to build against it is fairly pointless anyway This + my previous skip_if_library_missing change should make running the libc++ tests on a Linux machine without it much more seamless llvm-svn: 248057
2015-09-19 06:26:34 +08:00
endif
Centralize libc++ test skipping logic Summary: This aims to replace the different decorators we've had on each libc++ test with a single solution. Each libc++ will be assigned to the "libc++" category and a single central piece of code will decide whether we are actually able to run libc++ test in the given configuration by enabling or disabling the category (while giving the user the opportunity to override this). I started this effort because I wanted to get libc++ tests running on android, and none of the existing decorators worked for this use case: - skipIfGcc - incorrect, we can build libc++ executables on android with gcc (in fact, after this, we can now do it on linux as well) - lldbutil.skip_if_library_missing - this checks whether libc++.so is loaded in the proces, which fails in case of a statically linked libc++ (this makes copying executables to the remote target easier to manage). To make this work I needed to split out the pseudo_barrier code from the force-included file, as libc++'s atomic does not play well with gcc on linux, and this made every test fail, even though we need the code only in the threading tests. So far, I am only annotating one of the tests with this category. If this does not break anything, I'll proceed to update the rest. Reviewers: jingham, zturner, EricWF Subscribers: srhines, lldb-commits Differential Revision: https://reviews.llvm.org/D30984 llvm-svn: 299028
2017-03-30 05:01:14 +08:00
else ifeq "$(OS)" "Android"
# Nothing to do, this is already handled in
# Android.rules.
else
CXXFLAGS += -stdlib=libc++
LDFLAGS += -stdlib=libc++
Added a new makefile setting that can be set in LLDB makefiles: USE_LIBCPP. This will enable libc++ support. Improved the makefile "clean" to include deleting all ".d.[0-9]+" files. Added options to the "lldb/examples/lookup" example and made it build using the LLDB_BUILD_DIR. If this is not set, it will default to "/Applications/Xcode.app/Contents/SharedFrameworks" on Darwin. Added options to the "lldb/examples/function" example and made it build using the LLDB_BUILD_DIR. llvm-svn: 183949
2013-06-14 05:27:14 +08:00
endif
endif
Makefile refactoring for the test suite. Added a make directory under test, which hosts the Makefile.rules and modified most of the Makefiles under each test case directories to utilize Mekefile.rules. Added a description of 'make' directory into README-TestSuite file. llvm-svn: 111868
2010-08-24 07:56:08 +08:00
#----------------------------------------------------------------------
# dylib settings
#----------------------------------------------------------------------
ifneq "$(strip $(DYLIB_C_SOURCES))" ""
DYLIB_OBJECTS +=$(strip $(DYLIB_C_SOURCES:.c=.o))
endif
Added support for looking up the complete type for Objective-C classes. This allows LLDB to find ivars declared in class extensions in modules other than where the debugger is currently stopped (we already supported this when the debugger was stopped in the same module as the definition). This involved the following main changes: - The ObjCLanguageRuntime now knows how to hunt for the authoritative version of an Objective-C type. It looks for the symbol indicating a definition, and then gets the type from the module containing that symbol. - ValueObjects now report their type with a potential override, and the override is set if the type of the ValueObject is an Objective-C class or pointer type that is defined somewhere other than the original reported type. This means that "frame variable" will always use the complete type if one is available. - The ClangASTSource now looks for the complete type when looking for ivars. This means that "expr" will always use the complete type if one is available. - I added a testcase that verifies that both "frame variable" and "expr" work. llvm-svn: 151214
2012-02-23 07:57:45 +08:00
ifneq "$(strip $(DYLIB_OBJC_SOURCES))" ""
DYLIB_OBJECTS +=$(strip $(DYLIB_OBJC_SOURCES:.m=.o))
endif
Update makefile rules to support C++ files in shared libraries and fix how the linker driver is found. llvm-svn: 147814
2012-01-10 08:00:15 +08:00
ifneq "$(strip $(DYLIB_CXX_SOURCES))" ""
[lldbsuite] Invoke sed on Windows to determine the cache dir for clang Summary: In order to invoke sed on Windows, we need to quote the command correctly. Since we already have commands which do that, move the definitions at the beginning of the file and then re-use them for each command. Reviewers: aprantl, zturner Subscribers: teemperor, lldb-commits Differential Revision: https://reviews.llvm.org/D54709 llvm-svn: 347243
2018-11-20 02:41:33 +08:00
DYLIB_OBJECTS +=$(strip $(DYLIB_CXX_SOURCES:.cpp=.o))
CXX = $(call cxx_compiler,$(CC))
LD = $(call cxx_linker,$(CC))
Update makefile rules to support C++ files in shared libraries and fix how the linker driver is found. llvm-svn: 147814
2012-01-10 08:00:15 +08:00
endif
Makefile refactoring for the test suite. Added a make directory under test, which hosts the Makefile.rules and modified most of the Makefiles under each test case directories to utilize Mekefile.rules. Added a description of 'make' directory into README-TestSuite file. llvm-svn: 111868
2010-08-24 07:56:08 +08:00
Adds a test to detect when clang omits specialized generic types from debug information when using precompiled headers and -gmodules. llvm-svn: 266791
2016-04-20 02:20:11 +08:00
#----------------------------------------------------------------------
# Check if we have a precompiled header
#----------------------------------------------------------------------
ifneq "$(strip $(PCH_CXX_SOURCE))" ""
[lldbsuite] Invoke sed on Windows to determine the cache dir for clang Summary: In order to invoke sed on Windows, we need to quote the command correctly. Since we already have commands which do that, move the definitions at the beginning of the file and then re-use them for each command. Reviewers: aprantl, zturner Subscribers: teemperor, lldb-commits Differential Revision: https://reviews.llvm.org/D54709 llvm-svn: 347243
2018-11-20 02:41:33 +08:00
PCH_OUTPUT = $(PCH_CXX_SOURCE:.h=.h.pch)
PCHFLAGS = -include $(PCH_CXX_SOURCE)
Adds a test to detect when clang omits specialized generic types from debug information when using precompiled headers and -gmodules. llvm-svn: 266791
2016-04-20 02:20:11 +08:00
endif
Makefile refactoring for the test suite. Added a make directory under test, which hosts the Makefile.rules and modified most of the Makefiles under each test case directories to utilize Mekefile.rules. Added a description of 'make' directory into README-TestSuite file. llvm-svn: 111868
2010-08-24 07:56:08 +08:00
#----------------------------------------------------------------------
# Check if we have any C source files
#----------------------------------------------------------------------
ifneq "$(strip $(C_SOURCES))" ""
OBJECTS +=$(strip $(C_SOURCES:.c=.o))
endif
#----------------------------------------------------------------------
# Check if we have any C++ source files
#----------------------------------------------------------------------
ifneq "$(strip $(CXX_SOURCES))" ""
OBJECTS +=$(strip $(CXX_SOURCES:.cpp=.o))
Added a utility function to return the counterpart C++ compiler of $(CC) and use it inside Makefile.rules to return clang++ on clang and llvm-g++ on llvm-gcc. Removed CPLUSPLUSFLAGS which is simply wrong and CPPFLAGS which is unnecessary. llvm-svn: 115125
2010-09-30 09:22:34 +08:00
CXX = $(call cxx_compiler,$(CC))
The cxx_compiler function should not blindly return clang++ as the C++ compiler if $(CC) contains "clang". Instead, it should perform a textual replacement of $(CC) from "clang" to "clang++". The same is true for "llvm-gcc" to "llvm-g++" and for "gcc" to "g++". This way, we keep the path component of the $(CC) passed in from the user and do not end up with a mixed toolchains with different paths. Ditto for a newly added function called cxx_linker. llvm-svn: 123451
2011-01-15 02:19:53 +08:00
LD = $(call cxx_linker,$(CC))
Makefile refactoring for the test suite. Added a make directory under test, which hosts the Makefile.rules and modified most of the Makefiles under each test case directories to utilize Mekefile.rules. Added a description of 'make' directory into README-TestSuite file. llvm-svn: 111868
2010-08-24 07:56:08 +08:00
endif
#----------------------------------------------------------------------
# Check if we have any ObjC source files
#----------------------------------------------------------------------
ifneq "$(strip $(OBJC_SOURCES))" ""
OBJECTS +=$(strip $(OBJC_SOURCES:.m=.o))
LDFLAGS +=-lobjc
endif
#----------------------------------------------------------------------
# Check if we have any ObjC++ source files
#----------------------------------------------------------------------
ifneq "$(strip $(OBJCXX_SOURCES))" ""
OBJECTS +=$(strip $(OBJCXX_SOURCES:.mm=.o))
Added a utility function to return the counterpart C++ compiler of $(CC) and use it inside Makefile.rules to return clang++ on clang and llvm-g++ on llvm-gcc. Removed CPLUSPLUSFLAGS which is simply wrong and CPPFLAGS which is unnecessary. llvm-svn: 115125
2010-09-30 09:22:34 +08:00
CXX = $(call cxx_compiler,$(CC))
The cxx_compiler function should not blindly return clang++ as the C++ compiler if $(CC) contains "clang". Instead, it should perform a textual replacement of $(CC) from "clang" to "clang++". The same is true for "llvm-gcc" to "llvm-g++" and for "gcc" to "g++". This way, we keep the path component of the $(CC) passed in from the user and do not end up with a mixed toolchains with different paths. Ditto for a newly added function called cxx_linker. llvm-svn: 123451
2011-01-15 02:19:53 +08:00
LD = $(call cxx_linker,$(CC))
Add a suffix rule for compiling objc++ files and a sample directory under test/lang/objcxx. llvm-svn: 155501
2012-04-25 07:05:07 +08:00
ifeq "$(findstring lobjc,$(LDFLAGS))" ""
Makefile refactoring for the test suite. Added a make directory under test, which hosts the Makefile.rules and modified most of the Makefiles under each test case directories to utilize Mekefile.rules. Added a description of 'make' directory into README-TestSuite file. llvm-svn: 111868
2010-08-24 07:56:08 +08:00
LDFLAGS +=-lobjc
endif
endif
rdar://problem/10680957 Need a test case that tests DWARF with .o in .a files test/functionalities/archives: Produces libfoo.a from a.o and b.o. Test breaking inside functions defined inside the libfoo.a BSD Archive. test/make/makefile.rules: Some additional rules to sepcify archive building. For example: ARCHIVE_NAME := libfoo.a ARCHIVE_C_SOURCES := a.c b.c llvm-svn: 148066
2012-01-13 07:09:42 +08:00
#----------------------------------------------------------------------
# Check if we have any C source files for archive
#----------------------------------------------------------------------
ifneq "$(strip $(ARCHIVE_C_SOURCES))" ""
ARCHIVE_OBJECTS +=$(strip $(ARCHIVE_C_SOURCES:.c=.o))
endif
#----------------------------------------------------------------------
# Check if we have any C++ source files for archive
#----------------------------------------------------------------------
ifneq "$(strip $(ARCHIVE_CXX_SOURCES))" ""
ARCHIVE_OBJECTS +=$(strip $(ARCHIVE_CXX_SOURCES:.cpp=.o))
CXX = $(call cxx_compiler,$(CC))
LD = $(call cxx_linker,$(CC))
endif
#----------------------------------------------------------------------
# Check if we have any ObjC source files for archive
#----------------------------------------------------------------------
ifneq "$(strip $(ARCHIVE_OBJC_SOURCES))" ""
ARCHIVE_OBJECTS +=$(strip $(ARCHIVE_OBJC_SOURCES:.m=.o))
LDFLAGS +=-lobjc
endif
#----------------------------------------------------------------------
# Check if we have any ObjC++ source files for archive
#----------------------------------------------------------------------
ifneq "$(strip $(ARCHIVE_OBJCXX_SOURCES))" ""
ARCHIVE_OBJECTS +=$(strip $(ARCHIVE_OBJCXX_SOURCES:.mm=.o))
CXX = $(call cxx_compiler,$(CC))
LD = $(call cxx_linker,$(CC))
Add a suffix rule for compiling objc++ files and a sample directory under test/lang/objcxx. llvm-svn: 155501
2012-04-25 07:05:07 +08:00
ifeq "$(findstring lobjc,$(LDFLAGS))" ""
rdar://problem/10680957 Need a test case that tests DWARF with .o in .a files test/functionalities/archives: Produces libfoo.a from a.o and b.o. Test breaking inside functions defined inside the libfoo.a BSD Archive. test/make/makefile.rules: Some additional rules to sepcify archive building. For example: ARCHIVE_NAME := libfoo.a ARCHIVE_C_SOURCES := a.c b.c llvm-svn: 148066
2012-01-13 07:09:42 +08:00
LDFLAGS +=-lobjc
endif
endif
Fix test suite make so that -std=c++11 gets set properly for supported compilers and -std=c++0x gets set only for gcc 4.6 versions. Previously, -std=c++0x was being set for all compilers. llvm-svn: 187080
2013-07-25 05:39:24 +08:00
#----------------------------------------------------------------------
# Check if we are compiling with gcc 4.6
#----------------------------------------------------------------------
Improve test for g++ 4.6 Skip the g++ 4.6 test if we're not going to build any C++ source. If a test has C++ source files we automatically determine which C++ compiler to use based on $CC (for example, clang++ if CC=clang). However, this is not done for tests without C++ source and CXX will be GNU make's default of g++. This produces suprious "g++: not found" errors in testrun output on systems without a gcc/g++. Differential Revision: http://reviews.llvm.org/D10122 llvm-svn: 238603
2015-05-30 03:52:02 +08:00
ifneq "$(strip $(CXX_SOURCES) $(OBJCXX_SOURCES))" ""
ifneq "$(filter g++,$(CXX))" ""
CXXVERSION = $(shell $(CXX) -dumpversion | cut -b 1-3)
Fix test suite make so that -std=c++11 gets set properly for supported compilers and -std=c++0x gets set only for gcc 4.6 versions. Previously, -std=c++0x was being set for all compilers. llvm-svn: 187080
2013-07-25 05:39:24 +08:00
ifeq "$(CXXVERSION)" "4.6"
[lldbsuite] Invoke sed on Windows to determine the cache dir for clang Summary: In order to invoke sed on Windows, we need to quote the command correctly. Since we already have commands which do that, move the definitions at the beginning of the file and then re-use them for each command. Reviewers: aprantl, zturner Subscribers: teemperor, lldb-commits Differential Revision: https://reviews.llvm.org/D54709 llvm-svn: 347243
2018-11-20 02:41:33 +08:00
# GCC 4.6 cannot handle -std=c++11, so replace it with -std=c++0x
# instead. FIXME: remove once GCC version is upgraded.
Revert "Fix tests on Windows." This reverts commit 9b757b6e3946311802972409f38c6cefbea917b3. This seems to cause strange breakages about on Ubuntu. llvm-svn: 280763
2016-09-07 06:40:11 +08:00
override CXXFLAGS := $(subst -std=c++11,-std=c++0x,$(CXXFLAGS))
Fix test suite make so that -std=c++11 gets set properly for supported compilers and -std=c++0x gets set only for gcc 4.6 versions. Previously, -std=c++0x was being set for all compilers. llvm-svn: 187080
2013-07-25 05:39:24 +08:00
endif
endif
Improve test for g++ 4.6 Skip the g++ 4.6 test if we're not going to build any C++ source. If a test has C++ source files we automatically determine which C++ compiler to use based on $CC (for example, clang++ if CC=clang). However, this is not done for tests without C++ source and CXX will be GNU make's default of g++. This produces suprious "g++: not found" errors in testrun output on systems without a gcc/g++. Differential Revision: http://reviews.llvm.org/D10122 llvm-svn: 238603
2015-05-30 03:52:02 +08:00
endif
Makefile refactoring for the test suite. Added a make directory under test, which hosts the Makefile.rules and modified most of the Makefiles under each test case directories to utilize Mekefile.rules. Added a description of 'make' directory into README-TestSuite file. llvm-svn: 111868
2010-08-24 07:56:08 +08:00
Re-landing a cleaned up implementation of r284550 This time it should actually work. The previous implementaiton was not getting the linker or compiler flag set correctly in all the right situations. By moving the check down and basing it of whether or not CXX is set I we can have the logic to add the flags exist only once for the linker and once for the compiler instead of duplicating it. llvm-svn: 284756
2016-10-21 02:01:19 +08:00
ifeq ($(findstring clang, $(CXX)), clang)
[lldbsuite] Invoke sed on Windows to determine the cache dir for clang Summary: In order to invoke sed on Windows, we need to quote the command correctly. Since we already have commands which do that, move the definitions at the beginning of the file and then re-use them for each command. Reviewers: aprantl, zturner Subscribers: teemperor, lldb-commits Differential Revision: https://reviews.llvm.org/D54709 llvm-svn: 347243
2018-11-20 02:41:33 +08:00
CXXFLAGS += --driver-mode=g++
Re-landing a cleaned up implementation of r284550 This time it should actually work. The previous implementaiton was not getting the linker or compiler flag set correctly in all the right situations. By moving the check down and basing it of whether or not CXX is set I we can have the logic to add the flags exist only once for the linker and once for the compiler instead of duplicating it. llvm-svn: 284756
2016-10-21 02:01:19 +08:00
endif
ifneq "$(CXX)" ""
[lldbsuite] Invoke sed on Windows to determine the cache dir for clang Summary: In order to invoke sed on Windows, we need to quote the command correctly. Since we already have commands which do that, move the definitions at the beginning of the file and then re-use them for each command. Reviewers: aprantl, zturner Subscribers: teemperor, lldb-commits Differential Revision: https://reviews.llvm.org/D54709 llvm-svn: 347243
2018-11-20 02:41:33 +08:00
ifeq ($(findstring clang, $(LD)), clang)
LDFLAGS += --driver-mode=g++
endif
Re-landing a cleaned up implementation of r284550 This time it should actually work. The previous implementaiton was not getting the linker or compiler flag set correctly in all the right situations. By moving the check down and basing it of whether or not CXX is set I we can have the logic to add the flags exist only once for the linker and once for the compiler instead of duplicating it. llvm-svn: 284756
2016-10-21 02:01:19 +08:00
endif
Add a CFLAGS_EXTRAS make variable to be able to pass things (like '-DTEST_BLOCK_CAPTURED_VARS') to the compile phase. Plus add a DYLIB_ONLY make variable that can be used to turn off compilation/building of a.out. Example: [16:39:21] johnny:/Volumes/data/lldb/svn/trunk/test/lang/c/global_variables $ make clean rm -rf "a.out" "a.out.dSYM" main.o main.d a.o a.d liba.dylib liba.dylib.dSYM [16:39:24] johnny:/Volumes/data/lldb/svn/trunk/test/lang/c/global_variables $ make DYLIB_ONLY=YES clang -gdwarf-2 -O0 -arch x86_64 -c -o a.o a.c clang -gdwarf-2 -O0 -arch x86_64 a.o -install_name "@executable_path/liba.dylib" -dynamiclib -o "liba.dylib" [16:39:30] johnny:/Volumes/data/lldb/svn/trunk/test/lang/c/global_variables $ llvm-svn: 147821
2012-01-10 08:41:11 +08:00
#----------------------------------------------------------------------
# DYLIB_ONLY variable can be used to skip the building of a.out.
# See the sections below regarding dSYM file as well as the building of
# EXE from all the objects.
#----------------------------------------------------------------------
Makefile refactoring for the test suite. Added a make directory under test, which hosts the Makefile.rules and modified most of the Makefiles under each test case directories to utilize Mekefile.rules. Added a description of 'make' directory into README-TestSuite file. llvm-svn: 111868
2010-08-24 07:56:08 +08:00
#----------------------------------------------------------------------
# Compile the executable from all the objects.
#----------------------------------------------------------------------
Add a CFLAGS_EXTRAS make variable to be able to pass things (like '-DTEST_BLOCK_CAPTURED_VARS') to the compile phase. Plus add a DYLIB_ONLY make variable that can be used to turn off compilation/building of a.out. Example: [16:39:21] johnny:/Volumes/data/lldb/svn/trunk/test/lang/c/global_variables $ make clean rm -rf "a.out" "a.out.dSYM" main.o main.d a.o a.d liba.dylib liba.dylib.dSYM [16:39:24] johnny:/Volumes/data/lldb/svn/trunk/test/lang/c/global_variables $ make DYLIB_ONLY=YES clang -gdwarf-2 -O0 -arch x86_64 -c -o a.o a.c clang -gdwarf-2 -O0 -arch x86_64 a.o -install_name "@executable_path/liba.dylib" -dynamiclib -o "liba.dylib" [16:39:30] johnny:/Volumes/data/lldb/svn/trunk/test/lang/c/global_variables $ llvm-svn: 147821
2012-01-10 08:41:11 +08:00
ifneq "$(DYLIB_NAME)" ""
ifeq "$(DYLIB_ONLY)" ""
rdar://problem/10680957 Need a test case that tests DWARF with .o in .a files test/functionalities/archives: Produces libfoo.a from a.o and b.o. Test breaking inside functions defined inside the libfoo.a BSD Archive. test/make/makefile.rules: Some additional rules to sepcify archive building. For example: ARCHIVE_NAME := libfoo.a ARCHIVE_C_SOURCES := a.c b.c llvm-svn: 148066
2012-01-13 07:09:42 +08:00
$(EXE) : $(OBJECTS) $(ARCHIVE_NAME) $(DYLIB_FILENAME)
Rearranged linker flags for test suite. Some linkers (GNU ld) are picky about library order, so if we import libraries as part of our LDFLAGS then that needs to come after any DYLIB_NAME which might require that library. llvm-svn: 192917
2013-10-18 04:09:33 +08:00
$(LD) $(OBJECTS) $(ARCHIVE_NAME) -L. -l$(DYLIB_NAME) $(LDFLAGS) -o "$(EXE)"
Add a CFLAGS_EXTRAS make variable to be able to pass things (like '-DTEST_BLOCK_CAPTURED_VARS') to the compile phase. Plus add a DYLIB_ONLY make variable that can be used to turn off compilation/building of a.out. Example: [16:39:21] johnny:/Volumes/data/lldb/svn/trunk/test/lang/c/global_variables $ make clean rm -rf "a.out" "a.out.dSYM" main.o main.d a.o a.d liba.dylib liba.dylib.dSYM [16:39:24] johnny:/Volumes/data/lldb/svn/trunk/test/lang/c/global_variables $ make DYLIB_ONLY=YES clang -gdwarf-2 -O0 -arch x86_64 -c -o a.o a.c clang -gdwarf-2 -O0 -arch x86_64 a.o -install_name "@executable_path/liba.dylib" -dynamiclib -o "liba.dylib" [16:39:30] johnny:/Volumes/data/lldb/svn/trunk/test/lang/c/global_variables $ llvm-svn: 147821
2012-01-10 08:41:11 +08:00
else
EXE = $(DYLIB_FILENAME)
endif
else
rdar://problem/10680957 Need a test case that tests DWARF with .o in .a files test/functionalities/archives: Produces libfoo.a from a.o and b.o. Test breaking inside functions defined inside the libfoo.a BSD Archive. test/make/makefile.rules: Some additional rules to sepcify archive building. For example: ARCHIVE_NAME := libfoo.a ARCHIVE_C_SOURCES := a.c b.c llvm-svn: 148066
2012-01-13 07:09:42 +08:00
$(EXE) : $(OBJECTS) $(ARCHIVE_NAME)
Revert "Implement basic DidAttach and DidLaunch for DynamicLoaderWindowsDYLD" This breaks many tests on Windows, which now all fail with an error such as "Unable to read memory at address <xxxxxxxx>". llvm-svn: 347174
2018-11-19 04:48:25 +08:00
$(LD) $(OBJECTS) $(LDFLAGS) $(ARCHIVE_NAME) -o "$(EXE)"
Tiny testsuite tweaks. Don't run the apple simulator tests when targetting a device. Add an include to safe-to-call-func to work around a modules issue with a certain combination of header files. Add rules for Darwin systems to ad-hoc codesign binaries that the testsuite builds. llvm-svn: 344635
2018-10-17 02:14:30 +08:00
ifneq "$(CODESIGN)" ""
$(CODESIGN) -s - "$(EXE)"
endif
rdar://problem/10680957 Need a test case that tests DWARF with .o in .a files test/functionalities/archives: Produces libfoo.a from a.o and b.o. Test breaking inside functions defined inside the libfoo.a BSD Archive. test/make/makefile.rules: Some additional rules to sepcify archive building. For example: ARCHIVE_NAME := libfoo.a ARCHIVE_C_SOURCES := a.c b.c llvm-svn: 148066
2012-01-13 07:09:42 +08:00
endif
Compile the LLDB tests out-of-tree. This patch is the result of a discussion on lldb-dev, see http://lists.llvm.org/pipermail/lldb-dev/2018-January/013111.html for background. For each test (should be eventually: each test configuration) a separate build directory is created and we execute make VPATH=$srcdir/path/to/test -C $builddir/path/to/test -f $srcdir/path/to/test/Makefile -I $srcdir/path/to/test In order to make this work all LLDB tests need to be updated to find the executable in the test build directory, since CWD still points at the test's source directory, which is a requirement for unittest2. Although we have done extensive testing, I'm expecting that this first attempt will break a few bots. Please DO NOT HESITATE TO REVERT this patch in order to get the bots green again. We will likely have to iterate on this some more. Differential Revision: https://reviews.llvm.org/D42281 llvm-svn: 323803
2018-01-31 02:29:16 +08:00
#----------------------------------------------------------------------
# Make the dSYM file from the executable if $(MAKE_DSYM) != "NO"
#----------------------------------------------------------------------
$(DSYM) : $(EXE)
ifeq "$(OS)" "Darwin"
ifneq "$(MAKE_DSYM)" "NO"
"$(DS)" $(DSFLAGS) -o "$(DSYM)" "$(EXE)"
else
endif
else
ifeq "$(SPLIT_DEBUG_SYMBOLS)" "YES"
$(OBJCOPY) --only-keep-debug "$(EXE)" "$(DSYM)"
$(OBJCOPY) --strip-debug --add-gnu-debuglink="$(DSYM)" "$(EXE)" "$(EXE)"
endif
endif
rdar://problem/10680957 Need a test case that tests DWARF with .o in .a files test/functionalities/archives: Produces libfoo.a from a.o and b.o. Test breaking inside functions defined inside the libfoo.a BSD Archive. test/make/makefile.rules: Some additional rules to sepcify archive building. For example: ARCHIVE_NAME := libfoo.a ARCHIVE_C_SOURCES := a.c b.c llvm-svn: 148066
2012-01-13 07:09:42 +08:00
#----------------------------------------------------------------------
# Make the archive
#----------------------------------------------------------------------
ifneq "$(ARCHIVE_NAME)" ""
ifeq "$(OS)" "Darwin"
$(ARCHIVE_NAME) : $(ARCHIVE_OBJECTS)
$(AR) $(ARFLAGS) $(ARCHIVE_NAME) $(ARCHIVE_OBJECTS)
$(RM) $(ARCHIVE_OBJECTS)
else
$(ARCHIVE_NAME) : $(foreach ar_obj,$(ARCHIVE_OBJECTS),$(ARCHIVE_NAME)($(ar_obj)))
endif
Makefile refactoring for the test suite. Added a make directory under test, which hosts the Makefile.rules and modified most of the Makefiles under each test case directories to utilize Mekefile.rules. Added a description of 'make' directory into README-TestSuite file. llvm-svn: 111868
2010-08-24 07:56:08 +08:00
endif
#----------------------------------------------------------------------
# Make the dylib
#----------------------------------------------------------------------
Fix makefiles to build shared library tests on Windows. Abstracted away some POSIX-isms that caused MAKE to issue invalid commands on Windows. Added a new force-include for the test programs so that we can use platform-specific macros. TestSharedLib now builds and cleans up on Windows, though the test still fails some of the expectations. Differential Revision: http://reviews.llvm.org/D8277 Patch by: Adrian McCarthy Issue Tracker: http://llvm.org/pr21727 llvm-svn: 232220
2015-03-14 05:51:11 +08:00
$(DYLIB_OBJECTS) : CFLAGS += -DCOMPILING_LLDB_TEST_DLL
Only throw -fPIC when building a shared library Summary: Update makefiles to specify -fPIC in Makefile.rules and only throw -fPIC when building a shared library. This change is necessary to allow building the lldb tests on Windows where -fPIC is not a valid option. Update a few places to Python 3.x syntax Reviewers: zturner, lldb-commits Reviewed By: zturner Subscribers: stella.stamenova, labath, llvm-commits Differential Revision: https://reviews.llvm.org/D42994 llvm-svn: 324671
2018-02-09 07:10:29 +08:00
ifneq "$(OS)" "Windows_NT"
$(DYLIB_OBJECTS) : CFLAGS += -fPIC
$(DYLIB_OBJECTS) : CXXFLAGS += -fPIC
endif
Add Linux rules to test makefile llvm-svn: 133456
2011-06-21 03:06:04 +08:00
$(DYLIB_FILENAME) : $(DYLIB_OBJECTS)
ifeq "$(OS)" "Darwin"
Update TestLoadUnload to use base Makefile. Summary: The current Makefile scheme only allows one dylib to be specified in each make invocation, so TestLoadUnload had a custom Makefile that's unrelated to the base Makefile.rules. This change uses recursive make invocations to bypass the single dylib restriction. See D11202 for more context. Reviewers: clayborg Subscribers: chaoren, lldb-commits Differential Revision: http://reviews.llvm.org/D11367 llvm-svn: 242813
2015-07-22 01:50:16 +08:00
$(LD) $(DYLIB_OBJECTS) $(LDFLAGS) -install_name "$(DYLIB_EXECUTABLE_PATH)/$(DYLIB_FILENAME)" -dynamiclib -o "$(DYLIB_FILENAME)"
Tiny testsuite tweaks. Don't run the apple simulator tests when targetting a device. Add an include to safe-to-call-func to work around a modules issue with a certain combination of header files. Add rules for Darwin systems to ad-hoc codesign binaries that the testsuite builds. llvm-svn: 344635
2018-10-17 02:14:30 +08:00
ifneq "$(CODESIGN)" ""
$(CODESIGN) -s - "$(DYLIB_FILENAME)"
endif
Compile shared libraries with dSYM files when requested on darwin. Prior to this, we never had dSYM files for shared libraries unless it was a dylib only Makefile. llvm-svn: 164322
2012-09-21 05:43:11 +08:00
ifneq "$(MAKE_DSYM)" "NO"
ifneq "$(DS)" ""
Fixed a makefile rule used by several tests Now quotes dsymutil path, required when running tests where the toolchain is in a path that contains a space llvm-svn: 226695
2015-01-22 03:30:00 +08:00
"$(DS)" $(DSFLAGS) "$(DYLIB_FILENAME)"
Compile shared libraries with dSYM files when requested on darwin. Prior to this, we never had dSYM files for shared libraries unless it was a dylib only Makefile. llvm-svn: 164322
2012-09-21 05:43:11 +08:00
endif
endif
Add Linux rules to test makefile llvm-svn: 133456
2011-06-21 03:06:04 +08:00
else
Revert "Implement basic DidAttach and DidLaunch for DynamicLoaderWindowsDYLD" This breaks many tests on Windows, which now all fail with an error such as "Unable to read memory at address <xxxxxxxx>". llvm-svn: 347174
2018-11-19 04:48:25 +08:00
$(LD) $(DYLIB_OBJECTS) $(LDFLAGS) -shared -o "$(DYLIB_FILENAME)"
Add split symbol support to test makefile & add linux split symbol test case. llvm-svn: 185455
2013-07-03 02:13:13 +08:00
ifeq "$(SPLIT_DEBUG_SYMBOLS)" "YES"
Use objcopy provided next to the compiler on android Differential revision: http://reviews.llvm.org/D8765 llvm-svn: 233908
2015-04-02 19:09:28 +08:00
$(OBJCOPY) --only-keep-debug "$(DYLIB_FILENAME)" "$(DYLIB_FILENAME).debug"
$(OBJCOPY) --strip-debug --add-gnu-debuglink="$(DYLIB_FILENAME).debug" "$(DYLIB_FILENAME)" "$(DYLIB_FILENAME)"
Add split symbol support to test makefile & add linux split symbol test case. llvm-svn: 185455
2013-07-03 02:13:13 +08:00
endif
Add Linux rules to test makefile llvm-svn: 133456
2011-06-21 03:06:04 +08:00
endif
Makefile refactoring for the test suite. Added a make directory under test, which hosts the Makefile.rules and modified most of the Makefiles under each test case directories to utilize Mekefile.rules. Added a description of 'make' directory into README-TestSuite file. llvm-svn: 111868
2010-08-24 07:56:08 +08:00
Adds a test to detect when clang omits specialized generic types from debug information when using precompiled headers and -gmodules. llvm-svn: 266791
2016-04-20 02:20:11 +08:00
#----------------------------------------------------------------------
# Make the precompiled header and compile C++ sources against it
#----------------------------------------------------------------------
#ifneq "$(PCH_OUTPUT)" ""
$(PCH_OUTPUT) : $(PCH_CXX_SOURCE)
Compile the LLDB tests out-of-tree. This patch is the result of a discussion on lldb-dev, see http://lists.llvm.org/pipermail/lldb-dev/2018-January/013111.html for background. For each test (should be eventually: each test configuration) a separate build directory is created and we execute make VPATH=$srcdir/path/to/test -C $builddir/path/to/test -f $srcdir/path/to/test/Makefile -I $srcdir/path/to/test In order to make this work all LLDB tests need to be updated to find the executable in the test build directory, since CWD still points at the test's source directory, which is a requirement for unittest2. Although we have done extensive testing, I'm expecting that this first attempt will break a few bots. Please DO NOT HESITATE TO REVERT this patch in order to get the bots green again. We will likely have to iterate on this some more. Differential Revision: https://reviews.llvm.org/D42281 llvm-svn: 323803
2018-01-31 02:29:16 +08:00
$(CXX) $(CXXFLAGS) -x c++-header -o $@ $<
Adds a test to detect when clang omits specialized generic types from debug information when using precompiled headers and -gmodules. llvm-svn: 266791
2016-04-20 02:20:11 +08:00
%.o : %.cpp $(PCH_OUTPUT)
Add "-gmodules" support to the test suite. This change adds the capability of building test inferiors with the -gmodules flag to enable module debug info support. Windows is excluded per @zturner. Reviewers: granata.enrico, aprantl, zturner, labath Subscribers: zturner, labath, lldb-commits Differential Revision: http://reviews.llvm.org/D19998 llvm-svn: 270848
2016-05-26 21:57:03 +08:00
$(CXX) $(PCHFLAGS) $(CXXFLAGS) -c -o $@ $<
Adds a test to detect when clang omits specialized generic types from debug information when using precompiled headers and -gmodules. llvm-svn: 266791
2016-04-20 02:20:11 +08:00
#endif
Makefile refactoring for the test suite. Added a make directory under test, which hosts the Makefile.rules and modified most of the Makefiles under each test case directories to utilize Mekefile.rules. Added a description of 'make' directory into README-TestSuite file. llvm-svn: 111868
2010-08-24 07:56:08 +08:00
#----------------------------------------------------------------------
# Automatic variables based on items already entered. Below we create
Fix makefiles to build shared library tests on Windows. Abstracted away some POSIX-isms that caused MAKE to issue invalid commands on Windows. Added a new force-include for the test programs so that we can use platform-specific macros. TestSharedLib now builds and cleans up on Windows, though the test still fails some of the expectations. Differential Revision: http://reviews.llvm.org/D8277 Patch by: Adrian McCarthy Issue Tracker: http://llvm.org/pr21727 llvm-svn: 232220
2015-03-14 05:51:11 +08:00
# an object's lists from the list of sources by replacing all entries
Makefile refactoring for the test suite. Added a make directory under test, which hosts the Makefile.rules and modified most of the Makefiles under each test case directories to utilize Mekefile.rules. Added a description of 'make' directory into README-TestSuite file. llvm-svn: 111868
2010-08-24 07:56:08 +08:00
# that end with .c with .o, and we also create a list of prerequisite
# files by replacing all .c files with .d.
#----------------------------------------------------------------------
PREREQS := $(OBJECTS:.o=.d)
Clean up more .dwo files after the tests run llvm-svn: 250896
2015-10-21 20:56:37 +08:00
DWOS := $(OBJECTS:.o=.dwo) $(ARCHIVE_OBJECTS:.o=.dwo)
Generates the .d prerequisite file for dylib as well. llvm-svn: 111920
2010-08-25 00:35:00 +08:00
ifneq "$(DYLIB_NAME)" ""
DYLIB_PREREQS := $(DYLIB_OBJECTS:.o=.d)
Remove the dwo files in the cleanup stage of the tests The dwo files are generated when the tests run with split dwarf info. llvm-svn: 247130
2015-09-09 18:20:30 +08:00
DYLIB_DWOS := $(DYLIB_OBJECTS:.o=.dwo)
Generates the .d prerequisite file for dylib as well. llvm-svn: 111920
2010-08-25 00:35:00 +08:00
endif
Makefile refactoring for the test suite. Added a make directory under test, which hosts the Makefile.rules and modified most of the Makefiles under each test case directories to utilize Mekefile.rules. Added a description of 'make' directory into README-TestSuite file. llvm-svn: 111868
2010-08-24 07:56:08 +08:00
#----------------------------------------------------------------------
# Rule for Generating Prerequisites Automatically using .d files and
# the compiler -MM option. The -M option will list all system headers,
# and the -MM option will list all non-system dependencies.
#----------------------------------------------------------------------
%.d: %.c
Fix makefiles to build shared library tests on Windows. Abstracted away some POSIX-isms that caused MAKE to issue invalid commands on Windows. Added a new force-include for the test programs so that we can use platform-specific macros. TestSharedLib now builds and cleans up on Windows, though the test still fails some of the expectations. Differential Revision: http://reviews.llvm.org/D8277 Patch by: Adrian McCarthy Issue Tracker: http://llvm.org/pr21727 llvm-svn: 232220
2015-03-14 05:51:11 +08:00
@rm -f $@ $(JOIN_CMD) \
Clean up dependency .d.$$$$ files for tests Summary: Mac-only tests were leaving .d.$$$$ dependency files left in the test tree. This happened because: 1) "make clean" was invoked although no tests in the folder were run 2) The Makefile had main.d as a dependency, which meant it tried to compile the source file (to extract dependencies). 3) The compile failed (does not compile on linux) and left behind a main.d.$$$$ temporary file. 4) "make clean" tried to clean up these temporary files, but the expansion $(wildcard *.d.[0-9]*) was performed before the temporary file was created, so this file was not caught. I fix this by giving all the temporary files deterministic names, which makes it easier to clean them up afterwards. I also make the rules for generating the dependency files more robust and less likely to leak files in the first place. Reviewers: vharron, zturner Subscribers: lldb-commits Differential Revision: http://reviews.llvm.org/D7406 llvm-svn: 228285
2015-02-05 17:52:42 +08:00
$(CC) -M $(CFLAGS) $< > $@.tmp && \
Fix makefiles to build shared library tests on Windows. Abstracted away some POSIX-isms that caused MAKE to issue invalid commands on Windows. Added a new force-include for the test programs so that we can use platform-specific macros. TestSharedLib now builds and cleans up on Windows, though the test still fails some of the expectations. Differential Revision: http://reviews.llvm.org/D8277 Patch by: Adrian McCarthy Issue Tracker: http://llvm.org/pr21727 llvm-svn: 232220
2015-03-14 05:51:11 +08:00
sed $(QUOTE)s,\($*\)\.o[ :]*,\1.o $@ : ,g$(QUOTE) < $@.tmp > $@ $(JOIN_CMD) \
Clean up dependency .d.$$$$ files for tests Summary: Mac-only tests were leaving .d.$$$$ dependency files left in the test tree. This happened because: 1) "make clean" was invoked although no tests in the folder were run 2) The Makefile had main.d as a dependency, which meant it tried to compile the source file (to extract dependencies). 3) The compile failed (does not compile on linux) and left behind a main.d.$$$$ temporary file. 4) "make clean" tried to clean up these temporary files, but the expansion $(wildcard *.d.[0-9]*) was performed before the temporary file was created, so this file was not caught. I fix this by giving all the temporary files deterministic names, which makes it easier to clean them up afterwards. I also make the rules for generating the dependency files more robust and less likely to leak files in the first place. Reviewers: vharron, zturner Subscribers: lldb-commits Differential Revision: http://reviews.llvm.org/D7406 llvm-svn: 228285
2015-02-05 17:52:42 +08:00
rm -f $@.tmp
Makefile refactoring for the test suite. Added a make directory under test, which hosts the Makefile.rules and modified most of the Makefiles under each test case directories to utilize Mekefile.rules. Added a description of 'make' directory into README-TestSuite file. llvm-svn: 111868
2010-08-24 07:56:08 +08:00
%.d: %.cpp
Fix makefiles to build shared library tests on Windows. Abstracted away some POSIX-isms that caused MAKE to issue invalid commands on Windows. Added a new force-include for the test programs so that we can use platform-specific macros. TestSharedLib now builds and cleans up on Windows, though the test still fails some of the expectations. Differential Revision: http://reviews.llvm.org/D8277 Patch by: Adrian McCarthy Issue Tracker: http://llvm.org/pr21727 llvm-svn: 232220
2015-03-14 05:51:11 +08:00
@rm -f $@ $(JOIN_CMD) \
Clean up dependency .d.$$$$ files for tests Summary: Mac-only tests were leaving .d.$$$$ dependency files left in the test tree. This happened because: 1) "make clean" was invoked although no tests in the folder were run 2) The Makefile had main.d as a dependency, which meant it tried to compile the source file (to extract dependencies). 3) The compile failed (does not compile on linux) and left behind a main.d.$$$$ temporary file. 4) "make clean" tried to clean up these temporary files, but the expansion $(wildcard *.d.[0-9]*) was performed before the temporary file was created, so this file was not caught. I fix this by giving all the temporary files deterministic names, which makes it easier to clean them up afterwards. I also make the rules for generating the dependency files more robust and less likely to leak files in the first place. Reviewers: vharron, zturner Subscribers: lldb-commits Differential Revision: http://reviews.llvm.org/D7406 llvm-svn: 228285
2015-02-05 17:52:42 +08:00
$(CXX) -M $(CXXFLAGS) $< > $@.tmp && \
Fix makefiles to build shared library tests on Windows. Abstracted away some POSIX-isms that caused MAKE to issue invalid commands on Windows. Added a new force-include for the test programs so that we can use platform-specific macros. TestSharedLib now builds and cleans up on Windows, though the test still fails some of the expectations. Differential Revision: http://reviews.llvm.org/D8277 Patch by: Adrian McCarthy Issue Tracker: http://llvm.org/pr21727 llvm-svn: 232220
2015-03-14 05:51:11 +08:00
sed $(QUOTE)s,\($*\)\.o[ :]*,\1.o $@ : ,g$(QUOTE) < $@.tmp > $@ $(JOIN_CMD) \
Clean up dependency .d.$$$$ files for tests Summary: Mac-only tests were leaving .d.$$$$ dependency files left in the test tree. This happened because: 1) "make clean" was invoked although no tests in the folder were run 2) The Makefile had main.d as a dependency, which meant it tried to compile the source file (to extract dependencies). 3) The compile failed (does not compile on linux) and left behind a main.d.$$$$ temporary file. 4) "make clean" tried to clean up these temporary files, but the expansion $(wildcard *.d.[0-9]*) was performed before the temporary file was created, so this file was not caught. I fix this by giving all the temporary files deterministic names, which makes it easier to clean them up afterwards. I also make the rules for generating the dependency files more robust and less likely to leak files in the first place. Reviewers: vharron, zturner Subscribers: lldb-commits Differential Revision: http://reviews.llvm.org/D7406 llvm-svn: 228285
2015-02-05 17:52:42 +08:00
rm -f $@.tmp
Makefile refactoring for the test suite. Added a make directory under test, which hosts the Makefile.rules and modified most of the Makefiles under each test case directories to utilize Mekefile.rules. Added a description of 'make' directory into README-TestSuite file. llvm-svn: 111868
2010-08-24 07:56:08 +08:00
%.d: %.m
Fix makefiles to build shared library tests on Windows. Abstracted away some POSIX-isms that caused MAKE to issue invalid commands on Windows. Added a new force-include for the test programs so that we can use platform-specific macros. TestSharedLib now builds and cleans up on Windows, though the test still fails some of the expectations. Differential Revision: http://reviews.llvm.org/D8277 Patch by: Adrian McCarthy Issue Tracker: http://llvm.org/pr21727 llvm-svn: 232220
2015-03-14 05:51:11 +08:00
@rm -f $@ $(JOIN_CMD) \
Clean up dependency .d.$$$$ files for tests Summary: Mac-only tests were leaving .d.$$$$ dependency files left in the test tree. This happened because: 1) "make clean" was invoked although no tests in the folder were run 2) The Makefile had main.d as a dependency, which meant it tried to compile the source file (to extract dependencies). 3) The compile failed (does not compile on linux) and left behind a main.d.$$$$ temporary file. 4) "make clean" tried to clean up these temporary files, but the expansion $(wildcard *.d.[0-9]*) was performed before the temporary file was created, so this file was not caught. I fix this by giving all the temporary files deterministic names, which makes it easier to clean them up afterwards. I also make the rules for generating the dependency files more robust and less likely to leak files in the first place. Reviewers: vharron, zturner Subscribers: lldb-commits Differential Revision: http://reviews.llvm.org/D7406 llvm-svn: 228285
2015-02-05 17:52:42 +08:00
$(CC) -M $(CFLAGS) $< > $@.tmp && \
Fix makefiles to build shared library tests on Windows. Abstracted away some POSIX-isms that caused MAKE to issue invalid commands on Windows. Added a new force-include for the test programs so that we can use platform-specific macros. TestSharedLib now builds and cleans up on Windows, though the test still fails some of the expectations. Differential Revision: http://reviews.llvm.org/D8277 Patch by: Adrian McCarthy Issue Tracker: http://llvm.org/pr21727 llvm-svn: 232220
2015-03-14 05:51:11 +08:00
sed $(QUOTE)s,\($*\)\.o[ :]*,\1.o $@ : ,g$(QUOTE) < $@.tmp > $@ $(JOIN_CMD) \
Clean up dependency .d.$$$$ files for tests Summary: Mac-only tests were leaving .d.$$$$ dependency files left in the test tree. This happened because: 1) "make clean" was invoked although no tests in the folder were run 2) The Makefile had main.d as a dependency, which meant it tried to compile the source file (to extract dependencies). 3) The compile failed (does not compile on linux) and left behind a main.d.$$$$ temporary file. 4) "make clean" tried to clean up these temporary files, but the expansion $(wildcard *.d.[0-9]*) was performed before the temporary file was created, so this file was not caught. I fix this by giving all the temporary files deterministic names, which makes it easier to clean them up afterwards. I also make the rules for generating the dependency files more robust and less likely to leak files in the first place. Reviewers: vharron, zturner Subscribers: lldb-commits Differential Revision: http://reviews.llvm.org/D7406 llvm-svn: 228285
2015-02-05 17:52:42 +08:00
rm -f $@.tmp
Makefile refactoring for the test suite. Added a make directory under test, which hosts the Makefile.rules and modified most of the Makefiles under each test case directories to utilize Mekefile.rules. Added a description of 'make' directory into README-TestSuite file. llvm-svn: 111868
2010-08-24 07:56:08 +08:00
%.d: %.mm
Fix makefiles to build shared library tests on Windows. Abstracted away some POSIX-isms that caused MAKE to issue invalid commands on Windows. Added a new force-include for the test programs so that we can use platform-specific macros. TestSharedLib now builds and cleans up on Windows, though the test still fails some of the expectations. Differential Revision: http://reviews.llvm.org/D8277 Patch by: Adrian McCarthy Issue Tracker: http://llvm.org/pr21727 llvm-svn: 232220
2015-03-14 05:51:11 +08:00
@rm -f $@ $(JOIN_CMD) \
Clean up dependency .d.$$$$ files for tests Summary: Mac-only tests were leaving .d.$$$$ dependency files left in the test tree. This happened because: 1) "make clean" was invoked although no tests in the folder were run 2) The Makefile had main.d as a dependency, which meant it tried to compile the source file (to extract dependencies). 3) The compile failed (does not compile on linux) and left behind a main.d.$$$$ temporary file. 4) "make clean" tried to clean up these temporary files, but the expansion $(wildcard *.d.[0-9]*) was performed before the temporary file was created, so this file was not caught. I fix this by giving all the temporary files deterministic names, which makes it easier to clean them up afterwards. I also make the rules for generating the dependency files more robust and less likely to leak files in the first place. Reviewers: vharron, zturner Subscribers: lldb-commits Differential Revision: http://reviews.llvm.org/D7406 llvm-svn: 228285
2015-02-05 17:52:42 +08:00
$(CXX) -M $(CXXFLAGS) $< > $@.tmp && \
Fix makefiles to build shared library tests on Windows. Abstracted away some POSIX-isms that caused MAKE to issue invalid commands on Windows. Added a new force-include for the test programs so that we can use platform-specific macros. TestSharedLib now builds and cleans up on Windows, though the test still fails some of the expectations. Differential Revision: http://reviews.llvm.org/D8277 Patch by: Adrian McCarthy Issue Tracker: http://llvm.org/pr21727 llvm-svn: 232220
2015-03-14 05:51:11 +08:00
sed $(QUOTE)s,\($*\)\.o[ :]*,\1.o $@ : ,g$(QUOTE) < $@.tmp > $@ $(JOIN_CMD) \
Clean up dependency .d.$$$$ files for tests Summary: Mac-only tests were leaving .d.$$$$ dependency files left in the test tree. This happened because: 1) "make clean" was invoked although no tests in the folder were run 2) The Makefile had main.d as a dependency, which meant it tried to compile the source file (to extract dependencies). 3) The compile failed (does not compile on linux) and left behind a main.d.$$$$ temporary file. 4) "make clean" tried to clean up these temporary files, but the expansion $(wildcard *.d.[0-9]*) was performed before the temporary file was created, so this file was not caught. I fix this by giving all the temporary files deterministic names, which makes it easier to clean them up afterwards. I also make the rules for generating the dependency files more robust and less likely to leak files in the first place. Reviewers: vharron, zturner Subscribers: lldb-commits Differential Revision: http://reviews.llvm.org/D7406 llvm-svn: 228285
2015-02-05 17:52:42 +08:00
rm -f $@.tmp
Makefile refactoring for the test suite. Added a make directory under test, which hosts the Makefile.rules and modified most of the Makefiles under each test case directories to utilize Mekefile.rules. Added a description of 'make' directory into README-TestSuite file. llvm-svn: 111868
2010-08-24 07:56:08 +08:00
#----------------------------------------------------------------------
# Include all of the makefiles for each source file so we don't have
# to manually track all of the prerequisites for each source file.
#----------------------------------------------------------------------
sinclude $(PREREQS)
Generates the .d prerequisite file for dylib as well. llvm-svn: 111920
2010-08-25 00:35:00 +08:00
ifneq "$(DYLIB_NAME)" ""
sinclude $(DYLIB_PREREQS)
endif
Makefile refactoring for the test suite. Added a make directory under test, which hosts the Makefile.rules and modified most of the Makefiles under each test case directories to utilize Mekefile.rules. Added a description of 'make' directory into README-TestSuite file. llvm-svn: 111868
2010-08-24 07:56:08 +08:00
Add a suffix rule for compiling objc++ files and a sample directory under test/lang/objcxx. llvm-svn: 155501
2012-04-25 07:05:07 +08:00
# Define a suffix rule for .mm -> .o
.SUFFIXES: .mm .o
.mm.o:
$(CXX) $(CXXFLAGS) -c $<
Makefile refactoring for the test suite. Added a make directory under test, which hosts the Makefile.rules and modified most of the Makefiles under each test case directories to utilize Mekefile.rules. Added a description of 'make' directory into README-TestSuite file. llvm-svn: 111868
2010-08-24 07:56:08 +08:00
.PHONY: clean
dsym: $(DSYM)
all: $(EXE) $(DSYM)
Added "long long" and "unsigned long long" to the TestBasicTypes.py. Added a special "clean" target to the types/Makefile to clean up all the *.o/.d files. The generic_type_tester() method is modified to take a set of atoms, instead of type string as a required parameter, for example: o unsigned int => set(['unsigned', 'int']) o unsigned long long => set(['unsigned', 'long long']) o long long => set(['long long']) llvm-svn: 114871
2010-09-28 04:44:46 +08:00
clean::
Use test-specific module caches to avoid stale header conflicts Stale global module caches cause problems for the bots. The modules become invalid when clang headers are updated by version control, and tests which use these modules fail to compile, e.g: fatal error: file '.../__stddef_max_align_t.h' has been modified since the module file '/var/.../Darwin.pcm' was built note: please rebuild precompiled header '/var/.../Darwin.pcm' Eventually we should transition to having just a single module cache to speed tests up. This patch should be just enough to fix the spurious bot failures due to stale caches. rdar://36479805, also related to llvm.org/PR36048 Differential Revision: https://reviews.llvm.org/D42277 llvm-svn: 323450
2018-01-26 02:01:27 +08:00
$(RM) -rf $(OBJECTS) $(PREREQS) $(PREREQS:.d=.d.tmp) $(DWOS) $(ARCHIVE_NAME) $(ARCHIVE_OBJECTS) $(CLANG_MODULE_CACHE_DIR)
Fix test 'make clean' target for empty $(DSYM) on FreeBSD A freebsd issue with rm prevents '[g]make clean' from working if $(DSYM) is empty (fts_open(3) fails if passed an empty argument). To work around this, simplify the clean target by using three separate rm invocations: one for the common files, one for the case of non-empty $(DYLIB_NAME), and one for non-empty $(DSYM). Issue diagnosed (and reported to FreeBSD) by John Wolfe. llvm.org/pr17933 llvm-svn: 203253
2014-03-08 01:20:50 +08:00
ifneq "$(DYLIB_NAME)" ""
Need to use rm -rf on dSYM bundle directories. llvm-svn: 203332
2014-03-08 09:53:27 +08:00
$(RM) -r $(DYLIB_FILENAME).dSYM
Remove the dwo files in the cleanup stage of the tests The dwo files are generated when the tests run with split dwarf info. llvm-svn: 247130
2015-09-09 18:20:30 +08:00
$(RM) $(DYLIB_OBJECTS) $(DYLIB_PREREQS) $(DYLIB_PREREQS:.d=.d.tmp) $(DYLIB_DWOS) $(DYLIB_FILENAME) $(DYLIB_FILENAME).debug
Fix test 'make clean' target for empty $(DSYM) on FreeBSD A freebsd issue with rm prevents '[g]make clean' from working if $(DSYM) is empty (fts_open(3) fails if passed an empty argument). To work around this, simplify the clean target by using three separate rm invocations: one for the common files, one for the case of non-empty $(DYLIB_NAME), and one for non-empty $(DSYM). Issue diagnosed (and reported to FreeBSD) by John Wolfe. llvm.org/pr17933 llvm-svn: 203253
2014-03-08 01:20:50 +08:00
endif
Adds a test to detect when clang omits specialized generic types from debug information when using precompiled headers and -gmodules. llvm-svn: 266791
2016-04-20 02:20:11 +08:00
ifneq "$(PCH_OUTPUT)" ""
$(RM) $(PCH_OUTPUT)
endif
Fix test 'make clean' target for empty $(DSYM) on FreeBSD A freebsd issue with rm prevents '[g]make clean' from working if $(DSYM) is empty (fts_open(3) fails if passed an empty argument). To work around this, simplify the clean target by using three separate rm invocations: one for the common files, one for the case of non-empty $(DYLIB_NAME), and one for non-empty $(DSYM). Issue diagnosed (and reported to FreeBSD) by John Wolfe. llvm.org/pr17933 llvm-svn: 203253
2014-03-08 01:20:50 +08:00
ifneq "$(DSYM)" ""
Need to use rm -rf on dSYM bundle directories. llvm-svn: 203332
2014-03-08 09:53:27 +08:00
$(RM) -r "$(DSYM)"
Makefile refactoring for the test suite. Added a make directory under test, which hosts the Makefile.rules and modified most of the Makefiles under each test case directories to utilize Mekefile.rules. Added a description of 'make' directory into README-TestSuite file. llvm-svn: 111868
2010-08-24 07:56:08 +08:00
endif
Delete MSVC intermediate files on "make clean" from tests. lld-link shells out to MSVC for certain types of work, and this results in some MSVC output files being generated even though clang / lld are the compiler / linker. This is expected, so we make sure to clean these output files on make clean. llvm-svn: 224345
2014-12-17 00:48:19 +08:00
ifeq "$(OS)" "Windows_NT"
On Windows, use 'del' instead of 'rm' to delete the test executable. This is a nasty hack to work around the issue described in https://llvm.org/pr24589 llvm-svn: 246062
2015-08-27 03:44:45 +08:00
# http://llvm.org/pr24589
IF EXIST "$(EXE)" del "$(EXE)"
Tear down tests in reverse order from setting them up. Tests derive from TestBase, which derives from Base. In the test setUp() methods, we always call TestBase.setUp() first and then call implementation-specific setup. Tear down needs to do the reverse. This was causing over 20 failures on Windows, and was the culprit behind about 80% of the files not being cleaned up after test run. TestBase.tearDown() is responsible for deleting all targets created during the test run and without this step, on Windows files will be locked and cannot be deleted. But TestBase.tearDown() was calling Base.tearDown() before its own cleanup (i.e. deleting the targets) and in some cases one of the teardown hooks would be to call make clean. So make clean would be run before the targets had been deleted, and fail to remove the files, and subsequently result in a failed test as well. llvm-svn: 233284
2015-03-27 00:43:25 +08:00
$(RM) $(wildcard *.manifest *.pdb *.ilk)
On Windows, use 'del' instead of 'rm' to delete the test executable. This is a nasty hack to work around the issue described in https://llvm.org/pr24589 llvm-svn: 246062
2015-08-27 03:44:45 +08:00
ifneq "$(DYLIB_NAME)" ""
Tear down tests in reverse order from setting them up. Tests derive from TestBase, which derives from Base. In the test setUp() methods, we always call TestBase.setUp() first and then call implementation-specific setup. Tear down needs to do the reverse. This was causing over 20 failures on Windows, and was the culprit behind about 80% of the files not being cleaned up after test run. TestBase.tearDown() is responsible for deleting all targets created during the test run and without this step, on Windows files will be locked and cannot be deleted. But TestBase.tearDown() was calling Base.tearDown() before its own cleanup (i.e. deleting the targets) and in some cases one of the teardown hooks would be to call make clean. So make clean would be run before the targets had been deleted, and fail to remove the files, and subsequently result in a failed test as well. llvm-svn: 233284
2015-03-27 00:43:25 +08:00
$(RM) $(DYLIB_NAME).lib $(DYLIB_NAME).exp
On Windows, use 'del' instead of 'rm' to delete the test executable. This is a nasty hack to work around the issue described in https://llvm.org/pr24589 llvm-svn: 246062
2015-08-27 03:44:45 +08:00
endif
else
$(RM) "$(EXE)"
Delete MSVC intermediate files on "make clean" from tests. lld-link shells out to MSVC for certain types of work, and this results in some MSVC output files being generated even though clang / lld are the compiler / linker. This is expected, so we make sure to clean these output files on make clean. llvm-svn: 224345
2014-12-17 00:48:19 +08:00
endif
Add makefile debugging rule for printing out the value of a variable. From http://blog.melski.net/tag/debugging-makefiles/. Example: [13:14:59] johnny:/Volumes/data/lldb/svn/trunk/test/class_static $ make print-CC CC=gcc origin = file flavor = recursive value = gcc [13:15:09] johnny:/Volumes/data/lldb/svn/trunk/test/class_static $ make print-LD LD= g++ origin = file flavor = recursive value = $(call cxx_linker,$(CC)) [13:15:21] johnny:/Volumes/data/lldb/svn/trunk/test/class_static $ make print-CXX CXX= g++ origin = file flavor = recursive value = $(call cxx_compiler,$(CC)) [13:15:29] johnny:/Volumes/data/lldb/svn/trunk/test/class_static $ llvm-svn: 123469
2011-01-15 05:18:12 +08:00
#----------------------------------------------------------------------
# From http://blog.melski.net/tag/debugging-makefiles/
[dotest] Use in-tree dsymutil on Darwin Summary: With the upstream implementation of dsymutil containing almost all functionality from the one shipped with Xcode, we want to use the in-tree version for running the test suite. This will also allow us to re-enable TestUnicodeSymbols which was failing because of the discrepancy in how Unicode symbols were hashed in lldb and older versions of dsymutil. Reviewers: aprantl, davide, jingham, labath Subscribers: mgorny, llvm-commits, lldb-commits Differential Revision: https://reviews.llvm.org/D45518 llvm-svn: 329889
2018-04-12 17:25:32 +08:00
#
Add makefile debugging rule for printing out the value of a variable. From http://blog.melski.net/tag/debugging-makefiles/. Example: [13:14:59] johnny:/Volumes/data/lldb/svn/trunk/test/class_static $ make print-CC CC=gcc origin = file flavor = recursive value = gcc [13:15:09] johnny:/Volumes/data/lldb/svn/trunk/test/class_static $ make print-LD LD= g++ origin = file flavor = recursive value = $(call cxx_linker,$(CC)) [13:15:21] johnny:/Volumes/data/lldb/svn/trunk/test/class_static $ make print-CXX CXX= g++ origin = file flavor = recursive value = $(call cxx_compiler,$(CC)) [13:15:29] johnny:/Volumes/data/lldb/svn/trunk/test/class_static $ llvm-svn: 123469
2011-01-15 05:18:12 +08:00
# Usage: make print-CC print-CXX print-LD
#----------------------------------------------------------------------
print-%:
@echo '$*=$($*)'
@echo ' origin = $(origin $*)'
@echo ' flavor = $(flavor $*)'
@echo ' value = $(value $*)'
Minor comment change. llvm-svn: 124488
2011-01-29 01:22:29 +08:00
### Local Variables: ###
### mode:makefile ###
### End: ###