1. 01 3月, 2022 1 次提交
  2. 20 2月, 2022 1 次提交
  3. 17 1月, 2022 1 次提交
  4. 13 1月, 2022 1 次提交
  5. 08 1月, 2022 1 次提交
  6. 16 12月, 2021 1 次提交
  7. 15 12月, 2021 1 次提交
  8. 13 12月, 2021 1 次提交
  9. 12 9月, 2021 1 次提交
  10. 11 9月, 2021 1 次提交
  11. 24 8月, 2021 2 次提交
    • T
      Improve liveness analysis for generators · 9f6f8620
      Tomasz Miąsko 提交于
      Liveness analysis for generators assumes that execution always continues
      normally after a yield point, not accounting for the fact that generator
      could be dropped before completion.
      
      If generators captures any variables by reference, those variables could
      be used within a generator, or when the generator completes, but also
      after each yield point in the case the generator is dropped.
      
      Account for the case when generator is dropped after yielding, but
      before running to the completion. This effectively considers all
      variables captured by reference to be used after a yield point.
      9f6f8620
    • A
      2229: Consider varaiables mentioned in closure as used · d7b4ee8a
      Aman Arora 提交于
      d7b4ee8a
  12. 16 8月, 2021 1 次提交
  13. 05 8月, 2021 1 次提交
    • N
      Disable unused variable lint for naked functions · 9c0147c0
      Nathaniel McCallum 提交于
      In most calling conventions, accessing function parameters may require
      stack access. However, naked functions have no assembly prelude to set
      up stack access.  This is why naked functions may only contain a single
      `asm!()` block. All parameter access is done inside the `asm!()` block,
      so we cannot validate the liveness of the input parameters. Therefore,
      we should disable the lint for naked functions.
      
      rust-lang/rfcs#2774
      rust-lang/rfcs#2972
      9c0147c0
  14. 22 5月, 2021 2 次提交
  15. 11 5月, 2021 1 次提交
  16. 25 4月, 2021 1 次提交
  17. 06 4月, 2021 1 次提交
  18. 27 3月, 2021 1 次提交
  19. 19 3月, 2021 1 次提交
    • J
      Replace closures_captures and upvar_capture with closure_min_captures · 52dba13e
      Jennifer Wills 提交于
      make changes to liveness to use closure_min_captures
      
      use different span
      
      borrow check uses new structures
      
      rename to CapturedPlace
      
      stop using upvar_capture in regionck
      
      remove the bridge
      
      cleanup from rebase + remove the upvar_capture reference from mutability_errors.rs
      
      remove line from livenes test
      
      make our unused var checking more consistent
      
      update tests
      
      adding more warnings to the tests
      
      move is_ancestor_or_same_capture to rustc_middle/ty
      
      update names to reflect the closures
      
      add FIXME
      
      check that all captures are immutable borrows before returning
      
      add surrounding if statement like the original
      
      move var out of the loop and rename
      Co-authored-by: NLogan Mosier <logmosier@gmail.com>
      Co-authored-by: NRoxane Fruytier <roxane.fruytier@hotmail.com>
      52dba13e
  20. 01 3月, 2021 1 次提交
  21. 25 2月, 2021 1 次提交
  22. 22 1月, 2021 1 次提交
  23. 08 1月, 2021 1 次提交
  24. 30 12月, 2020 1 次提交
  25. 24 12月, 2020 1 次提交
  26. 09 12月, 2020 2 次提交
  27. 07 12月, 2020 1 次提交
  28. 06 12月, 2020 2 次提交
    • L
      Implement liveness passes for if-let guards · cfaaa21e
      LeSeulArtichaut 提交于
      cfaaa21e
    • T
      Compress RWU from at least 32 bits to 4 bits · bc8317a1
      Tomasz Miąsko 提交于
      The liveness uses a mixed representation of RWUs based on the
      observation that most of them have invalid reader and invalid
      writer. The packed variant uses 32 bits and unpacked 96 bits.
      Unpacked data contains reader live node and writer live node.
      
      Since live nodes are used only to determine their validity,
      RWUs can always be stored in a packed form with four bits for
      each: reader bit, writer bit, used bit, and one extra padding
      bit to simplify packing and unpacking operations.
      bc8317a1
  29. 11 11月, 2020 1 次提交
  30. 19 10月, 2020 1 次提交
  31. 18 10月, 2020 2 次提交
  32. 17 10月, 2020 1 次提交
  33. 30 9月, 2020 2 次提交
  34. 28 9月, 2020 1 次提交