Skip to content
  1. Aug 03, 2009
    • Daniel Dunbar's avatar
      Pass target triple string in to TargetMachine constructor. · 0f16ea5c
      Daniel Dunbar authored
      This is not just a matter of passing in the target triple from the module;
      currently backends are making decisions based on the build and host
      architecture. The goal is to migrate to making these decisions based off of the
      triple (in conjunction with the feature string). Thus most clients pass in the
      target triple, or the host triple if that is empty.
      
      This has one important change in the way behavior of the JIT and llc.
      
      For the JIT, it was previously selecting the Target based on the host
      (naturally), but it was setting the target machine features based on the triple
      from the module. Now it is setting the target machine features based on the
      triple of the host.
      
      For LLC, -march was previously only used to select the target, the target
      machine features were initialized from the module's triple (which may have been
      empty). Now the target triple is taken from the module, or the host's triple is
      used if that is empty. Then the triple is adjusted to match -march.
      
      The take away is that -march for llc is now used in conjunction with the host
      triple to initialize the subtarget. If users want more deterministic behavior
      from llc, they should use -mtriple, or set the triple in the input module.
      
      llvm-svn: 77946
      0f16ea5c
  2. Aug 02, 2009
  3. Aug 01, 2009
  4. Jul 31, 2009
  5. Jul 30, 2009
  6. Jul 29, 2009
  7. Jul 28, 2009
  8. Jul 27, 2009
    • Daniel Dunbar's avatar
      llvm-mc: Move AsmLexer::getCurStrVal to StringRef based API. · 52d03b25
      Daniel Dunbar authored
       - My DFS traversal of LLVM is, at least for now, nearly complete! :)
      
      llvm-svn: 77258
      52d03b25
    • Nick Lewycky's avatar
      Fix libLTO: · fd6a2498
      Nick Lewycky authored
       * Call InitializeAllTargets on every path where we might query the
         TargetRegistry. This fixes PR4604.
       * flush the formatted_raw_ostream& or else not all of the assembly will make
         it to the .s file. (It doesn't do this in its destructor?!)
       * Due to a reversed conditional, libLTO was reporting many symbols as both
         defined and undefined, including two definitions of the same symbol name
         in its symbol list.
      
      llvm-svn: 77170
      fd6a2498
  9. Jul 26, 2009
  10. Jul 25, 2009
  11. Jul 24, 2009
  12. Jul 23, 2009
Loading