Open
Bug 1409448
Opened 7 years ago
Updated 8 months ago
Check with -Wno-inline if any important functions don't get inlined
Categories
(Core :: JavaScript Engine, enhancement, P3)
Core
JavaScript Engine
Tracking
()
NEW
People
(Reporter: anba, Unassigned)
References
(Blocks 1 open bug)
Details
From time to time compilers don't inline or inline the wrong function. We could check with "-Wno-inline" if any important functions which we expect to be inlined actually don't get inlined by the compiler.
https://gcc.gnu.org/onlinedocs/gcc/Warning-Options.html#index-Wno-inline
---
-Winline
Warn if a function that is declared as inline cannot be inlined. Even with this option, the compiler does not warn about failures to inline functions declared in system headers.
The compiler uses a variety of heuristics to determine whether or not to inline a function. For example, the compiler takes into account the size of the function being inlined and the amount of inlining that has already been done in the current function. Therefore, seemingly insignificant changes in the source program can cause the warnings produced by -Winline to appear or disappear.
---
Updated•7 years ago
|
status-firefox58:
--- → fix-optional
Priority: -- → P3
Comment 1•7 years ago
|
||
status-firefox59:
--- → ?
Updated•2 years ago
|
Severity: normal → S3
Updated•8 months ago
|
Blocks: sm-js-perf
You need to log in
before you can comment on or make changes to this bug.
Description
•