Skip to content
  1. Jan 10, 2012
  2. Jan 09, 2012
  3. Dec 30, 2011
  4. Dec 29, 2011
  5. Dec 02, 2011
  6. Nov 30, 2011
  7. Oct 30, 2011
  8. Oct 18, 2011
  9. Oct 16, 2011
  10. Oct 14, 2011
  11. Oct 13, 2011
  12. Oct 11, 2011
  13. Oct 10, 2011
  14. Oct 09, 2011
  15. Oct 03, 2011
  16. Sep 05, 2011
  17. Aug 26, 2011
  18. Jul 07, 2011
  19. May 20, 2011
  20. May 03, 2011
  21. Apr 15, 2011
  22. Apr 14, 2011
  23. Dec 13, 2010
  24. Dec 10, 2010
    • Nate Begeman's avatar
      Formalize the notion that AVX and SSE are non-overlapping extensions from the... · 8b08f523
      Nate Begeman authored
      Formalize the notion that AVX and SSE are non-overlapping extensions from the compiler's point of view.  Per email discussion, we either want to always use VEX-prefixed instructions or never use them, and are taking "HasAVX" to mean "Always use VEX".  Passing -mattr=-avx,+sse42 should serve to restore legacy SSE support when desirable.
      
      llvm-svn: 121439
      8b08f523
  25. Dec 04, 2010
  26. Oct 30, 2010
  27. Oct 01, 2010
  28. Aug 12, 2010
  29. Jul 23, 2010
  30. Jul 19, 2010
  31. May 04, 2010
    • Daniel Dunbar's avatar
      MC/X86: Add "support" for matching ATT style mnemonic prefixes. · 9b816a1b
      Daniel Dunbar authored
       - The idea is that when a match fails, we just try to match each of +'b', +'w',
         +'l'. If exactly one matches, we assume this is a mnemonic prefix and accept
         it. If all match, we assume it is width generic, and take the 'l' form.
      
       - This would be a horrible hack, if it weren't so simple. Therefore it is an
         elegant solution! Chris gets the credit for this particular elegant
         solution. :)
      
       - Next step to making this more robust is to have the X86 matcher generate the
         mnemonic prefix information. Ideally we would also compute up-front exactly
         which mnemonic to attempt to match, but this may require more custom code in
         the matcher than is really worth it.
      
      llvm-svn: 103012
      9b816a1b
  32. Apr 05, 2010
    • Jakob Stoklund Olesen's avatar
      Replace TSFlagsFields and TSFlagsShifts with a simpler TSFlags field. · b93331f3
      Jakob Stoklund Olesen authored
      When a target instruction wants to set target-specific flags, it should simply
      set bits in the TSFlags bit vector defined in the Instruction TableGen class.
      
      This works well because TableGen resolves member references late:
      
      class I : Instruction {
        AddrMode AM = AddrModeNone;
        let TSFlags{3-0} = AM.Value;
      }
      
      let AM = AddrMode4 in
      def ADD : I;
      
      TSFlags gets the expected bits from AddrMode4 in this example.
      
      llvm-svn: 100384
      b93331f3
Loading