diff options
| author | Philip Herron <philip.herron@embecosm.com> | 2022-10-21 13:40:40 +0100 |
|---|---|---|
| committer | Philip Herron <philip.herron@embecosm.com> | 2022-12-04 21:00:45 +0000 |
| commit | b5c354de73ddccb7738778c1e013d42b96aeb048 (patch) | |
| tree | 606e6aa1cd1ba5f6dbee7a54dc6df92cfc8d20b8 /gcc/tree-vectorizer.cc | |
| parent | 6c5dc8aa1a99bc3a0220aeabecd84ffa6f233433 (diff) | |
| download | gcc-b5c354de73ddccb7738778c1e013d42b96aeb048.zip gcc-b5c354de73ddccb7738778c1e013d42b96aeb048.tar.gz gcc-b5c354de73ddccb7738778c1e013d42b96aeb048.tar.bz2 | |
Add closure binding's tracking to name resolution
When we have a closure block referencing variables in a parent function,
we must track what these are. We do this by having a context of closures
so if we have a variable reference and its declared in a rib whose node id
is less than the node id of the closure's node id we know it must be a
captured variable. We also need to iterate all possible closure contexts
as we might be in the case of a nested closure.
Addresses #195
Diffstat (limited to 'gcc/tree-vectorizer.cc')
0 files changed, 0 insertions, 0 deletions