summaryrefslogtreecommitdiffstats
path: root/contrib/llvm/tools/clang/lib
Commit message (Collapse)AuthorAgeFilesLines
* Similar to what is already done for Linux, make clang not complain aboutdim2012-07-281-0/+8
| | | | | | | | unused -g, -emit-llvm or -w arguments when doing linking. E.g. invoking "clang -g foo.o -o foo" will now be silent. Reported by: Jakub Lach <jakub_lach@mailplus.pl> MFC after: 1 week
* Similar to r238472, let clang pass --enable-new-dtags to the linkerdim2012-07-281-1/+3
| | | | | | | invocation by default. Also make sure --hash-style=both is passed for the same arches as gcc, e.g. arm, sparc and x86. X-MFC-with: r238472
* Pull in r159895 from upstream clang trunk:dim2012-07-131-8/+17
| | | | | | | | | | | | | | When marking virtual functions as used for a class' vtable, mark all functions which will appear in the vtable as used, not just those ones which were declared within the class itself. Fixes an issue reported as comment#3 in PR12763 -- we sometimes assert in codegen if we try to emit a reference to a function declaration which we've not marked as referenced. This also matches gcc's observed behavior. This should fix clang assertions when building certain components of the LibreOffice port. MFC after: 3 days
* Pull in r156591 from upstream llvm trunk:dim2012-05-291-1/+2
| | | | | | | | | | | | | | | Allow unique_file to take a mode for file permissions, but default to user only read/write. and r156592 from upstream clang trunk: For final output files create them with mode 0664 to match other compilers and expected defaults. This should fix clang creating files with mode 0600. Reported by: James <james@hicag.org> MFC after: 3 days
* For clang, similar to r236137, enable gnu hash generation for dynamicdim2012-05-291-0/+3
| | | | ELF binaries on x86.
* Pull in r157212 from upstream clang trunk:dim2012-05-271-18/+14
| | | | | | | | | | | | | | | | | | | Revert r115805. An array type is required to have a range type, however, the range can be unknown for the upper bound. Testcase to follow. Part of rdar://11457152 This should fix ctfconvert producing error messages during kernel builds, similar to: ERROR: scsi_all.c: die 24561: failed to retrieve array bounds These were caused by incorrect debug information for flexible array members of structs. MFC after: 3 days
* Upgrade our copy of llvm/clang to 3.1 release. Release notes can bedim2012-05-2314-297/+101
| | | | | | found at: http://llvm.org/releases/3.1/docs/ReleaseNotes.html MFC after: 3 days
* Upgrade our copy of llvm/clang to r155985, from upstream's release_31dim2012-05-03103-3370/+2865
| | | | | | | 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-16411-34915/+91394
| | | | | | | 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
* Pull in r145194 from upstream clang trunk:dim2012-03-121-11/+34
| | | | | | | | | | | | | Make our handling of MMX x SSE closer to what gcc does: * Enabling sse enables mmx. * Disabling (-mno-mmx) mmx, doesn't disable sse (we got this right already). * The order in not important. -msse -mno-mmx is the same as -mno-mmx -msse. Some configure scripts depend on this. PR: i386/165968 MFC after: 3 days
* Upgrade our copy of llvm/clang to 3.0 release. Release notes can bedim2011-12-0910-857/+984
| | | | | | found at: http://llvm.org/releases/3.0/docs/ReleaseNotes.html MFC after: 1 week
* Rename the linker emulation name for powerpc and powerc64. This is needed thatandreast2011-11-191-1/+1
| | | | | we can also use the upstream binutils linker where we have to have a unique name for the FreeBSD emulation.
* Pull in r144505 from upstream clang trunk:dim2011-11-194-2/+39
| | | | | | | | | | Fix the signature of the getcontext builtin, eliminating incorrect warnings about its prototype. This also adds a -W(no-)builtin-requires-header option, which can be used to enable or disable warnings of this kind. MFC after: 1 week
* Pull in r144110 from upstream clang trunk:dim2011-11-191-8/+0
| | | | | | | | | | Mark the overloaded atomic builtins as having custom type checking, which they do. This avoids all of the default argument promotions that we (1) don't want, and (2) undo during that custom type checking, and makes sure that we don't run into trouble during template instantiation. Fixes llvm/clang PR11320. MFC after: 1 week
* Pull in r143305 and r143312 from upstream clang trunk, so using "clangdim2011-10-301-3/+18
| | | | | | | | -march=native" on AMD K10 family processors no longer errors out with "unknown target CPU 'amdfam10'". This also enables use of SSE4A. Reported by: David Marec <david.marec@davenulle.org> MFC after: 3 days
* Upgrade our copy of llvm/clang to r142614, from upstream's release_30dim2011-10-22393-31839/+50217
| | | | | | | branch. This brings us very close to the 3.0 release, which is expected in a week or two. MFC after: 1 week
* Fix breakage introduced by r226518.dim2011-10-191-2/+3
| | | | | Spotted by: tinderbox, yanefbsd at gmail.com Pointy hat to: dim
* Fix the way clang retrieves the major FreeBSD release number from thedim2011-10-181-4/+5
| | | | | | | target triple, so that the __FreeBSD__ and __FreeBSD_cc_version builtin macros return the expected results. Spotted by: nalitoja at gmail.com
* Upgrade our copy of llvm/clang to r135360, from upstream's trunk.dim2011-07-17205-9644/+25432
|
* Upgrade our copy of llvm/clang to r132879, from upstream's trunk.dim2011-06-12163-4954/+11672
|
* Upgrade our copy of llvm/clang to r130700, from upstream's trunk.dim2011-05-02294-15103/+29816
|
* For clang, make -mno-mmx imply -mno-3dnow. This is what gcc does.dim2011-04-171-4/+3
| | | | | Submitted by: arundel Obtained from: http://llvm.org/viewvc/llvm-project?view=rev&revision=129665
* Update llvm/clang to trunk r126547.dim2011-02-27117-2627/+4840
| | | | | | | | | | | | | | 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'.
* Remove getDriver().Dir + /../libexec and /usr/libexec from clang'sdim2011-02-261-2/+0
| | | | program paths. Unlike gcc, clang has no executables in libexec.
* Remove misapplied space.dim2011-02-261-1/+1
|
* Recently, in upstream clang, a fix was done to add -L/usr/lib to thedim2011-02-241-8/+9
| | | | | | | | | | | | | | | | | | | | | | | | | arguments passed to ld, when linking. This was to appease configure scripts in several ports, that grep for such a -L option in "${CC} -v" output, to determine the startup objects passed to ld. Note ld itself does not need to be told about /usr/lib, since it has this path builtin anyway. However, if clang is built as a bootstrap tool during buildworld, it should not use *anything* outside ${WORLDTMP} to include or link with. The upstream fix to add -L/usr/lib breaks this assumption, and can thus cause libraries from /usr/lib to be linked in during buildworld. This can result in buildworld dying during linking of zinject, where it picks up the wrong copy of libzpool.so, eventually leading to: /usr/obj/usr/src/tmp/lib/libthr.so.3: undefined reference to `_rtld_get_stack_prot' Fix this issue by not adding any hardcoded paths, but by looping through the run-time library path list, which is already correctly set for the bootstrap phase. Reported by: datastream.freecity@gmail.com Pointy hat to: dim
* Upgrade our copy of llvm/clang to r126079, from upstream's trunk.dim2011-02-20354-36065/+72683
| | | | | This contains many improvements, primarily better C++ support, an integrated assembler for x86 and support for -pg.
* Actually, check for any kind of "C string type".rdivacky2010-10-131-8/+4
| | | | Approved by: rpaulo (mentor)
* Extend this check for const unsigned char *.rdivacky2010-10-131-2/+6
| | | | Approved by: rpaulo (mentor)
* Remove more unneeded files and directories from contrib/llvm. Thisdim2010-10-1133-885/+0
| | | | | | | still allows us to build tblgen and clang, and further reduces the footprint in the tree. Approved by: rpaulo (mentor)
* Rework the analysis of the 'r' specifier. It turns out that we can'trpaulo2010-10-112-1/+6
| | | | | | | | make it like xArg because they are different ('x' doesn't accept sign, but 'r' does). This fixes some warnings when building DDB with clang. With help from: rdivacky
* Restore the support for the 'r' and the 'y' conversion specifiers, firstrpaulo2010-10-111-0/+2
| | | | | added on r208987. These are undocumented but are part of printf(9).
* Upgrade Clang and LLVM to the 2.8 release. See here for release notes:dim2010-10-071-1/+1
| | | | | | http://llvm.org/releases/2.8/docs/ReleaseNotes.html Approved by: rpaulo (mentor)
* Apply r207674 from the clangbsd project branch:dim2010-10-061-1/+1
| | | | | | | | | Make "clang -print-multi-os-directory" return "." on amd64, matching gcc's behaviour. This is needed because some ports use the option to determine the installation directory for their libraries. Requested by: kwm Approved by: rpaulo (mentor)
* Upgrade our Clang in base to r114020, from upstream's release_28 branch.dim2010-09-20304-29899/+39314
| | | | Approved-by: rpaulo (mentor)
* Modify clang so that when TOOLS_PREFIX is defined we register therpaulo2010-08-212-12/+21
| | | | | | | | 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
* Upgrade our Clang in base to r108428.ed2010-07-20251-12319/+31842
| | | | | | | | | 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
* Do the branding right this time.ed2010-06-121-0/+3
| | | | | | | | | 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.
* Introduce -fformat-extensions. A local FreeBSD extension usedrdivacky2010-06-104-4/+51
| | | | | | for additional printf modifiers in kernel. Approved by: ed (mentor)
* Remove the commented out piece that slipped as a mismerge.rdivacky2010-06-091-10/+0
| | | | Approved by: ed (mentor)
* Adjust include paths to FreeBSD. Remove /usr/local/include andrdivacky2010-06-091-0/+15
| | | | | | add /usr/include/clang/$VERSION (currently VERSION is 2.0). Approved by: ed (mentor)
* Change the default CPU to i486 on i386 (architecture).rdivacky2010-06-091-1/+1
| | | | Approved by: ed (mentor)
* Import LLVM/clang from vendor stripped of docs/ test/ website/ www/ examples/rdivacky2010-06-09383-0/+280085
in llvm/ and/or llvm/contrib/clang/ respectively. Approved by: ed (mentor) Approved by: core
OpenPOWER on IntegriCloud