Skip to content
  1. Jul 04, 2013
  2. Jun 26, 2013
  3. Jun 14, 2013
  4. Jun 11, 2013
  5. May 29, 2013
  6. May 06, 2013
    • 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
  7. May 04, 2013
  8. May 03, 2013
  9. Apr 28, 2013
  10. Apr 23, 2013
  11. Apr 21, 2013
  12. Apr 12, 2013
  13. Apr 07, 2013
  14. Mar 26, 2013
  15. Mar 25, 2013
  16. Mar 19, 2013
  17. Mar 15, 2013
  18. Mar 13, 2013
  19. Mar 02, 2013
  20. Feb 14, 2013
    • Tim Northover's avatar
      Use correct host/target CMake variables to define lit variables. · bfe84685
      Tim Northover authored
      CMake and autotools disagree on what "host" means in a cross-compilation
      context. Autotools (and lit) take it to be the machine the binaries being
      compiled now will run on. CMake takes it to be the machine actually compiling
      the binaries now.
      
      This change makes lit.site-cfg more consistent between autotools and CMake,
      allowing lit tests (particularly in ExecutionEngine) to run correctly when
      cross-compiled with CMake
      
      llvm-svn: 175179
      bfe84685
  21. Feb 09, 2013
    • Jordan Rose's avatar
      CMake: Use check_symbol_exists instead of check_cxx_symbol_exists. · cea01ee9
      Jordan Rose authored
      check_cxx_symbol_exists requires CMake 2.8.6, so even though I
      recommended it to Owen it's probably better to stay away for now.
      This check is not technically correct because we're checking <math.h>
      but then using <cmath> in the actual code, but if we run into problems we
      can do the same sort of dance as isinf() and isnan() where we check /both/
      headers and then write a wrapper header around them.
      
      llvm-svn: 174773
      cea01ee9
  22. Feb 07, 2013
  23. Feb 04, 2013
    • Edwin Vane's avatar
      Turn off uninitialized-use warnings for gcc in cmake build · a9c5bb3f
      Edwin Vane authored
      Added support to the cmake build to turn off uninitialized use warnings
      for gcc. This cleans the build up somewhat.
      
      Used logic simpler than found in autoconf by making use of the fact that
      although gcc won't complain about unsupported -Wno-* flags it *will*
      complain about unsupported -W flags.
      
      Reviewers: gribozavr, doug.gregor, chandlerc
      llvm-svn: 174299
      a9c5bb3f
  24. Jan 31, 2013
  25. Jan 27, 2013
  26. Jan 25, 2013
    • Reid Kleckner's avatar
      Disable MSVC's warning about noreturn destructors · cd947f97
      Reid Kleckner authored
      This warning fires on:
        Operator::~Operator() {
          llvm_unreachable("should never destroy an Operator");
        }
      
      That seems like a false positive.  I don't see any good way to silence
      the warning here, so I'm disabling it.
      
      llvm-svn: 173455
      cd947f97
  27. Jan 05, 2013
    • 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
  28. Jan 03, 2013
  29. Dec 24, 2012
Loading