summaryrefslogtreecommitdiff
path: root/mk/project.mk.in
diff options
context:
space:
mode:
authorDavid M Peixotto <dmp@rice.edu>2011-06-28 15:38:32 -0500
committerDavid M Peixotto <dmp@rice.edu>2011-10-07 16:48:34 -0500
commit6247b59e5d31de58ee51273916bc44ac2118240a (patch)
tree10ce216966c64b2e45373cd9ceb45e7d27f3f766 /mk/project.mk.in
parentdba7254566b121408e7167200d0223a531b66e8b (diff)
downloadhaskell-6247b59e5d31de58ee51273916bc44ac2118240a.tar.gz
Add autoconf support to detect an LLVM-based C compiler
This patch adds support to the autoconf scripts to detect when we are using a C compiler that uses an LLVM back end. An LLVM back end does not support all of the extensions use by GCC, so we need to perform some conditional compilation in the runtime, particularly for handling thread local storage and global register variables. The changes here will set the CC_LLVM_BACKEND in the autoconf scripts if we detect an llvm-based compiler. We use this variable to define the llvm_CC_FLAVOR variable that we can use in the runtime code to conditionally compile for LLVM.
Diffstat (limited to 'mk/project.mk.in')
-rw-r--r--mk/project.mk.in3
1 files changed, 3 insertions, 0 deletions
diff --git a/mk/project.mk.in b/mk/project.mk.in
index 58b0f1a028..3625124f75 100644
--- a/mk/project.mk.in
+++ b/mk/project.mk.in
@@ -143,3 +143,6 @@ OSTYPE=@OSTYPE@
# In case of Solaris OS, does it provide broken shared libs
# linker or not?
SOLARIS_BROKEN_SHLD=@SOLARIS_BROKEN_SHLD@
+
+# Do we have a C compiler using an LLVM back end?
+CC_LLVM_BACKEND = @CC_LLVM_BACKEND@