Skip to content
  1. May 06, 2013
    • Ulrich Weigand's avatar
      · 92b2085c
      Ulrich Weigand authored
      [SystemZ] Add to --enable-targets=all
      
      This patch finally enables the SystemZ target in the default build
      (with --enable-targets=all).
      
      Patch by Richard Sandiford.
      
      llvm-svn: 181209
      92b2085c
    • Ulrich Weigand's avatar
      · 1ceebf6e
      Ulrich Weigand authored
      [SystemZ] Add configure bits
      
      This patch wires up the SystemZ target in configure, so that it can now be
      built using --enable-targets=systemz.   It is not yet included in the default
      build (--enable-targets=all); this will be done by a follow-up patch.
      
      Patch by Richard Sandiford.
      
      llvm-svn: 181208
      1ceebf6e
  2. May 04, 2013
    • Tim Northover's avatar
      Allow host triple to be correctly overridden in CMake builds · fee13d1e
      Tim Northover authored
      The intended semantics mirror autoconf, where the user is able to
      specify a host triple, but if it's left to the build system then
      "config.guess" is invoked for the default.
      
      This also renames the LLVM_HOSTTRIPLE define to LLVM_HOST_TRIPLE to
      fit in with the style of the surrounding defines.
      
      llvm-svn: 181112
      fee13d1e
  3. May 03, 2013
  4. Apr 28, 2013
  5. Apr 23, 2013
  6. Apr 22, 2013
  7. Mar 25, 2013
  8. Mar 15, 2013
  9. Feb 13, 2013
  10. Feb 08, 2013
  11. Feb 07, 2013
  12. Feb 04, 2013
    • Tim Northover's avatar
      Enable AArch64 as a target built by default. · 43852f20
      Tim Northover authored
      llvm-svn: 174322
      43852f20
    • Patrik Hagglund's avatar
      Pass CPPFLAGS/CFLAGS/CXXFLAGS from the environment of configure to · d91ae4d9
      Patrik Hagglund authored
      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
      d91ae4d9
  13. Feb 03, 2013
  14. Feb 01, 2013
  15. Jan 31, 2013
    • Richard Smith's avatar
      Add -Wno-nested-anon-types to -pedantic builds of LLVM. This Clang warning · 6c26e747
      Richard Smith authored
      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
      6c26e747
    • Tim Northover's avatar
      Add AArch64 as an experimental target. · e0e3aefd
      Tim Northover authored
      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
      e0e3aefd
  16. Jan 30, 2013
  17. Jan 15, 2013
    • David Greene's avatar
      Disable Uninitialized Use Warnings for Broken gcc Versions · 57ad4297
      David Greene authored
      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
      57ad4297
  18. Jan 09, 2013
    • David Greene's avatar
      Disable -Wuninitialized for gcc · 9ff8d471
      David Greene authored
      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
      9ff8d471
    • Dmitri Gribenko's avatar
      Configure: if we compile with clang, check that it is not broken · 06358bd0
      Dmitri Gribenko authored
      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
      06358bd0
  19. Jan 05, 2013
    • Chandler Carruth's avatar
      Finally, fix the autoconf setup to allow for a missing clock_gettime; · d121a7b0
      Chandler Carruth authored
      the source code should now be set up to handle this.
      
      llvm-svn: 171570
      d121a7b0
    • Chandler Carruth's avatar
      Add time getters to the process interface for requesting the elapsed · ef7f968e
      Chandler Carruth authored
      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
      ef7f968e
  20. Jan 02, 2013
  21. Jan 01, 2013
  22. Dec 26, 2012
  23. Dec 13, 2012
  24. Nov 19, 2012
  25. Nov 17, 2012
  26. Nov 14, 2012
  27. Oct 29, 2012
  28. Oct 01, 2012
    • Jordan Rose's avatar
      Re-enable support for --program-prefix. · 3c837abd
      Jordan Rose authored
      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
      3c837abd
  29. Sep 28, 2012
  30. Sep 26, 2012
    • Jordan Rose's avatar
      Revert "Add --program-prefix support to build" · 2998d25a
      Jordan Rose authored
      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
      2998d25a
  31. Sep 25, 2012
  32. Sep 22, 2012
Loading