summaryrefslogtreecommitdiffstats
path: root/lldb/source/Plugins/ScriptInterpreter/Python/ScriptInterpreterPython.cpp
diff options
context:
space:
mode:
authorjmolloy <jmolloy@google.com>2019-11-04 19:25:13 +0000
committerJames Molloy <James Molloy jmolloy@google.com>2019-11-05 15:41:42 +0000
commit39525a6723854e9920b2560aadaa399cfbbd006a (patch)
tree9fae65c0ccd9e50b655cf9cec6059c83b5209750 /lldb/source/Plugins/ScriptInterpreter/Python/ScriptInterpreterPython.cpp
parent7b710a4294c1baed0157d86d3e2dabac78c306ce (diff)
downloadbcm5719-llvm-39525a6723854e9920b2560aadaa399cfbbd006a.tar.gz
bcm5719-llvm-39525a6723854e9920b2560aadaa399cfbbd006a.zip
[DFAPacketizer] Allow up to 64 functional units
Summary: To drive the automaton we used a uint64_t as an action type. This contained the transition's resource requirements as a conjunction: (a OR b) AND (b OR c) We encoded this conjunction as a sequence of four 16-bit bitmasks. This limited the number of addressable functional units to 16, which is quite low and has bitten many people in the past. Instead, the DFAEmitter now generates a lookup table from InstrItinerary class (index of the ItinData inside the ProcItineraries) to an internal action index which is essentially a dense embedding of the conjunctive form. Because we never materialize the conjunctive form, we no longer have the 16 FU restriction. In this patch we limit to 64 functional units due to using a uint64_t bitmask in the DFAEmitter. Now that we've decoupled these representations we can increase this in future. Reviewers: ThomasRaoux, kparzysz, majnemer Reviewed By: ThomasRaoux Subscribers: hiraditya, llvm-commits Tags: #llvm Differential Revision: https://reviews.llvm.org/D69110
Diffstat (limited to 'lldb/source/Plugins/ScriptInterpreter/Python/ScriptInterpreterPython.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud