Skip to content
  1. Aug 11, 2009
  2. Aug 10, 2009
  3. Aug 09, 2009
  4. Aug 08, 2009
  5. Aug 07, 2009
  6. Aug 06, 2009
  7. Aug 05, 2009
  8. Aug 04, 2009
  9. Aug 03, 2009
    • Daniel Dunbar's avatar
      c0deed32
    • Nick Lewycky's avatar
      129bb416
    • Daniel Dunbar's avatar
      Remove now unused arguments from TargetRegistry::lookupTarget. · 719d2355
      Daniel Dunbar authored
      llvm-svn: 77950
      719d2355
    • 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
  10. Aug 02, 2009
  11. Aug 01, 2009
  12. Jul 31, 2009
Loading