Skip to content
Snippets Groups Projects
  1. Apr 09, 2018
  2. Jan 03, 2018
  3. Jan 01, 2018
    • Serge Pavlov's avatar
      Fixed markup formatting · 39c04dc5
      Serge Pavlov authored
      git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@321623 91177308-0d34-0410-b5e6-96231b3b80d8
      39c04dc5
    • Serge Pavlov's avatar
      Enable configuration files in clang · 5f7f2c06
      Serge Pavlov authored
      Clang is inherently a cross compiler and can generate code for any target
      enabled during build. It however requires to specify many parameters in the
      invocation, which could be hardcoded during configuration process in the
      case of single-target compiler. The purpose of configuration files is to
      make specifying clang arguments easier.
      
      A configuration file is a collection of driver options, which are inserted
      into command line before other options specified in the clang invocation.
      It groups related options together and allows specifying them in simpler,
      more flexible and less error prone way than just listing the options
      somewhere in build scripts. Configuration file may be thought as a "macro"
      that names an option set and is expanded when the driver is called.
      
      Use of configuration files is described in `UserManual.rst`.
      
      Differential Revision: https://reviews.llvm.org/D24933
      
      
      git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@321621 91177308-0d34-0410-b5e6-96231b3b80d8
      5f7f2c06
  4. Dec 30, 2017
    • Serge Pavlov's avatar
      Reverted 321587: Enable configuration files in clang · 509607e4
      Serge Pavlov authored
      Need to check targets in tests more carefully.
      
      
      
      git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@321588 91177308-0d34-0410-b5e6-96231b3b80d8
      509607e4
    • Serge Pavlov's avatar
      Enable configuration files in clang · 67245e0d
      Serge Pavlov authored
      Clang is inherently a cross compiler and can generate code for any target
      enabled during build. It however requires to specify many parameters in the
      invocation, which could be hardcoded during configuration process in the
      case of single-target compiler. The purpose of configuration files is to
      make specifying clang arguments easier.
      
      A configuration file is a collection of driver options, which are inserted
      into command line before other options specified in the clang invocation.
      It groups related options together and allows specifying them in simpler,
      more flexible and less error prone way than just listing the options
      somewhere in build scripts. Configuration file may be thought as a "macro"
      that names an option set and is expanded when the driver is called.
      
      Use of configuration files is described in `UserManual.rst`.
      
      Differential Revision: https://reviews.llvm.org/D24933
      
      
      git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@321587 91177308-0d34-0410-b5e6-96231b3b80d8
      67245e0d
  5. Dec 29, 2017
  6. Oct 31, 2017
    • Vlad Tsyrklevich's avatar
      [CFI] Add CFI-icall pointer type generalization · 746fd88c
      Vlad Tsyrklevich authored
      Summary:
      This change allows generalizing pointers in type signatures used for
      cfi-icall by enabling the -fsanitize-cfi-icall-generalize-pointers flag.
      This works by 1) emitting an additional generalized type signature
      metadata node for functions and 2) llvm.type.test()ing for the
      generalized type for translation units with the flag specified.
      
      This flag is incompatible with -fsanitize-cfi-cross-dso because it would
      require emitting twice as many type hashes which would increase artifact
      size.
      
      Reviewers: pcc, eugenis
      
      Reviewed By: pcc
      
      Subscribers: kcc
      
      Differential Revision: https://reviews.llvm.org/D39358
      
      git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@317044 91177308-0d34-0410-b5e6-96231b3b80d8
      746fd88c
  7. Sep 23, 2017
  8. Aug 27, 2017
  9. Jul 19, 2017
  10. Jul 05, 2017
  11. Jul 01, 2017
  12. Apr 12, 2017
    • Bruno Cardoso Lopes's avatar
      [Driver] Add compiler option to generate a reproducer · f2ee5f1a
      Bruno Cardoso Lopes authored
      One way to currently test the reproducers is to setup
      "FORCE_CLANG_DIAGNOSTICS_CRASH=1" before invoking clang. This simulates
      a crash and produces the same contents needed by the reproducers.  The
      reproducers are specially useful when triaging Modules issues, not only
      on crashes, but also for reproducing misleading warnings, errors, etc.
      
      Add a '-gen-reproducer' driver option to clang (or any similar name) and
      give users a flag option.
      
      Note that clang already has a -fno-crash-diagnostics, which disables the
      crash reproducers. I've decided not to propose "-fcrash-diagnostics"
      since it doesn't convey the ideia of reproduction despite a crash.
      
      rdar://problem/24114619
      
      Differential Revision: https://reviews.llvm.org/D27604
      
      git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@300109 91177308-0d34-0410-b5e6-96231b3b80d8
      f2ee5f1a
  13. Feb 17, 2017
  14. Feb 16, 2017
  15. Feb 09, 2017
  16. Feb 02, 2017
  17. Jan 17, 2017
  18. Jan 16, 2017
  19. Jan 14, 2017
  20. Jan 12, 2017
  21. Dec 12, 2016
  22. Oct 27, 2016
  23. Sep 13, 2016
    • Adam Nemet's avatar
      Reapply r281276 with passing -emit-llvm in one of the tests · 8a7af2f3
      Adam Nemet authored
      Original commit message:
      
      Add -fdiagnostics-show-hotness
      
      Summary:
      I've recently added the ability for optimization remarks to include the
      hotness of the corresponding code region.  This uses PGO and allows
      filtering of the optimization remarks by relevance.  The idea was first
      discussed here:
      http://thread.gmane.org/gmane.comp.compilers.llvm.devel/98334
      
      The general goal is to produce a YAML file with the remarks.  Then, an
      external tool could dynamically filter these by hotness and perhaps by
      other things.
      
      That said it makes sense to also expose this at the more basic level
      where we just include the hotness info with each optimization remark.
      For example, in D22694, the clang flag was pretty useful to measure the
      overhead of the additional analyses required to include hotness.
      (Without the flag we don't even run the analyses.)
      
      For the record, Hal has already expressed support for the idea of this
      patch on IRC.
      
      Differential Revision: https://reviews.llvm.org/D23284
      
      git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@281293 91177308-0d34-0410-b5e6-96231b3b80d8
      8a7af2f3
    • Adam Nemet's avatar
      Revert "Add -fdiagnostics-show-hotness" · 8503d694
      Adam Nemet authored
      This reverts commit r281276.
      
      Many bots are failing.
      
      git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@281279 91177308-0d34-0410-b5e6-96231b3b80d8
      8503d694
    • Adam Nemet's avatar
      Add -fdiagnostics-show-hotness · fd2a481c
      Adam Nemet authored
      Summary:
      I've recently added the ability for optimization remarks to include the
      hotness of the corresponding code region.  This uses PGO and allows
      filtering of the optimization remarks by relevance.  The idea was first
      discussed here:
      http://thread.gmane.org/gmane.comp.compilers.llvm.devel/98334
      
      The general goal is to produce a YAML file with the remarks.  Then, an
      external tool could dynamically filter these by hotness and perhaps by
      other things.
      
      That said it makes sense to also expose this at the more basic level
      where we just include the hotness info with each optimization remark.
      For example, in D22694, the clang flag was pretty useful to measure the
      overhead of the additional analyses required to include hotness.
      (Without the flag we don't even run the analyses.)
      
      For the record, Hal has already expressed support for the idea of this
      patch on IRC.
      
      Differential Revision: https://reviews.llvm.org/D23284
      
      git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@281276 91177308-0d34-0410-b5e6-96231b3b80d8
      fd2a481c
  24. Sep 12, 2016
  25. Aug 30, 2016
  26. Aug 15, 2016
  27. Jul 27, 2016
  28. Jul 23, 2016
  29. Jul 21, 2016
  30. Jul 16, 2016
  31. Jul 15, 2016
Loading