https://gcc.gnu.org/bugzilla/show_bug.cgi?id=124353

--- Comment #7 from Sam James <sjames at gcc dot gnu.org> ---
The linemap appearance in there got me wondering, so with reduced flags...

On trunk (*), using -w, I get:
> Maximum resident set size (kbytes): 2713052

Without -w, I get:
> Maximum resident set size (kbytes): 2714984

So not a huge difference, but the flags I removed obviously made a big
difference. Will figure out which.

(*) x86_64-pc-linux-gnu-g++ -MMD -MF
obj/deps/v8/src/compiler/turboshaft/v8_compiler.csa-optimize-phase.o.d
-D_GLIBCXX_USE_CXX11_ABI=1 -D_FILE_OFFSET_BITS=64
-DNODE_OPENSSL_CONF_NAME=nodejs_conf -DNODE_OPENSSL_CERT_STORE
-DICU_NO_USER_DATA_OVERRIDE -DV8_GYP_BUILD -DV8_TYPED_ARRAY_MAX_SIZE_IN_HEAP=64
-D__STDC_FORMAT_MACROS -DV8_TARGET_ARCH_X64 -DV8_HAVE_TARGET_OS
-DV8_TARGET_OS_LINUX '-DV8_EMBEDDER_STRING="-node.27"' -DENABLE_DISASSEMBLER
-DV8_PROMISE_INTERNAL_FIELD_COUNT=1
-DV8_ENABLE_PRIVATE_MAPPING_FORK_OPTIMIZATION -DV8_SHORT_BUILTIN_CALLS
-DOBJECT_PRINT -DV8_INTL_SUPPORT -DV8_ATOMIC_OBJECT_FIELD_WRITES
-DV8_ENABLE_LAZY_SOURCE_POSITIONS -DV8_USE_SIPHASH -DNDEBUG
-DV8_WIN64_UNWINDING_INFO -DV8_ENABLE_REGEXP_INTERPRETER_THREADED_DISPATCH
-DV8_USE_ZLIB -DV8_ENABLE_LEAPTIERING -DV8_ENABLE_SPARKPLUG -DV8_ENABLE_MAGLEV
-DV8_ENABLE_TURBOFAN -DV8_ENABLE_WEBASSEMBLY
-DV8_ENABLE_JAVASCRIPT_PROMISE_HOOKS
-DV8_ENABLE_CONTINUATION_PRESERVED_EMBEDDER_DATA -DV8_ALLOCATION_FOLDING
-DV8_ALLOCATION_SITE_TRACKING -DV8_ADVANCED_BIGINT_ALGORITHMS
-DV8_ENABLE_WASM_SIMD256_REVEC -I../../deps/v8 -I../../deps/v8/include
-Igen/generate-bytecode-output-root -Igen
-I../../deps/v8/third_party/fp16/src/include
-I../../deps/v8/third_party/abseil-cpp -O3 -fno-rtti -fno-exceptions
-fno-strict-aliasing -std=gnu++20  -c
../../deps/v8/src/compiler/turboshaft/csa-optimize-phase.cc -o
obj/deps/v8/src/compiler/turboshaft/v8_compiler.csa-optimize-phase.o

Reply via email to