Bug 172945 - We don't properly parse init_expr when the opcode is an unexpected opcode
Summary: We don't properly parse init_expr when the opcode is an unexpected opcode
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: JavaScriptCore (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Saam Barati
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-06-05 17:39 PDT by Saam Barati
Modified: 2017-06-05 19:59 PDT (History)
11 users (show)

See Also:

Attachments
patch (1.31 KB, patch)
2017-06-05 17:42 PDT, Saam Barati 		no flags Details | Formatted Diff | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Saam Barati 2017-06-05 17:39:40 PDT 
...
Comment 1 Saam Barati 2017-06-05 17:42:43 PDT 
Created attachment 312040 [details]
patch
Comment 2 Saam Barati 2017-06-05 17:51:40 PDT 
Comment on attachment 312040 [details]
patch

Hmm, the test is still failing locally. Very weird.
Comment 3 JF Bastien 2017-06-05 18:07:09 PDT 
Comment on attachment 312040 [details]
patch

r=me
Comment 4 Saam Barati 2017-06-05 18:12:00 PDT 
(In reply to Saam Barati from comment #2)
> Comment on attachment 312040 [details]
> patch
> 
> Hmm, the test is still failing locally. Very weird.

Nevermind, ignore me. It passes.
Comment 5 WebKit Commit Bot 2017-06-05 19:59:58 PDT 
Comment on attachment 312040 [details]
patch

Clearing flags on attachment: 312040

Committed r217814: <http://trac.webkit.org/changeset/217814>
Comment 6 WebKit Commit Bot 2017-06-05 19:59:59 PDT 
All reviewed patches have been landed.  Closing bug.