Summary: | Fix clang build error in JITOpcodes32_64.cpp | ||||||
---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | David Kilzer (:ddkilzer) <ddkilzer> | ||||
Component: | JavaScriptCore | Assignee: | Nobody <webkit-unassigned> | ||||
Status: | RESOLVED FIXED | ||||||
Severity: | Normal | CC: | ap, barraclough, darin, ggaren, oliver | ||||
Priority: | P2 | Keywords: | InRadar | ||||
Version: | 528+ (Nightly build) | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Attachments: |
|
Description
David Kilzer (:ddkilzer)
2011-07-01 09:16:42 PDT
Committed r90232: <http://trac.webkit.org/changeset/90232> Created attachment 99482 [details]
Patch
Looks to me like clang correctly spotted a programming error here, so there was a symptom of this too. This code was originally introduced in r58991 in JavaScriptCore/jit/JITOpcodes.cpp. <http://trac.webkit.org/changeset/58991> How could this be landed without review, and without a regression test? I have an answer to my question - probably because it was originally believed that it's only a build fix. |