| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
compression/uncompression in selected LLVM tools.
llvm-svn: 180083
|
|
|
|
|
|
| |
Northover & Eric Christopher
llvm-svn: 180025
|
|
|
|
|
|
|
| |
it. NetBSD/ARM and TILE-Gx are examples for platforms that have an
unusable fenv.h and this avoids the need for a blacklist.
llvm-svn: 177865
|
|
|
|
|
|
| |
issues.
llvm-svn: 177136
|
|
|
|
|
|
|
| |
Since r174770 gcc version check is not needed because CXX_FLAG_CHECK
implements the workaround itself.
llvm-svn: 175080
|
|
|
|
|
|
|
|
|
| |
to use -Wfoo instead of -Wno-foo. This works around a bug in some versions of
gcc, where it will silently accept an unknown -Wno-foo option, but will
generate an error for a compile which uses -Wno-foo if that compile also
triggers any warnings.
llvm-svn: 174770
|
|
|
|
|
|
| |
implementation on the host. This is a little bit unfortunate, but until someone decides to implement a full libm for APFloat, we don't have a better way to get this functionality.
llvm-svn: 174561
|
|
|
|
| |
llvm-svn: 174322
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Makefile.config.
This is implied at the bottom of the help text of configure (besides
CC/CXX/LDFLAGS, already passed to Makefile.config).
For backward compatibility, the values of CFLAGS and CXXFLAGS defaults
to empty, overriding the default values provided by autoconf (for
example, '-g -O2' when CC=gcc').
$(CPP) is not used by our makefiles. Therefore, the value of CPP is
not passed to Makefile.config, despite beeing mentioned by 'configure
--help'.
llvm-svn: 174313
|
|
|
|
| |
llvm-svn: 174288
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
catches uses of an extremely minor and widely-available C++ extension (which
every C++ compiler I could find supports, but EDG and Clang reject in strict
mode).
The diagnosed code pattern looks like this:
struct X {
union {
struct {
int a;
int b;
} S;
};
};
llvm-svn: 174103
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This patch adds support for AArch64 (ARM's 64-bit architecture) to
LLVM in the "experimental" category. Currently, it won't be built
unless requested explicitly.
This initial commit should have support for:
+ Assembly of all scalar (i.e. non-NEON, non-Crypto) instructions
(except the late addition CRC instructions).
+ CodeGen features required for C++03 and C99.
+ Compilation for the "small" memory model: code+static data <
4GB.
+ Absolute and position-independent code.
+ GNU-style (i.e. "__thread") TLS.
+ Debugging information.
The principal omission, currently, is performance tuning.
This patch excludes the NEON support also reviewed due to an outbreak of
batshit insanity in our legal department. That will be committed soon bringing
the changes to precisely what has been approved.
Further reviews would be gratefully received.
llvm-svn: 174054
|
|
|
|
|
|
|
|
|
|
|
| |
This adds a new --with-python option to allow configuration of the python binary
for building. If not specified, $PATH will be searched for common python binary
names (python, python2, python3). If specified, and the path is not executable,
it will attempt to search $PATH.
Signed-off-by: Saleem Abdulrasool <compnerd@compnerd.org>
Reviewed-by: Eric Christopher <echristo@gmail.com>, Daniel Dunbar <daniel@zuster.org>
llvm-svn: 173890
|
|
|
|
|
|
|
| |
http://llvm-reviews.chandlerc.com/D332
Signed-off-by: Saleem Abdulrasool <compnerd@compnerd.org>
llvm-svn: 173879
|
|
|
|
|
|
|
|
|
| |
This simply fixes up quoting of macro invocations to appease newer versions of autotools.
http://llvm-reviews.chandlerc.com/D332
Signed-off-by: Saleem Abdulrasool <compnerd@compnerd.org>
llvm-svn: 173878
|
|
|
|
|
|
|
|
|
| |
Additional quoting for safety and satisfying newer autotools. Fix a couple of 80 column violations.
http://llvm-reviews.chandlerc.com/D333
Signed-off-by: Saleem Abdulrasool <compnerd@compnerd.org>
llvm-svn: 173877
|
|
|
|
|
|
|
|
|
|
|
|
| |
Some versions of gcc accept unsupported -W flags and run just fine if
there are no warnings, but die with an unsupported flag error if a
warning is encountered. gcc 4.3 and gcc 4.4 both exhibit this
behavior for -Wno-maybe-uninitialized. Therefore, if the flag check
for -Wno-maybe-uninitialized succeeds, only use
-Wno-maybe-uninitialized if we are using gcc version 4.7 or greater.
Use -Wno-uninitialized otherwise.
llvm-svn: 172543
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
If the compiler is gcc, disable variants of -Wuninitialized depending
on the gcc version. This gets a lot of false positive warnings out of
the build.
Generate a new configure for the gcc -Wno-uninitialized fix.
Pick up -Wno-uninitialized from configure
Add the option -Wno[-maybe]-uninitialized as determined by configure.
llvm-svn: 172006
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Some linux distibutions (for example, Mageia 2, Fedora 17) ship Clang that is
essentially broken for the end user. Clang can not find or compile libstdc++
headers.
The issue is that our configure prefers clang over gcc, thus selecting a broken
Clang when a working GCC is available.
Now we detect this issue by compiling a simple program. If it does not
compile, configure stops with an error suggesting the user to select a
different compiler.
llvm-svn: 171975
|
|
|
|
|
|
| |
to filcab on IRC for spotting.
llvm-svn: 171573
|
|
|
|
|
|
| |
the source code should now be set up to handle this.
llvm-svn: 171570
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
wall time, user time, and system time since a process started.
For walltime, we currently use TimeValue's interface and a global
initializer to compute a close approximation of total process runtime.
For user time, this adds support for an somewhat more precise timing
mechanism -- clock_gettime with the CLOCK_PROCESS_CPUTIME_ID clock
selected.
For system time, we have to do a full getrusage call to extract the
system time from the OS. This is expensive but unavoidable.
In passing, clean up the implementation of the old APIs and fix some
latent bugs in the Windows code. This might have manifested on Windows
ARM systems or other systems with strange 64-bit integer behavior.
The old API for this both user time and system time simultaneously from
a single getrusage call. While this results in fewer system calls, it
also results in a lower precision user time and if only user time is
desired, it introduces a higher overhead. It may be worthwhile to switch
some of the pass timers to not track system time and directly track user
and wall time. The old API also tracked walltime in a confusing way --
it just set it to the current walltime rather than providing any measure
of wall time since the process started the way buth user and system time
are tracked. The new API is more consistent here.
The plan is to eventually implement these methods for a *child* process
by using the wait3(2) system call to populate an rusage struct
representing the whole subprocess execution. That way, after waiting on
a child process its stats will become accurate and cheap to query.
llvm-svn: 171551
|
|
|
|
|
|
| |
VMCore to IR.
llvm-svn: 171360
|
|
|
|
| |
llvm-svn: 171342
|
|
|
|
| |
llvm-svn: 171108
|
|
|
|
| |
llvm-svn: 171037
|
|
|
|
|
|
| |
in clang. The default remains to build those.
llvm-svn: 170134
|
|
|
|
|
|
| |
Noticed by Dimitri Andric!
llvm-svn: 168319
|
|
|
|
| |
llvm-svn: 168272
|
|
|
|
|
|
| |
Approved by Chris Lattner.
llvm-svn: 167984
|
|
|
|
|
|
| |
as valid triples denote Mips target.
llvm-svn: 166961
|
|
|
|
|
|
|
|
|
| |
The Apple buildbots have been modified not to pass --target,
so they shouldn't choke on a default program prefix anymore.
Patch by Rick Foos!
llvm-svn: 164956
|
|
|
|
|
|
| |
Patch committed on behalf of Kirill Uhanov
llvm-svn: 164831
|
|
|
|
|
|
| |
See: http://en.wikipedia.org/wiki/If_and_only_if Commit 164767
llvm-svn: 164768
|
|
|
|
| |
llvm-svn: 164767
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The Apple buildbots are set up to pass --target to configure for both
cross- and non-cross-compile builds, and the standard autoconf response
to this is to set the program prefix to '<target>-'. Until we can figure
out the proper way to handle this (don't pass --target? pass an explicit
--program-prefix=""? don't auto-populate program_prefix with target_alias?)
it's more important to keep the buildbots running.
This reverts r164633 / ba48ceb1a3802e20e781ef04ea2573ffae2ac414.
llvm-svn: 164651
|
|
|
|
| |
llvm-svn: 164633
|
|
|
|
|
|
|
|
|
| |
whether or not we want to print out backtrace information. Useful
for libraries that don't need backtrace information on a crash.
rdar://11844710
llvm-svn: 164426
|
|
|
|
| |
llvm-svn: 162722
|
|
|
|
| |
llvm-svn: 162707
|
|
|
|
| |
llvm-svn: 161880
|
|
|
|
|
|
| |
Added LLVM_EXPERIMENTAL_TARGETS_TO_BUILD in CMake and --enable-experimental-targets in configure.
llvm-svn: 161561
|
|
|
|
|
|
| |
Patch by David Hill.
llvm-svn: 161344
|
|
|
|
|
|
| |
while building as requested by Lang.
llvm-svn: 161253
|
|
|
|
|
|
| |
commit code in clang that uses this shortly.
llvm-svn: 161252
|
|
|
|
|
|
| |
rdar://11366674
llvm-svn: 161251
|
|
|
|
|
|
| |
packages for particular uses.
llvm-svn: 161246
|
|
|
|
|
|
|
|
|
|
| |
to store additional flag options since too many things can
and do override CPPFLAGS. Also, this is exported, unlike CPPFLAGS
so it can be actually used elsewhere. This should enable us
to remove the AC_SUBSTs in the intel checks, but I have no way
of testing it.
llvm-svn: 161233
|
|
|
|
| |
llvm-svn: 160621
|
|
|
|
|
| |
cmake: Add LLVM_HOSTTRIPLE. For now, it is same as TARGET_TRIPLE.
llvm-svn: 160609
|