From 33ce9b1b5c23cd31eefeb58818f994796dea1704 Mon Sep 17 00:00:00 2001 From: Augustin Cavalier Date: Mon, 16 Sep 2024 13:23:46 -0400 Subject: [PATCH] runtime_loader: Remove -fno-builtin from compiler options. Except on kernel_cpp.cpp. We don't use it for most of libroot, so we don't need it for most of runtime_loader either. The two preceding changes were all that's necessary to fix things with builtins enabled. Very slight performance improvement (the "run 1000 shells" benchmark seems to decrease by about 0.4 seconds out of 16.5 or so.) --- src/system/runtime_loader/Jamfile | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/src/system/runtime_loader/Jamfile b/src/system/runtime_loader/Jamfile index 26907b76a0..d94d31190b 100644 --- a/src/system/runtime_loader/Jamfile +++ b/src/system/runtime_loader/Jamfile @@ -19,11 +19,9 @@ for architectureObject in [ MultiArchSubDirSetup ] { UsePrivateSystemHeaders ; ObjectHdrs find_directory.cpp : $(HAIKU_TOP)/src/system/libroot/os ; + ObjectC++Flags kernel_cpp.cpp : -fno-builtin ; - # Don't let gcc inject built-in function code. This will cause - # dependencies to libroot, which we don't link against. - SubDirCcFlags -fno-builtin ; - SubDirC++Flags -fno-builtin -fno-exceptions ; + SubDirC++Flags -fno-exceptions ; DEFINES += KMESSAGE_CONTAINER_ONLY