| Summary: | make sdiv a template on armv7s to remove duplicate code in dfg | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | WebKit | Reporter: | Alex Christensen <achristensen> | ||||||
| Component: | JavaScriptCore | Assignee: | Alex Christensen <achristensen> | ||||||
| Status: | RESOLVED FIXED | ||||||||
| Severity: | Normal | CC: | benjamin, dbates, fpizlo, ggaren | ||||||
| Priority: | P2 | ||||||||
| Version: | 528+ (Nightly build) | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Attachments: |
|
||||||||
|
Description
Alex Christensen
2014-06-11 14:07:44 PDT
Created attachment 232902 [details]
Patch
Created attachment 233074 [details]
Patch
Comment on attachment 233074 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=233074&action=review > Source/JavaScriptCore/assembler/ARMv7Assembler.h:1520 > + COMPILE_ASSERT(datasize == 32); Does this compile? I mean, COMPILE_ASSERT() takes two arguments: a predicate and a error message to be shown if the predicate evaluates to false. Moreover, the blog post <https://www.webkit.org/blog/3172/webkit-and-cxx11/> implies that we should explicitly use static_assert() in new C++ code instead of the COMPILE_ASSERT() macro function (even though it calls through to static_assert()) since we require ports to build WebKit with compilers that supports the C++11 static_assert feature. (In reply to comment #3) I'll use static_assert and double check that it compiles. |