en Copyright 2015 Java http://172.16.0.5:8080/history/llvm-project-15.0.7/clang/test/Driver/cc1-spawnprocess.c#c35448ba [Driver][test] Fix cc1-spawnprocess.c List of files: /llvm-project-15.0.7/clang/test/Driver/cc1-spawnprocess.c Sat, 14 Nov 2020 17:53:34 +0000 Fangrui Song <i@maskray.me> http://172.16.0.5:8080/history/llvm-project-15.0.7/clang/test/Driver/cc1-spawnprocess.c#bc7df035 Make -fintegrated-cc1 work with cc1asTested 0.018s faster on my machine. List of files: /llvm-project-15.0.7/clang/test/Driver/cc1-spawnprocess.c Sat, 14 Nov 2020 09:16:16 +0000 Fangrui Song <i@maskray.me> http://172.16.0.5:8080/history/llvm-project-15.0.7/clang/test/Driver/cc1-spawnprocess.c#3a2df3ba [Clang][test] fix tests when using external assembler.Summary:The test assume using integraed-as, so make it explicit.Reviewered by: aganeaDifferential Revision: https://reviews.llvm.org/D80454 List of files: /llvm-project-15.0.7/clang/test/Driver/cc1-spawnprocess.c Fri, 22 May 2020 19:33:33 +0000 Yuanfang Chen <yuanfang.chen@sony.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/clang/test/Driver/cc1-spawnprocess.c#20f1abe3 [Clang] Limit -fintegrated-cc1 to only one TUAs discussed in https://reviews.llvm.org/D74447, this patch disables integrated-cc1 behavior if there's more than one job to be executed. This is meant to limit memory bloating, given that currently jobs don't clean up after execution (-disable-free is always active in cc1 mode).I see this behavior as temporary until release 10.0 ships (to ease merging of this patch), then we'll reevaluate the situation, see if D74447 makes more sense on the long term.Differential Revision: https://reviews.llvm.org/D74490 List of files: /llvm-project-15.0.7/clang/test/Driver/cc1-spawnprocess.c Wed, 12 Feb 2020 22:01:55 +0000 Alexandre Ganea <alexandre.ganea@ubisoft.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/clang/test/Driver/cc1-spawnprocess.c#8e5018e9 Replace CLANG_SPAWN_CC1 env var with a driver mode flagFlags are clang's default UI is flags.We can have an env var in addition to that, but in D69825 nobody has yetmentioned why this needs an env var, so omit it for now. If someoneneeds to set the flag via env var, the existing CCC_OVERRIDE_OPTIONSmechanism works for it (set CCC_OVERRIDE_OPTIONS=+-fno-integrated-cc1for example).Also mention the cc1-in-process change in the release notes.Also spruce up the test a bit so it actually tests something :)Differential Revision: https://reviews.llvm.org/D72769 List of files: /llvm-project-15.0.7/clang/test/Driver/cc1-spawnprocess.c Wed, 15 Jan 2020 15:45:02 +0000 Nico Weber <thakis@chromium.org> http://172.16.0.5:8080/history/llvm-project-15.0.7/clang/test/Driver/cc1-spawnprocess.c#c6e69880 Modify test to use -S instead of -c so that it works when an external assembler is used that is not present. List of files: /llvm-project-15.0.7/clang/test/Driver/cc1-spawnprocess.c Wed, 15 Jan 2020 02:58:18 +0000 Douglas Yung <douglas.yung@sony.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/clang/test/Driver/cc1-spawnprocess.c#88b8cb72 Fix NetBSD bot after b4a99a061f517e60985667e39519f60186cbb469 ([Clang][Driver] Re-use the calling process instead of creating a new process for the cc1 invocation) List of files: /llvm-project-15.0.7/clang/test/Driver/cc1-spawnprocess.c Tue, 14 Jan 2020 19:14:07 +0000 Alexandre Ganea <alexandre.ganea@ubisoft.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/clang/test/Driver/cc1-spawnprocess.c#b4a99a06 [Clang][Driver] Re-use the calling process instead of creating a new process for the cc1 invocationWith this patch, the clang tool will now call the -cc1 invocation directly inside the same process. Previously, the -cc1 invocation was creating, and waiting for, a new process.This patch therefore reduces the number of created processes during a build, thus it reduces build times on platforms where process creation can be costly (Windows) and/or impacted by a antivirus.It also makes debugging a bit easier, as there's no need to attach to the secondary -cc1 process anymore, breakpoints will be hit inside the same process.Crashes or signaling inside the -cc1 invocation will have the same side-effect as before, and will be reported through the same means.This behavior can be controlled at compile-time through the CLANG_SPAWN_CC1 cmake flag, which defaults to OFF. Setting it to ON will revert to the previous behavior, where any -cc1 invocation will create/fork a secondary process.At run-time, it is also possible to tweak the CLANG_SPAWN_CC1 environment variable. Setting it and will override the compile-time setting. A value of 0 calls -cc1 inside the calling process; a value of 1 will create a secondary process, as before.Differential Revision: https://reviews.llvm.org/D69825 List of files: /llvm-project-15.0.7/clang/test/Driver/cc1-spawnprocess.c Mon, 13 Jan 2020 15:40:04 +0000 Alexandre Ganea <alexandre.ganea@ubisoft.com>