summaryrefslogtreecommitdiffstats
path: root/lib/clang
Commit message (Collapse)AuthorAgeFilesLines
* Fix the TARGET_ABI value clang uses. It shpuld be gnueabi on all ARMandrew2014-10-011-3/+3
| | | | soft-float architectures, and gnueabihf for hard-float.
* Remove MK_ARM_EABI, the armeb issues have been fixed. The code to supportandrew2014-10-011-2/+1
| | | | | | | | | | | | the oabi is still in the tree, but it is expected this will be removed as developers work on surrounding code. With this commit the ARM EABI is the only supported supported ABI by FreeBSD on ARMa 32-bit processors. X-MFC after: never Relnotes: yes Differential Revision: https://reviews.freebsd.org/D876
* Replace DPADD with DPSRCS to fix "make checkdpadd"ngie2014-08-181-1/+1
| | | | | | | | Phabric: D625 Approved by: jmmv (mentor) Reviewed by: dim PR: 192734 MFC after: 2 weeks
* Stop telling people to directly report llvm or clang bugs upstream,dim2014-08-132-2/+2
| | | | | | | point them to the FreeBSD bug tracker instead, since we use our own patches. MFC after: 3 days
* Remove ia64.marcel2014-07-074-8/+0
| | | | | | | | | | | | | | | | | This includes: o All directories named *ia64* o All files named *ia64* o All ia64-specific code guarded by __ia64__ o All ia64-specific makefile logic o Mention of ia64 in comments and documentation This excludes: o Everything under contrib/ o Everything under crypto/ o sys/xen/interface o sys/sys/elf_common.h Discussed at: BSDcan
* In some scenarios, when generating llvm/clang .inc.h files, multipledim2014-06-101-32/+43
| | | | | | | | | source files could be passed to tblgen or clang-tblgen, leading to a "Too many positional arguments specified" error message. Fix this by replacing the too-generic ${.ALLSRC} sources with explicit paths. Reported by: rysto32@gmail.com, rodrigc MFC after: 3 days
* Use the new -d option that was added to tblgen between llvm/clang 3.3dim2014-05-141-78/+93
| | | | | | | | | | | | | | | | | | and 3.4 to generate dependency files for the '.inc.h' files generated from .td files, and .sinclude those dependency files in clang.build.mk. This will make future incremental builds of lib/clang and usr.bin/clang work correctly, whenever any of the .td files get modified. Note that this will not fix any problems with incremental builds from *before* this revision, since there will not yet be any generated dependency files. A quick workaround is to run the following: find /usr/obj -type f -name '*.inc.h' | xargs rm and then a regular incremental buildworld (e.g. with -DNO_CLEAN). MFC after: 3 days
* Upgrade our copy of llvm/clang to 3.4.1 release. This release containsdim2014-05-124-29/+15
| | | | | | | | | | | | | | | mostly fixes, for the following upstream bugs: http://llvm.org/PR16365 http://llvm.org/PR17473 http://llvm.org/PR18000 http://llvm.org/PR18068 http://llvm.org/PR18102 http://llvm.org/PR18165 http://llvm.org/PR18260 http://llvm.org/PR18290 http://llvm.org/PR18316 http://llvm.org/PR18460 http://llvm.org/PR18473 http://llvm.org/PR18515 http://llvm.org/PR18526 http://llvm.org/PR18600 http://llvm.org/PR18762 http://llvm.org/PR18773 http://llvm.org/PR18860 http://llvm.org/PR18994 http://llvm.org/PR19007 http://llvm.org/PR19010 http://llvm.org/PR19033 http://llvm.org/PR19059 http://llvm.org/PR19144 http://llvm.org/PR19326 MFC after: 2 weeks
* Eliminate EARLY_BUILD flag. It is redundant and means MK_CLANG_FULL=noimp2014-05-102-9/+6
| | | | | | and MK_LLDB=no, so set those explicitly (now that we can do that). Simplify tests for these variables as well, since we know they will always be defined regardless of the phase of the build.
* Use src.opts.mk in preference to bsd.own.mk except where we need stuffimp2014-05-0610-9/+11
| | | | from the latter.
* Add a SUBDIR_PARALLEL option to bsd.subdir.mk, to allow make to processdim2014-03-261-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | all the SUBDIR entries in parallel, instead of serially. Apply this option to a selected number of Makefiles, which can greatly speed up the build on multi-core machines, when using make -j. This can be extended to more Makefiles later on, whenever they are verified to work correctly with parallel building. I tested this on a 24-core machine, with make -j48 buildworld (N = 6): before stddev after stddev ======= ====== ======= ====== real time 1741.1 16.5 959.8 2.7 user time 12468.7 16.4 14393.0 16.8 sys time 1825.0 54.8 2110.6 22.8 (user+sys)/real 8.2 17.1 E.g. the build was approximately 45% faster in real time. On machines with less cores, or with lower -j settings, the speedup will not be as impressive. But at least you can now almost max out a machine with buildworld! Submitted by: jilles MFC after: 2 weeks
* Add a new ARM TARGET_ARCH, armv6hf. This is considered experimental.andrew2014-03-231-2/+4
| | | | | | | | | | | | | | | | | | | | | | | | | This targets the existing ARMv6 and ARMv7 SoCs that contain a VFP unit. This is an optional coprocessors may not be present in all devices, however it appears to be in all current SoCs we support. armv6hf targets the VFP variant of the ARM EABI and our copy of gcc is too old to support this. Because of this there are a number of WITH/WITHOUT options that are unsupported and must be left as the default value. The options and their required value are: * WITH_ARM_EABI * WITHOUT_GCC * WITHOUT_GNUCXX In addition, without an external toolchain, the following need to be left as their default: * WITH_CLANG * WITH_CLANG_IS_CC As there is a different method of passing float and double values to functions the ABI is incompatible with existing armv6 binaries. To use this a full rebuild of world is required. Because no floating point values are passed into the kernel an armv6 kernel with VFP enabled will work with an armv6hf userland and vice versa.
* Merge from head up to r262536.dim2014-02-265-4/+9
|\
| * Update LLDB bmake build for r262187emaste2014-02-185-4/+9
| | | | | | | | Sponsored by: DARPA, AFRL
* | Add Makefile glue to build the Sparc backend libraries and link themdim2014-02-2022-1/+150
|/ | | | into the clang executable.
* Upgrade our copy of llvm/clang to 3.4 release. This version supportsdim2014-02-1641-147/+173
| | | | | | | | | | | | | | | | | all of the features in the current working draft of the upcoming C++ standard, provisionally named C++1y. The code generator's performance is greatly increased, and the loop auto-vectorizer is now enabled at -Os and -O2 in addition to -O3. The PowerPC backend has made several major improvements to code generation quality and compile time, and the X86, SPARC, ARM32, Aarch64 and SystemZ backends have all seen major feature work. Release notes for llvm and clang can be found here: <http://llvm.org/releases/3.4/docs/ReleaseNotes.html> <http://llvm.org/releases/3.4/tools/clang/docs/ReleaseNotes.html> MFC after: 1 month
* Enable llvm's integrated assembler for PowerPC, since it should now bedim2013-12-164-0/+20
| | | | | | | good enough for typical usage. Requested by: rdivacky MFC after: 1 week
* lldb: Threaded inferior support for FreeBSDemaste2013-12-031-1/+2
| | | | | | | | | | This is in the process of being submitted to the upstream LLDB repository. The thread list functionality is modelled in part on GDBRemoteCommunicationClient. LLDB bug pr16696 and code review D2267 Sponsored by: DARPA, AFRL
* Update LLDB to upstream r196259 snapshotemaste2013-12-032-0/+4
| | | | Sponsored by: DARPA, AFRL
* Update LLDB to upstream r194122 snapshotemaste2013-11-128-6/+17
| | | | | | | | | | | | | ludes minor changes relative to upstream, for compatibility with FreeBSD's in-tree LLVM 3.3: - Reverted LLDB r191806, restoring use of previous API. - Reverted part of LLDB r189317, restoring previous enum names. - Work around missing LLVM r192504, using previous registerEHFrames API (limited functionality). - Removed PlatformWindows header include and init/terminate calls. Sponsored by: DARPA, AFRL
* Bump OS versions in the toolchain triples to 11.0, and bump thedim2013-10-101-2/+2
| | | | | | __FreeBSD_cc_version predefined macros in clang and gcc. Approved by: re (gjb)
* Add LLDB bmake infrastructureemaste2013-09-2038-9/+963
| | | | | | | | | | | This connects LLDB to the build, but it is disabled by default. Add WITH_LLDB= to src.conf to build it. Note that LLDB requires a C++11 compiler so is disabled on platforms using GCC. Approved by: re (gjb) Sponsored by: DARPA, AFRL
* Upgrade our copy of llvm/clang to 3.3 release.dim2013-06-1214-13/+38
| | | | | | Release notes are still in the works, these will follow soon. MFC after: 1 month
* Use an ugly hack to get around bootstrapping problems when buildingdim2013-05-131-0/+5
| | | | | | | | | | | | | | | clang on head between r239347 and r245428. The former revision introduced CLOCK_PROCESS_CPUTIME_ID as a clock id for the clock_gettime() function and friends, but it was only added in <sys/time.h>, not in <time.h>. Any program including <time.h> would therefore not be able to use CLOCK_PROCESS_CPUTIME_ID, even though the value of _POSIX_CPUTIME indicates its existence. The latter revision synchronized the defines again. Work around this problem by defining the id on the command line for the particular .cpp file that needs it. If the id ever changes value, this hack will need to be updated.
* Allow building clang on older FreeBSD releases, where log2() does notdim2013-05-031-0/+5
| | | | | | | exist yet. With this change, I have verified that building head on 8.1-RELEASE works. Noticed by: Ryan Stone <rysto32@gmail.com>
* Upgrade our copy of llvm/clang to trunk r178860, in preparation of thedim2013-04-1260-139/+247
| | | | | | | | | upcoming 3.3 release (branching and freezing expected in a few weeks). Preliminary release notes can be found at the usual location: <http://llvm.org/docs/ReleaseNotes.html> An MFC is planned once the actual 3.3 release is finished.
* Allow us to build clang for ARM EABI. Clang and llvm use theandrew2013-02-121-1/+9
| | | | | | | arm-gnueabi-freebsd10.0 triple for EABI. Use this when we are on arm or armv6 and are building for EABI. Reviewed by: dim
* Pull in r170135 from upstream clang trunk:dim2013-02-0264-8/+147
| | | | | | | | | | | | | | | | Dont use/link ARCMT, StaticAnalyzer and Rewriter to clang when the user specifies not to. Dont build ASTMatchers with Rewriter disabled and StaticAnalyzer when it's disabled. Without all those three, the clang binary shrinks (x86_64) from ~36MB to ~32MB (unstripped). To disable these clang components, and get a smaller clang binary built and installed, set WITHOUT_CLANG_FULL in src.conf(5). During the initial stages of buildworld, those extra components are already disabled automatically, to save some build time. MFC after: 1 week
* Upgrade our copy of llvm/clang to 3.2 release.dim2012-12-231-2/+2
| | | | | | | | | | Release notes for llvm: http://llvm.org/releases/3.2/docs/ReleaseNotes.html Release notes for clang: http://llvm.org/releases/3.2/tools/clang/docs/ReleaseNotes.html MFC after: 2 weeks
* Cleanup a few duplicate llvm libs that snuck in with the recent update.dim2012-12-111-4/+1
| | | | Noticed by: rdivacky
* Upgrade our copy of llvm/clang to r168974, from upstream's release_32dim2012-12-0334-55/+114
| | | | | branch. This is effectively llvm/clang 3.2 RC2; the 3.2 release is coming soon.
* Add support for bmake. This includes:marcel2012-10-061-3/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | 1. Don't do upgrade_checks when using bmake. As long as we have WITH_BMAKE, there's a bootstrap complication in ths respect. Avoid it. Make the necessary changes to have upgrade_checks work wth bmake anyway. 2. Remove the use of -E. It's not needed in our build because we use ?= for the respective variables, which means that we'll take the environment value (if any) anyway. 3. Properly declare phony targets as phony as bmake is a lot smarter (and thus agressive) about build avoidance. 4. Make sure CLEANFILES is complete and use it on .NOPATH. bmake is a lot smarter about build avoidance and should not find files we generate in the source tree. We should not have files in the repository we want to generate, but this is an easier way to cross this hurdle. 5. Have behavior under bmake the same as it is under make with respect to halting when sub-commands fail. Add "set -e" to compound commands so that bmake is informed when sub-commands fail. 6. Make sure crunchgen uses the same make as the rest of the build. This is important when the make utility isn't called make (but bmake for example). 7. While here, add support for using MAKEOBJDIR to set the object tree location. It's the second alternative bmake looks for when determining the actual object directory (= .OBJDIR). Submitted by: Simon Gerraty <sjg@juniper.net> Submitted by: John Van Horne <jvanhorne@juniper.net>
* Do not install incomplete unwind.h from clang. This header file was meantjkim2012-10-051-1/+0
| | | | | | | | | | to be a wrapper for the canonical system header file. Unfortunately, we do not have one (yet) and some times it is causing weird failures when clang is used for building ports. More complete and correct file will come from libcxxrt in the future. Discussed with: dim, kib, theraven MFC after: 1 week
* Sprinkle a bit of style.Makefile(5) across various clang Makefiles. Nodim2012-08-232-14/+14
| | | | | | functional changes. MFC after: 3 days
* Add three additional clang intrinsics headers, which I missed in thedim2012-08-201-1/+4
| | | | previous import.
* Upgrade our copy of llvm/clang to trunk r162107. With thanks todim2012-08-2039-34/+116
| | | | Benjamin Kramer and Joerg Sonnenberger for their input and fixes.
* 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-039-33/+19
| | | | | | | 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-1653-79/+269
| | | | | | | 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
* Add a WITH_CLANG_EXTRAS option for src.conf(5), disabled by default,dim2012-02-0519-0/+197
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | that builds the following additional llvm/clang tools: - bugpoint - llc - lli - llvm-ar - llvm-as - llvm-bcanalyzer - llvm-diff - llvm-dis - llvm-extract - llvm-ld - llvm-link - llvm-mc - llvm-nm - llvm-objdump - llvm-prof - llvm-ranlib - llvm-rtdyld - llvm-stub - macho-dump - opt These tools are mainly useful for people that want to manipulate llvm bitcode (.bc) and llvm assembly language (.ll) files, or want to tinker with llvm and clang themselves. MFC after: 2 weeks
* In several llvm library Makefiles, remove extraneous slashes at the enddim2012-01-014-4/+4
| | | | | | of SRCDIR definitions. MFC after: 3 days
* 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
* 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.
OpenPOWER on IntegriCloud