summaryrefslogtreecommitdiffstats
path: root/lib/clang/include
Commit message (Collapse)AuthorAgeFilesLines
* Upgrade our copy of llvm/clang to 3.1 release. Release notes can bedim2012-05-232-4/+4
| | | | | | found at: http://llvm.org/releases/3.1/docs/ReleaseNotes.html MFC after: 3 days
* Make sure a few new internal clang headers get installed, I missed thesedim2012-05-051-1/+7
| | | | | | | | | | | | | | in the last import. They are sometimes needed when you want to use advanced instructions. Also, add clang's internal stdalign.h header to ObsoleteFiles.inc, since it is redundant: we already have a stdalign.h header in /usr/include. Pointy hat to: dim PR: kern/167574 Submitted by: jkim Reported by: Oliver Hartmann <ohartman@zedat.fu-berlin.de> MFC after: 2 weeks
* Upgrade our copy of llvm/clang to r155985, from upstream's release_31dim2012-05-033-5/+14
| | | | | | | branch. This brings us very close to the 3.1 release, which is planned for May 14th. MFC after: 2 weeks
* Upgrade our copy of llvm/clang to trunk r154661, in preparation of thedim2012-04-1610-38/+86
| | | | | | | 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
* 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-092-2/+4
| | | | | | found at: http://llvm.org/releases/3.0/docs/ReleaseNotes.html MFC after: 1 week
* 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-226-27/+35
| | | | | | | branch. This brings us very close to the 3.0 release, which is expected in a week or two. MFC after: 1 week
* Upgrade our copy of llvm/clang to r135360, from upstream's trunk.dim2011-07-1727-40/+27
|
* Upgrade our copy of llvm/clang to r132879, from upstream's trunk.dim2011-06-121-2/+2
|
* Upgrade our copy of llvm/clang to r130700, from upstream's trunk.dim2011-05-024-9/+19
|
* Update llvm/clang to trunk r126547.dim2011-02-271-2/+2
| | | | | | | | | | | | | | 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-2015-102/+55
| | | | | This contains many improvements, primarily better C++ support, an integrated assembler for x86 and support for -pg.
* 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-2010-3/+97
| | | | Approved-by: rpaulo (mentor)
* Upgrade our Clang in base to r108428.ed2010-07-2010-105/+36
| | | | | | | | | 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
* 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
* Disable usage of __DATE__.ed2010-06-101-1/+1
| | | | | This ensures that the Clang binary doesn't change checksums every time it's built.
* Import the build makefiles for clang/LLVM.rdivacky2010-06-0970-0/+1014
Approved by: ed (mentor)
OpenPOWER on IntegriCloud