mirror of
https://github.com/RGBCube/serenity
synced 2025-07-25 06:27:45 +00:00
Kernel: static vs non-static constexpr variables
Problem: - `static` variables consume memory and sometimes are less optimizable. - `static const` variables can be `constexpr`, usually. - `static` function-local variables require an initialization check every time the function is run. Solution: - If a global `static` variable is only used in a single function then move it into the function and make it non-`static` and `constexpr`. - Make all global `static` variables `constexpr` instead of `const`. - Change function-local `static const[expr]` variables to be just `constexpr`.
This commit is contained in:
parent
2b64d163cd
commit
5751327195
15 changed files with 30 additions and 37 deletions
|
@ -137,7 +137,7 @@ struct [[gnu::packed]] received_packet_header {
|
|||
|
||||
UNMAP_AFTER_INIT void NE2000NetworkAdapter::detect()
|
||||
{
|
||||
static const auto ne2k_ids = Array<PCI::ID, 11> {
|
||||
constexpr auto ne2k_ids = Array {
|
||||
PCI::ID { 0x10EC, 0x8029 }, // RealTek RTL-8029(AS)
|
||||
|
||||
// List of clones, taken from Linux's ne2k-pci.c
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue