Ignore:
Timestamp:
Jun 3, 2011, 5:43:42 PM (14 years ago)
Author:
[email protected]
Message:

2011-06-03 Oliver Hunt <[email protected]>

Reviewed by Gavin Barraclough.

GCC not inlining some functions that it really should be
https://bugs.webkit.org/show_bug.cgi?id=62075

Add ALWAYS_INLINE to a number of parsing and lexing functions
that should always be inlined. This gets us ~1.4% on my ad hoc
parser test.

  • KeywordLookupGenerator.py:
  • parser/JSParser.cpp: (JSC::JSParser::next): (JSC::JSParser::nextTokenIsColon): (JSC::JSParser::consume): (JSC::JSParser::match): (JSC::JSParser::tokenStart): (JSC::JSParser::tokenLine): (JSC::JSParser::tokenEnd):
  • parser/Lexer.cpp: (JSC::isIdentPart):
File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/Source/JavaScriptCore/parser/Lexer.cpp

    r88082 r88083  
    358358}
    359359
    360 static inline bool isIdentPart(int c)
     360static ALWAYS_INLINE bool isIdentPart(int c)
    361361{
    362362    // Character types are divided into two groups depending on whether they can be part of an
Note: See TracChangeset for help on using the changeset viewer.