summaryrefslogtreecommitdiffstats
path: root/lib/clang/clang.build.mk
Commit message (Collapse)AuthorAgeFilesLines
...
* Upgrade our copy of llvm/clang to trunk r162107. With thanks todim2012-08-201-6/+10
| | | | Benjamin Kramer and Joerg Sonnenberger for their input and fixes.
* Upgrade our copy of llvm/clang to r155985, from upstream's release_31dim2012-05-031-3/+1
| | | | | | | branch. This brings us very close to the 3.1 release, which is planned for May 14th. MFC after: 2 weeks
* Revert r234356 for now, as it leads to run-time problems on 32-bitdim2012-04-231-6/+0
| | | | | | | PowerPC. Note this will break world. Reported by: andreast Pointy hat to: dim
* Work around an issue on 32-bit PowerPC, where clang executable can getdim2012-04-161-0/+6
| | | | | | too big, causing 'relocation truncated to fit' errors at link time. Reviewed by: nwhitehorn
* Upgrade our copy of llvm/clang to trunk r154661, in preparation of thedim2012-04-161-2/+17
| | | | | | | upcoming 3.1 release (expected in a few weeks). Preliminary release notes can be found at: <http://llvm.org/docs/ReleaseNotes.html> MFC after: 2 weeks
* Instead of forcing -O1 on PowerPC for LLVM and clang, fix the actualnwhitehorn2012-01-011-4/+2
| | | | | | | | problem by adding -fno-strict-aliasing to CFLAGS. Since this is a global issue that just happened to manifest on PowerPC, add this to CFLAGS unconditionally. MFC after: 1 week
* Connect LLVM/clang to the build on powerpc64. After the binutils 2.17.50nwhitehorn2011-11-211-1/+1
| | | | import, it works without issue.
* Upgrade our copy of llvm/clang to r142614, from upstream's release_30dim2011-10-221-20/+22
| | | | | | | branch. This brings us very close to the 3.0 release, which is expected in a week or two. MFC after: 1 week
* Update llvm/clang's target triple (confusingly named LLVM_HOSTTRIPLE) todim2011-10-171-2/+1
| | | | $arch-unknown-freebsd10.0.
* Upgrade our copy of llvm/clang to r135360, from upstream's trunk.dim2011-07-171-35/+54
|
* On amd64, change clang's default triple to 'x86_64-unknown-freebsd9.0',dim2011-05-221-1/+1
| | | | | | | | | | | | | | | | similar to what we do for binutils. When clang's default triple starts with 'amd64-', it does not pass a proper -target-cpu option to its first stage. This can lead to problems, for example when structs are memcpy'd, and clang erroneously assumes they are 16-byte aligned. It will then use the 'movaps' SSE instruction to implement the copy, which results in a bus error if the struct is really 8-byte aligned. I encountered this issue when gcc's /usr/libexec/cc1 started crashing with SIGBUS, after rebuilding world with clang ToT, but it also affects the version of clang that we have in the tree. We were just lucky until now, apparently. :)
* Upgrade our copy of llvm/clang to r130700, from upstream's trunk.dim2011-05-021-6/+11
|
* Upgrade our copy of llvm/clang to r126079, from upstream's trunk.dim2011-02-201-33/+33
| | | | | This contains many improvements, primarily better C++ support, an integrated assembler for x86 and support for -pg.
* Don't use -fno-exceptions or -fno-rtti for .c files, when buildingdim2010-11-141-2/+2
| | | | llvm/clang.
* Upgrade our Clang in base to r114020, from upstream's release_28 branch.dim2010-09-201-1/+15
| | | | Approved-by: rpaulo (mentor)
* Modify clang so that when TOOLS_PREFIX is defined we register therpaulo2010-08-211-0/+4
| | | | | | | | CLANG_PREFIX macro. This changes the default header search path when we are building clang as part of cross-tools. Submitted by: Dimitry Andric <dimitry at andric.com> Reviewed by: freebsd-current
* Build clang libraries by default with -fno-exceptions and withrpaulo2010-07-221-0/+11
| | | | | | | | | -fno-rtti. The clang libaries that really use exceptions and virtual functions can enable LLVM_REQUIRES_EH and LLVM_REQUIRES_RTTI respectively. This saves space on the resulting binaries and follows what's being done upstream. Submitted by: Dimitry Andric <dimitry at andric.com>
* Upgrade our Clang in base to r108428.ed2010-07-201-11/+27
| | | | | | | | | This commit merges the latest LLVM sources from the vendor space. It also updates the build glue to match the new sources. Clang's version number is changed to match LLVM's, which means /usr/include/clang/2.0 has been renamed to /usr/include/clang/2.8. Obtained from: projects/clangbsd
* Remove unneeded files from the build.ed2010-06-151-1/+1
| | | | | | | | | | | | | | | I used the following command to determine which source files were unneeded: | for i in `find lib/clang -name '*.o'` | do | MATCHES="`(nm -g --defined-only $i; nm -g --defined-only \ | usr.bin/clang/clang/clang) | sed -e 's/.* //' | \ | sort | uniq -d | wc -l`" | [ $MATCHES -eq 0 ] && echo "$i: unneeded" | done This should slightly improve the build times.
* Unbreak Clang on PowerPC.ed2010-06-141-1/+6
| | | | | | | | It seems GCC 4.2.1 on PowerPC miscompiles Clang, causing it to crash when building even simple Hello World applications. Switch back to -O1 for this architecture. Submitted by: nwhitehorn
* Disable usage of posix_spawn() inside LLVM.ed2010-06-131-1/+1
| | | | | | | | | Even though it's nice to use posix_spawn() instead of manually using fork()/exec(), it's better to disable this. FreeBSD 7 doesn't support this interface. When enabled, we can't build tblgen, which prevents us from building FreeBSD 9 on 7. Tested by: raj
* Do the branding right this time.ed2010-06-121-1/+2
| | | | | | | | | I've looked at other places in the source tree where CLANG_VENDOR is used and I suspect it might not be safe to use newlines here. CLANG_VENDOR should just be defined to "FreeBSD ", just like the latest Clang preview in OS X uses "Apple ". Properly use SVN_REVISION to define it to the imported revision of Clang. I do want to have a date in there, so slightly modify the code to support CLANG_VENDOR_SUFFIX.
* Brand our Clang binary.ed2010-06-101-1/+2
| | | | | That way it's easier for the Clang folks to keep track of what we're doing.
* Import the build makefiles for clang/LLVM.rdivacky2010-06-091-0/+73
Approved by: ed (mentor)
OpenPOWER on IntegriCloud