maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity
llvm-project/clang/test/Driver/cc1-spawnprocess.c

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

49 lines
2.3 KiB
C
Raw Normal View History

[Clang][test] fix tests when using external assembler. Summary: The test assume using integraed-as, so make it explicit. Reviewered by: aganea Differential Revision: https://reviews.llvm.org/D80454
2020-05-23 03:33:33 +08:00
// If a toolchain uses an external assembler, the test would fail because using
// an external assember would increase job counts. Most toolchains in tree
// use integrated assembler, but we still support external assembler.
// So -fintegrated-as is specified explicitly when applicable.
// RUN: %clang -fintegrated-cc1 -fintegrated-as -c -### %s 2>&1 | FileCheck %s --check-prefix=YES
[Clang] Limit -fintegrated-cc1 to only one TU As 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
2020-02-13 06:01:55 +08:00
// RUN: %clang -fno-integrated-cc1 -c -### %s 2>&1 | FileCheck %s --check-prefix=NO
Replace CLANG_SPAWN_CC1 env var with a driver mode flag Flags are clang's default UI is flags. We can have an env var in addition to that, but in D69825 nobody has yet mentioned why this needs an env var, so omit it for now. If someone needs to set the flag via env var, the existing CCC_OVERRIDE_OPTIONS mechanism works for it (set CCC_OVERRIDE_OPTIONS=+-fno-integrated-cc1 for 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
2020-01-15 23:45:02 +08:00
[Clang] Limit -fintegrated-cc1 to only one TU As 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
2020-02-13 06:01:55 +08:00
// RUN: %clang -fintegrated-cc1 -fno-integrated-cc1 -c -### %s 2>&1 \
Replace CLANG_SPAWN_CC1 env var with a driver mode flag Flags are clang's default UI is flags. We can have an env var in addition to that, but in D69825 nobody has yet mentioned why this needs an env var, so omit it for now. If someone needs to set the flag via env var, the existing CCC_OVERRIDE_OPTIONS mechanism works for it (set CCC_OVERRIDE_OPTIONS=+-fno-integrated-cc1 for 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
2020-01-15 23:45:02 +08:00
// RUN: | FileCheck %s --check-prefix=NO
[Clang][test] fix tests when using external assembler. Summary: The test assume using integraed-as, so make it explicit. Reviewered by: aganea Differential Revision: https://reviews.llvm.org/D80454
2020-05-23 03:33:33 +08:00
// RUN: %clang -fno-integrated-cc1 -fintegrated-cc1 -fintegrated-as -c -### %s 2>&1 \
Replace CLANG_SPAWN_CC1 env var with a driver mode flag Flags are clang's default UI is flags. We can have an env var in addition to that, but in D69825 nobody has yet mentioned why this needs an env var, so omit it for now. If someone needs to set the flag via env var, the existing CCC_OVERRIDE_OPTIONS mechanism works for it (set CCC_OVERRIDE_OPTIONS=+-fno-integrated-cc1 for 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
2020-01-15 23:45:02 +08:00
// RUN: | FileCheck %s --check-prefix=YES
[Clang][test] fix tests when using external assembler. Summary: The test assume using integraed-as, so make it explicit. Reviewered by: aganea Differential Revision: https://reviews.llvm.org/D80454
2020-05-23 03:33:33 +08:00
// RUN: %clang_cl -fintegrated-cc1 -fintegrated-as -c -### -- %s 2>&1 \
Replace CLANG_SPAWN_CC1 env var with a driver mode flag Flags are clang's default UI is flags. We can have an env var in addition to that, but in D69825 nobody has yet mentioned why this needs an env var, so omit it for now. If someone needs to set the flag via env var, the existing CCC_OVERRIDE_OPTIONS mechanism works for it (set CCC_OVERRIDE_OPTIONS=+-fno-integrated-cc1 for 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
2020-01-15 23:45:02 +08:00
// RUN: | FileCheck %s --check-prefix=YES
[Clang] Limit -fintegrated-cc1 to only one TU As 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
2020-02-13 06:01:55 +08:00
// RUN: %clang_cl -fno-integrated-cc1 -c -### -- %s 2>&1 \
Replace CLANG_SPAWN_CC1 env var with a driver mode flag Flags are clang's default UI is flags. We can have an env var in addition to that, but in D69825 nobody has yet mentioned why this needs an env var, so omit it for now. If someone needs to set the flag via env var, the existing CCC_OVERRIDE_OPTIONS mechanism works for it (set CCC_OVERRIDE_OPTIONS=+-fno-integrated-cc1 for 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
2020-01-15 23:45:02 +08:00
// RUN: | FileCheck %s --check-prefix=NO
// RUN: env CCC_OVERRIDE_OPTIONS=+-fintegrated-cc1 \
[Clang][test] fix tests when using external assembler. Summary: The test assume using integraed-as, so make it explicit. Reviewered by: aganea Differential Revision: https://reviews.llvm.org/D80454
2020-05-23 03:33:33 +08:00
// RUN: %clang -fintegrated-cc1 -fintegrated-as -c -### %s 2>&1 \
Replace CLANG_SPAWN_CC1 env var with a driver mode flag Flags are clang's default UI is flags. We can have an env var in addition to that, but in D69825 nobody has yet mentioned why this needs an env var, so omit it for now. If someone needs to set the flag via env var, the existing CCC_OVERRIDE_OPTIONS mechanism works for it (set CCC_OVERRIDE_OPTIONS=+-fno-integrated-cc1 for 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
2020-01-15 23:45:02 +08:00
// RUN: | FileCheck %s --check-prefix=YES
// RUN: env CCC_OVERRIDE_OPTIONS=+-fno-integrated-cc1 \
[Clang] Limit -fintegrated-cc1 to only one TU As 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
2020-02-13 06:01:55 +08:00
// RUN: %clang -fintegrated-cc1 -c -### %s 2>&1 \
Replace CLANG_SPAWN_CC1 env var with a driver mode flag Flags are clang's default UI is flags. We can have an env var in addition to that, but in D69825 nobody has yet mentioned why this needs an env var, so omit it for now. If someone needs to set the flag via env var, the existing CCC_OVERRIDE_OPTIONS mechanism works for it (set CCC_OVERRIDE_OPTIONS=+-fno-integrated-cc1 for 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
2020-01-15 23:45:02 +08:00
// RUN: | FileCheck %s --check-prefix=NO
// YES: (in-process)
// NO-NOT: (in-process)
[Clang] Limit -fintegrated-cc1 to only one TU As 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
2020-02-13 06:01:55 +08:00
// The following tests ensure that only one integrated-cc1 is executed.
// Only one TU, one job, thus integrated-cc1 is enabled.
[Clang][test] fix tests when using external assembler. Summary: The test assume using integraed-as, so make it explicit. Reviewered by: aganea Differential Revision: https://reviews.llvm.org/D80454
2020-05-23 03:33:33 +08:00
// RUN: %clang -fintegrated-cc1 -fintegrated-as -c %s -### 2>&1 | FileCheck %s --check-prefix=YES
[Clang] Limit -fintegrated-cc1 to only one TU As 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
2020-02-13 06:01:55 +08:00
// Only one TU, but we're linking, two jobs, thus integrated-cc1 is disabled.
// RUN: %clang -fintegrated-cc1 %s -### 2>&1 | FileCheck %s --check-prefix=NO
// RUN: echo 'int main() { return f() + g(); }' > %t1.cpp
// RUN: echo 'int f() { return 1; }' > %t2.cpp
// RUN: echo 'int g() { return 2; }' > %t3.cpp
// Three jobs, thus integrated-cc1 is disabled.
// RUN: %clang -fintegrated-cc1 -c %t1.cpp %t2.cpp %t3.cpp -### 2>&1 | FileCheck %s --check-prefix=NO
Make -fintegrated-cc1 work with cc1as Tested 0.018s faster on my machine.
2020-11-14 17:16:16 +08:00
// -fintegrated-cc1 works with cc1as.
[Driver][test] Fix cc1-spawnprocess.c
2020-11-15 01:53:34 +08:00
// macOS triples have an extra -x assembler-with-cpp job so (in-process) is not triggered.
Make -fintegrated-cc1 work with cc1as Tested 0.018s faster on my machine.
2020-11-14 17:16:16 +08:00
// RUN: echo > %t.s
[Driver][test] Fix cc1-spawnprocess.c
2020-11-15 01:53:34 +08:00
// RUN: %clang --target=x86_64-linux -fintegrated-cc1 -fintegrated-as -c -### %t.s 2>&1 | FileCheck %s --check-prefix=YES
// RUN: %clang --target=x86_64-linux -fno-integrated-cc1 -c -### %t.s 2>&1 | FileCheck %s --check-prefix=NO