search for: 75gib

...forces Debug builds if the user does not specify the build type. https://github.com/llvm/llvm-project/blob/9218ff50f93085d0a16a974db28ca8f14bc66f64/llvm/CMakeLists.txt#L57-L60 I've just done a build of llvm and clang 10 in debug mode for X86 and ARM targets and it weighs in at a whopping 75GiB. I feel that forcing Debug builds in the absence of an option to be a wasteful default. It is a valid and useful thing to call cmake without specifying a build type; absence of a command line switch does not always imply absence of a choice. I took some measurements. The machine under test is an o...

...pecify the build type. >> >> https://github.com/llvm/llvm-project/blob/9218ff50f93085d0a16a974db28ca8f14bc66f64/llvm/CMakeLists.txt#L57-L60 >> >> I've just done a build of llvm and clang 10 in debug mode for X86 and >> ARM targets and it weighs in at a whopping 75GiB. I feel that forcing >> Debug builds in the absence of an option to be a wasteful default. It is >> a valid and useful thing to call cmake without specifying a build type; >> absence of a command line switch does not always imply absence of a >> choice. >> >> I t...

...ser > does not specify the build type. > > https://github.com/llvm/llvm-project/blob/9218ff50f93085d0a16a974db28ca8f14bc66f64/llvm/CMakeLists.txt#L57-L60 > > I've just done a build of llvm and clang 10 in debug mode for X86 and > ARM targets and it weighs in at a whopping 75GiB. I feel that forcing > Debug builds in the absence of an option to be a wasteful default. It is > a valid and useful thing to call cmake without specifying a build type; > absence of a command line switch does not always imply absence of a > choice. > > I took some measurements....

...ser > does not specify the build type. > > > https://github.com/llvm/llvm-project/blob/9218ff50f93085d0a16a974db28ca8f14bc66f64/llvm/CMakeLists.txt#L57-L60 > > I've just done a build of llvm and clang 10 in debug mode for X86 and > ARM targets and it weighs in at a whopping 75GiB. I feel that forcing > Debug builds in the absence of an option to be a wasteful default. It is > a valid and useful thing to call cmake without specifying a build type; > absence of a command line switch does not always imply absence of a > choice. > > I took some measurements. T...

...user > does not specify the build type. > > https://github.com/llvm/llvm-project/blob/9218ff50f93085d0a16a974db28ca8f14bc66f64/llvm/CMakeLists.txt#L57-L60 > > I've just done a build of llvm and clang 10 in debug mode for X86 and > ARM targets and it weighs in at a whopping 75GiB. I feel that forcing > Debug builds in the absence of an option to be a wasteful default. It is > a valid and useful thing to call cmake without specifying a build type; > absence of a command line switch does not always imply absence of a > choice. I don't think the current state...

...r > does not specify the build type. > > https://github.com/llvm/llvm-project/blob/9218ff50f93085d0a16a974db28ca8f14bc66f64/llvm/CMakeLists.txt#L57-L60 > > I've just done a build of llvm and clang 10 in debug mode for X86 and > ARM targets and it weighs in at a whopping 75GiB. I feel that forcing > Debug builds in the absence of an option to be a wasteful default. It is > a valid and useful thing to call cmake without specifying a build type; > absence of a command line switch does not always imply absence of a > choice. I think you are conflating two thing...

...pecify the build type. >> >> https://github.com/llvm/llvm-project/blob/9218ff50f93085d0a16a974db28ca8f14bc66f64/llvm/CMakeLists.txt#L57-L60 >> >> I've just done a build of llvm and clang 10 in debug mode for X86 and >> ARM targets and it weighs in at a whopping 75GiB. I feel that forcing >> Debug builds in the absence of an option to be a wasteful default. It is >> a valid and useful thing to call cmake without specifying a build type; >> absence of a command line switch does not always imply absence of a >> choice. >> >> I t...