Dan Elphick 97336f2e52 [compiler] Don't calculate StateValueAccess::size in InstructionSelector ... Since the size of the parameters and locals inputs is already stored on the FrameStateFunctionInfo, this skips the calls to size() and just reuses the previous values. The stack parameter can only have a size of 0 or 1 depending on whether it's a InterpretedFunction frame or not. It also extends the verifier to check that the values to match those returned by StateValueAccess::size and changes a unit test that added a TypedStateValues of size 2 to the stack input. Bug: v8:10051 Change-Id: I3693c04b4677812b9f19491c198d0551df20f817 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2047045 Reviewed-by: Jakob Gruber <jgruber@chromium.org> Reviewed-by: Georg Neis <neis@chromium.org> Commit-Queue: Dan Elphick <delphick@chromium.org> Cr-Commit-Position: refs/heads/master@{#66268}		2020-02-14 10:30:31 +00:00
..
instruction-selector-unittest.cc	[compiler] Don't calculate StateValueAccess::size in InstructionSelector	2020-02-14 10:30:31 +00:00
instruction-selector-unittest.h	[cleanup] Replace simple typedefs by using	2019-05-27 12:39:49 +00:00
instruction-sequence-unittest.cc	Use static RegisterName function instead of RegisterConfiguration	2018-11-21 10:24:13 +00:00
instruction-sequence-unittest.h	[turbofan][cleanup] Remove dead ExplicitOperand class.	2019-09-10 08:23:40 +00:00
instruction-unittest.cc	Move code generation related files to src/codegen	2019-05-21 10:33:39 +00:00