Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
L
loopy
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Kaushik Kulkarni
loopy
Commits
498f8eb0
Commit
498f8eb0
authored
7 years ago
by
Andreas Klöckner
Browse files
Options
Downloads
Patches
Plain Diff
Fix no_sync_with_docs
parent
d260f4e7
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
loopy/kernel/instruction.py
+7
-6
7 additions, 6 deletions
loopy/kernel/instruction.py
with
7 additions
and
6 deletions
loopy/kernel/instruction.py
+
7
−
6
View file @
498f8eb0
...
@@ -91,7 +91,7 @@ class InstructionBase(ImmutableRecord):
...
@@ -91,7 +91,7 @@ class InstructionBase(ImmutableRecord):
.. attribute:: no_sync_with
.. attribute:: no_sync_with
a :class:`frozenset` of tuples of the form `(insn_id, scope)`, where
a :class:`frozenset` of tuples of the form
`
`(insn_id, scope)`
`
, where
`insn_id` refers to :attr:`id` of :class:`Instruction` instances
`insn_id` refers to :attr:`id` of :class:`Instruction` instances
and `scope` is one of the following strings:
and `scope` is one of the following strings:
...
@@ -99,11 +99,12 @@ class InstructionBase(ImmutableRecord):
...
@@ -99,11 +99,12 @@ class InstructionBase(ImmutableRecord):
- `
"
global
"
`
- `
"
global
"
`
- `
"
any
"
`.
- `
"
any
"
`.
This indicates (symmetrically) that program semantics are not affected by
An element ``(insn_id, scope)`` means
"
no conflicting variable access
execution ordering of the involved instructions. In particular,
for variables of ``scope`` between this instruction and ``insn_id``.
no barrier synchronization will be considered necessary with the given
Specifically, loopy will not complain even if it detects that accesses
instruction using barriers of type `scope`, even given the existence of
potentially requiring ordering (e.g. by dependencies) exist, and it
a dependency chain and apparently conflicting access.
will not emit barriers to guard any dependencies from this
instruction on ``insn_id`` that may exist.
Note, that :attr:`no_sync_with` allows instruction matching through wildcards
Note, that :attr:`no_sync_with` allows instruction matching through wildcards
and match expression, just like :attr:`depends_on`.
and match expression, just like :attr:`depends_on`.
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment