search for: resourceref

.../ResourceManager.cpp > +++ b/llvm/lib/MCA/HardwareUnits/ResourceManager.cpp > @@ -292,7 +292,7 @@ void ResourceManager::issueInstruction( > ResourceState &RS = *Resources[Index]; > > - if (!R.second.isReserved()) { > + if (!R.second.isReserved() && RS.isReady()) { > ResourceRef Pipe = selectPipe(R.first); > use(Pipe); > BusyResources[Pipe] += CS.size(); > ``` > which is probably the cause of that weird behavior I reported. > > > > I’m also somewhat curious about what “NumUnits” is modeling: I haven’t > totally worked through the code yet, but it...

> On May 9, 2020, at 5:12 PM, Andrea Di Biagio via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > The llvm scheduling model is quite simple and doesn't allow mca to accurately simulate the execution of individual uOPs. That limitation is sort-of acceptable if you consider how the scheduling model framework was originally designed with a different goal in mind (i.e. machine

...y/1.8/puppet/parser/ast/resourcedef.rb ./opt/csw/lib/ruby/site_ruby/1.8/puppet/parser/ast/resourcedefaults.rb ./opt/csw/lib/ruby/site_ruby/1.8/puppet/parser/ast/resourceoverride.rb ./opt/csw/lib/ruby/site_ruby/1.8/puppet/parser/ast/resourceparam.rb ./opt/csw/lib/ruby/site_ruby/1.8/puppet/parser/ast/resourceref.rb ./opt/csw/lib/ruby/site_ruby/1.8/puppet/parser/ast/selector.rb ./opt/csw/lib/ruby/site_ruby/1.8/puppet/parser/ast/tag.rb ./opt/csw/lib/ruby/site_ruby/1.8/puppet/parser/ast/vardef.rb ./opt/csw/lib/ruby/site_ruby/1.8/puppet/parser/ast.rb ./opt/csw/lib/ruby/site_ruby/1.8/puppet/parser/collector.rb...