summaryrefslogtreecommitdiffstats
path: root/lib/clang
Commit message (Collapse)AuthorAgeFilesLines
* Use the correct upstream revision number for llvm/clang 3.0 release.dim2011-12-101-2/+2
| | | | | | | The r145546 revision is from branches/release_30, the r145349 revision is from tags/RELEASE_30/final. MFC after: 1 week
* Upgrade our copy of llvm/clang to 3.0 release. Release notes can bedim2011-12-093-2/+5
| | | | | | found at: http://llvm.org/releases/3.0/docs/ReleaseNotes.html 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.
* Revert r227538, since it doesn't compile with clang at all (it doesn'tdim2011-11-172-6/+2
| | | | | | | | | | | allow the built-in operations to be redefined, at least not without excessive force). Instead, just disable LLVM's support for atomic operations for now. Nothing in either clang or the tablegen tools currently depends on it. This still allows users of head built before r198344 to upgrade to top-of-head seamlessly.
* When one attempts to compile the tree with -march=i386, which also useddim2011-11-062-0/+4
| | | | | | | | | | | to be gcc's default before r198344, calls to atomic builtins will not be expanded inline. Instead, they will be generated as calls to external functions (e.g. __sync_fetch_and_add_N), leading to linking errors later on. Put in a seatbelt that disables use of atomic builtins in libstdc++ and llvm, when tuning specifically for the real i386 CPU. This does not protect against all possible issues, but it is better than nothing.
* Upgrade our copy of llvm/clang to r142614, from upstream's release_30dim2011-10-2237-88/+150
| | | | | | | 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-1761-128/+228
|
* Upgrade our copy of llvm/clang to r132879, from upstream's trunk.dim2011-06-126-5/+7
|
* 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-0225-36/+81
|
* Update llvm/clang to trunk r126547.dim2011-02-273-3/+4
| | | | | | | | | | | | | | There are several bugfixes in this update, but the most important one is to ensure __start_ and __stop_ symbols for linker sets and kernel module metadata are always emitted in object files: http://llvm.org/bugs/show_bug.cgi?id=9292 Before this fix, if you compiled kernel modules with clang, they would not be properly processed by kldxref, and if they had any dependencies, the kernel would fail to load those. Another problem occurred when attempting to mount a tmpfs filesystem, which would result in 'operation not supported by device'.
* Instead of defining LLVM_MULTITHREADED as 0 or 1, define or undefine it,dim2011-02-272-2/+2
| | | | | and test appropriately. Otherwise it might erroneously pick up some pthread primitives, and fail to link.
* Update llvm's config.h files to match more closely what is generated bydim2011-02-262-11/+132
| | | | a regular autoconf-based build. More cosmetic than functional changes.
* Upgrade our copy of llvm/clang to r126079, from upstream's trunk.dim2011-02-2048-243/+299
| | | | | 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.
* When the make target is 'install', don't descend into the clangrpaulo2010-10-301-3/+5
| | | | | libraries subdirectories since there's nothing to do there. This saves us quite a few seconds off installworld, esp. if the disk I/O is slow.
* Upgrade Clang and LLVM to the 2.8 release. See here for release notes:dim2010-10-071-2/+2
| | | | | | http://llvm.org/releases/2.8/docs/ReleaseNotes.html Approved by: rpaulo (mentor)
* Upgrade our Clang in base to r114020, from upstream's release_28 branch.dim2010-09-2043-86/+260
| | | | Approved-by: rpaulo (mentor)
* In all Makefiles under lib/clang, consistently use tabs instead ofdim2010-09-198-8/+8
| | | | | | spaces after the '=' sign in macro assignments. 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-224-0/+14
| | | | | | | | | -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-2055-408/+973
| | | | | | | | | 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 even two more unneeded files from libllvmsupport.ed2010-06-151-8/+7
|
* Remove unneeded files from the build.ed2010-06-1512-51/+46
| | | | | | | | | | | | | | | 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-132-2/+2
| | | | | | | | | 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.
* Disable usage of __DATE__.ed2010-06-101-1/+1
| | | | | This ensures that the Clang binary doesn't change checksums every time it's built.
* 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-09115-0/+1811
Approved by: ed (mentor)
OpenPOWER on IntegriCloud