Tim Kientzle
f09fb7dfa4
Update a couple of files to pull assertion helpers from the new header
2024-05-16 12:50:23 -07:00
Erik Eckstein
e0c862fc94
Remove uses of llvm::empty
...
It's deprecated in rebranch
2022-11-14 09:36:13 +01:00
Josh Soref
730b16c569
Spelling siloptimizer
...
* access
* accessed
* accesses
* accessor
* acquiring
* across
* activated
* additive
* address
* addresses'
* aggregated
* analysis
* and
* appropriately
* archetype
* argument
* associated
* availability
* barriers
* because
* been
* beginning
* belongs
* beneficial
* blocks
* borrow
* builtin
* cannot
* canonical
* canonicalize
* clazz
* cleanup
* coalesceable
* coalesced
* comparisons
* completely
* component
* computed
* concrete
* conjunction
* conservatively
* constituent
* construct
* consuming
* containing
* covered
* creates
* critical
* dataflow
* declaration
* defined
* defining
* definition
* deinitialization
* deliberately
* dependencies
* dependent
* deserialized
* destroy
* deterministic
* deterministically
* devirtualizes
* diagnostic
* diagnostics
* differentiation
* disable
* discipline
* dominate
* dominates
* don't
* element
* eliminate
* eliminating
* elimination
* embedded
* encounter
* epilogue
* epsilon
* escape
* escaping
* essential
* evaluating
* evaluation
* evaluator
* executing
* existential
* existentials
* explicit
* expression
* extended
* extension
* extract
* for
* from
* function
* generic
* guarantee
* guaranteed
* happened
* heuristic
* however
* identifiable
* immediately
* implementation
* improper
* include
* infinite
* initialize
* initialized
* initializer
* inside
* instruction
* interference
* interferes
* interleaved
* internal
* intersection
* intractable
* intrinsic
* invalidates
* irreducible
* irrelevant
* language
* lifetime
* literal
* looks
* materialize
* meaning
* mergeable
* might
* mimics
* modification
* modifies
* multiple
* mutating
* necessarily
* necessary
* needsmultiplecopies
* nonetheless
* nothing
* occurred
* occurs
* optimization
* optimizing
* original
* outside
* overflow
* overlapping
* overridden
* owned
* ownership
* parallel
* parameter
* paths
* patterns
* pipeline
* plottable
* possible
* potentially
* practically
* preamble
* precede
* preceding
* predecessor
* preferable
* preparation
* probably
* projection
* properties
* property
* protocol
* reabstraction
* reachable
* recognized
* recursive
* recursively
* redundant
* reentrancy
* referenced
* registry
* reinitialization
* reload
* represent
* requires
* response
* responsible
* retrieving
* returned
* returning
* returns
* rewriting
* rewritten
* sample
* scenarios
* scope
* should
* sideeffects
* similar
* simplify
* simplifycfg
* somewhat
* spaghetti
* specialization
* specializations
* specialized
* specially
* statistically
* substitute
* substitution
* succeeds
* successful
* successfully
* successor
* superfluous
* surprisingly
* suspension
* swift
* targeted
* that
* that our
* the
* therefore
* this
* those
* threshold
* through
* transform
* transformation
* truncated
* ultimate
* unchecked
* uninitialized
* unlikely
* unmanaged
* unoptimized key
* updataflow
* usefulness
* utilities
* villain
* whenever
* writes
Signed-off-by: Josh Soref <jsoref@users.noreply.github.com >
2022-10-03 18:31:33 -04:00
Andrew Trick
ddf0965d3f
Rewrite ClosureScopeAnalysis for generality.
...
Handle recursive non-escaping local functions.
Previously, it was thought that recursion would force a closure to be
escaping. This is not necessarilly true.
Update AccessEnforcementSelection to conservatively handle closure cycles.
Fixes rdar://88726092 (Compiler hangs when building)
2022-03-18 02:28:53 -07:00
Jordan Rose
a1ea211f22
Add llvm::iterator_range to LLVM.h
...
If we're going to get rid of swift::IteratorRange, let's make
llvm::iterator_range easy to use.
No functionality change.
2019-10-08 15:24:06 -07:00
Jordan Rose
7b0d081965
Remove IteratorRange in favor of llvm::iterator_range
...
Now that llvm::iterator_range has 'empty', there's not enough reason to
keep our own version of it in the Swift repo.
No functionality change.
2019-10-08 11:23:28 -07:00
Michael Gottesman
234fcc1771
[pass-manager] notifyDeleteFunction => notifyWillDeleteFunction.
...
This name makes it clear that the function has not yet been deleted and also
contrasts with the past tense used in the API notifyAddedOrModifiedFunction to
show that said function has already added/modified the function.
2018-07-16 14:11:06 -07:00
Michael Gottesman
190008418e
[pass-manager] notifyAddFunction => notifyAddedOrModifiedFunction.
...
The name notifyAddFunction is actively harmful since the pass manager uses this
entrypoint to notify analyses of added *OR* modified functions. It is up to the
caller analysis to distinguish in between these cases.
I am not vouching for the design, just trying to make names match the
current behavior.
2018-07-16 13:10:28 -07:00
Michael Gottesman
56d100f493
[analysis] Standardize AnalysisKind by moving it out of SILAnalysis into its own "struct enum" in a non-nested scope.
...
Generally in the SIL/SILOptimizer libraries we have been putting kinds in the
swift namespace, not a nested scope in a type in swift (see ValueKind as an
example of this).
2018-07-15 11:00:33 -07:00
Huon Wilson
978a5c89b1
[SILOptimizer] std::function -> llvm::function_ref for some non-escaping params.
2018-05-01 08:29:07 +10:00
Andrew Trick
4575525786
NFC: Cleanup ClosureScope/AccessEnforcementSelection/Tests.
...
Per Devin and John's review.
2017-06-20 14:57:56 -07:00
Andrew Trick
00a72b8517
Comment typo.
2017-06-17 16:27:02 -07:00
Andrew Trick
0ce81c90f0
Doxygen formatting.
2017-06-17 16:19:16 -07:00
Andrew Trick
94db617471
Add TopDownClosureFunctionOrder based on ClosureScopeAnalysis.
...
Simple utility for transfersing functions such that parent scopes are always
visited before noescape closures.
Note that recursion is disallowed. Noescape closures are not reentrant.
2017-06-16 19:08:40 -07:00
Andrew Trick
3bec7d81ac
Add ClosureScopeAnalysis.
...
Record noescape closure scopes. This allows passes to process closures and their
parent scopes in a controlled order. AccessEnforcementSelection needs this
because it needs to process parent scopes before selecting enforcement within
noescape closures.
Eventually this could be used by the PassManager so that
AccessEnforcementSelection can go back to being a function transform.
2017-06-16 19:08:39 -07:00
