Skip to content
  1. Aug 14, 2019
  2. Aug 05, 2019
  3. Jul 11, 2019
  4. Jul 05, 2019
    • Nico Weber's avatar
      lld, llvm-dlltool, llvm-lib: Use getAsString() instead of getSpelling() for printing unknown args · a7802763
      Nico Weber authored
      Since OPT_UNKNOWN args never have any values and consist only of
      spelling (and are never aliased), this doesn't make any difference in
      practice, but it's more consistent with Arg's guidance to use
      getAsString() for diagnostics, and it matches what clang does.
      
      Also tweak two tests to use an unknown option that contains '=' for
      additional coverage while here. (The new tests pass fine with the old
      code too though.)
      
      llvm-svn: 365200
      a7802763
    • Nico Weber's avatar
      Make joined instances of JoinedOrSeparate flags point to the unaliased args,... · cf1a11de
      Nico Weber authored
      Make joined instances of JoinedOrSeparate flags point to the unaliased args, like all other arg types do
      
      This fixes an 8-year-old regression. r105763 made it so that aliases
      always refer to the unaliased option – but it missed the "joined" branch
      of JoinedOrSeparate flags. (r162231 then made the Args classes
      non-virtual, and r169344 moved them from clang to llvm.)
      
      Back then, there was no JoinedOrSeparate flag that was an alias, so it
      wasn't observable. Now /U in CLCompatOptions is a JoinedOrSeparate alias
      in clang, and warn_slash_u_filename incorrectly used the aliased arg id
      (using the unaliased one isn't really a regression since that warning
      checks if the undefined macro contains slash or backslash and only then
      emits the warning – and no valid use will pass "-Ufoo/bar" or similar).
      
      Also, lld has many JoinedOrSeparate aliases, and due to this bug it had
      to explicitly call `getUnaliasedOption()` in a bunch of places, even
      though that shouldn't be necessary by design. After this fix in Option,
      these calls really don't have an effect any more, so remove them.
      
      No intended behavior change.
      
      (I accidentally fixed this bug while working on PR29106 but then
      wondered why the warn_slash_u_filename broke. When I figured it out, I
      thought it would make sense to land this in a separate commit.)
      
      Differential Revision: https://reviews.llvm.org/D64156
      
      llvm-svn: 365186
      cf1a11de
  5. Jun 14, 2019
  6. Jun 10, 2019
  7. Jun 08, 2019
  8. May 18, 2019
  9. May 17, 2019
  10. Apr 19, 2019
  11. Feb 19, 2019
  12. Feb 06, 2019
  13. Feb 05, 2019
  14. Jan 29, 2019
  15. Jan 19, 2019
    • Chandler Carruth's avatar
      Update the file headers across all of the LLVM projects in the monorepo · 2946cd70
      Chandler Carruth authored
      to reflect the new license.
      
      We understand that people may be surprised that we're moving the header
      entirely to discuss the new license. We checked this carefully with the
      Foundation's lawyer and we believe this is the correct approach.
      
      Essentially, all code in the project is now made available by the LLVM
      project under our new license, so you will see that the license headers
      include that license only. Some of our contributors have contributed
      code under our old license, and accordingly, we have retained a copy of
      our old license notice in the top-level files in each project and
      repository.
      
      llvm-svn: 351636
      2946cd70
  16. Jan 05, 2019
  17. Oct 10, 2018
  18. Sep 10, 2018
  19. Jun 29, 2018
  20. May 15, 2018
  21. Mar 14, 2018
  22. Mar 01, 2018
  23. Feb 27, 2018
  24. Dec 15, 2017
  25. Dec 13, 2017
  26. Dec 12, 2017
  27. Nov 15, 2017
  28. Nov 03, 2017
Loading