[Webkit-unassigned] [Bug 162692] New: B3 and Air opcodes should leave room for flags

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=162692

            Bug ID: 162692
           Summary: B3 and Air opcodes should leave room for flags
    Classification: Unclassified
           Product: WebKit
           Version: WebKit Nightly Build
          Hardware: All
                OS: All
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: JavaScriptCore
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: fpizlo at apple.com

We want to be able to express variants of opcodes using some meta-data in the opcode itself.  This is great in B3 because then this meta-data could become part of the accepts() logic for dynamic casting Values.  This is great in Air because then we don't have to add more fields to Inst - the opcode field would simply expand to tell us this extra information, leading to hopefully a cleaner overall design.  For example a "trapping" flag is not meaningful for every opcode, so we don't want a trapping bit in Inst; we want a smart Opcode-like class that will reveal a trapping flag exactly when the opcode makes it meaningful, and intelligently reuses those bits for other things for opcodes that don't care about trapping but maybe care about other things.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.webkit.org/pipermail/webkit-unassigned/attachments/20160928/c15e8b16/attachment.html>