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/darwin-dsymutil.c

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

50 lines
2.2 KiB
C
Raw Normal View History

Driver/Darwin: Model dsymutil properly, as a separate action/tool kind which is added as the last output step, instead of just hacking it into the link step. - Among other things, this fixes dSYM generation when using multiple -arch options. llvm-svn: 105475
2010-06-05 02:28:41 +08:00
// Check that we run dsymutil properly with multiple -arch options.
//
rename -ccc-host-triple into -target llvm-svn: 148582
2012-01-21 06:01:23 +08:00
// RUN: %clang -target x86_64-apple-darwin10 -ccc-print-phases \
Driver/Darwin: Model dsymutil properly, as a separate action/tool kind which is added as the last output step, instead of just hacking it into the link step. - Among other things, this fixes dSYM generation when using multiple -arch options. llvm-svn: 105475
2010-06-05 02:28:41 +08:00
// RUN: -arch i386 -arch x86_64 %s -g 2> %t
// RUN: FileCheck -check-prefix=CHECK-MULTIARCH-ACTIONS < %t %s
//
// CHECK-MULTIARCH-ACTIONS: 0: input, "{{.*}}darwin-dsymutil.c", c
// CHECK-MULTIARCH-ACTIONS: 1: preprocessor, {0}, cpp-output
Reapply "Change -save-temps to emit unoptimized bitcode files." This reapplies r224503 along with a fix for compiling Fortran by having the clang driver invoke gcc (see r224546, where it was reverted). I have added a testcase for that as well. Original commit message: It is often convenient to use -save-temps to collect the intermediate results of a compilation, e.g., when triaging a bug report. Besides the temporary files for preprocessed source and assembly code, this adds the unoptimized bitcode files as well. This adds a new BackendJobAction, which is mostly mechanical, to run after the CompileJobAction. When not using -save-temps, the BackendJobAction is combined into one job with the CompileJobAction, similar to the way the integrated assembler is handled. I've implemented this entirely as a driver change, so under the hood, it is just using -disable-llvm-optzns to get the unoptimized bitcode. Based in part on a patch by Steven Wu. rdar://problem/18909437 llvm-svn: 224688
2014-12-21 15:00:00 +08:00
// CHECK-MULTIARCH-ACTIONS: 2: compiler, {1}, ir
// CHECK-MULTIARCH-ACTIONS: 3: backend, {2}, assembler
// CHECK-MULTIARCH-ACTIONS: 4: assembler, {3}, object
// CHECK-MULTIARCH-ACTIONS: 5: linker, {4}, image
// CHECK-MULTIARCH-ACTIONS: 6: bind-arch, "i386", {5}, image
// CHECK-MULTIARCH-ACTIONS: 7: bind-arch, "x86_64", {5}, image
// CHECK-MULTIARCH-ACTIONS: 8: lipo, {6, 7}, image
// CHECK-MULTIARCH-ACTIONS: 9: dsymutil, {8}, dSYM
Driver/Darwin: Model dsymutil properly, as a separate action/tool kind which is added as the last output step, instead of just hacking it into the link step. - Among other things, this fixes dSYM generation when using multiple -arch options. llvm-svn: 105475
2010-06-05 02:28:41 +08:00
//
rename -ccc-host-triple into -target llvm-svn: 148582
2012-01-21 06:01:23 +08:00
// RUN: %clang -target x86_64-apple-darwin10 -ccc-print-bindings \
Driver/Darwin: Model dsymutil properly, as a separate action/tool kind which is added as the last output step, instead of just hacking it into the link step. - Among other things, this fixes dSYM generation when using multiple -arch options. llvm-svn: 105475
2010-06-05 02:28:41 +08:00
// RUN: -arch i386 -arch x86_64 %s -g 2> %t
// RUN: FileCheck -check-prefix=CHECK-MULTIARCH-BINDINGS < %t %s
//
// CHECK-MULTIARCH-BINDINGS: "x86_64-apple-darwin10" - "darwin::Lipo", inputs: [{{.*}}, {{.*}}], output: "a.out"
Driver: .dSYM suffix should be appended, not replace the existing suffix. llvm-svn: 107369
2010-07-01 09:36:31 +08:00
// CHECK-MULTIARCH-BINDINGS: # "x86_64-apple-darwin10" - "darwin::Dsymutil", inputs: ["a.out"], output: "a.out.dSYM"
Driver/Darwin: Model dsymutil properly, as a separate action/tool kind which is added as the last output step, instead of just hacking it into the link step. - Among other things, this fixes dSYM generation when using multiple -arch options. llvm-svn: 105475
2010-06-05 02:28:41 +08:00
// Check output name derivation.
//
rename -ccc-host-triple into -target llvm-svn: 148582
2012-01-21 06:01:23 +08:00
// RUN: %clang -target x86_64-apple-darwin10 -ccc-print-bindings \
Driver/Darwin: Model dsymutil properly, as a separate action/tool kind which is added as the last output step, instead of just hacking it into the link step. - Among other things, this fixes dSYM generation when using multiple -arch options. llvm-svn: 105475
2010-06-05 02:28:41 +08:00
// RUN: -o foo %s -g 2> %t
// RUN: FileCheck -check-prefix=CHECK-OUTPUT-NAME < %t %s
//
Pedantically rename all Tool subclasses to be nouns, not verbs. NFC Classes in Tools.h inherit ultimately from Tool, which is a noun, but subclasses of Tool were named for their operation, such as "Compile", wherein the constructor call "Compile(args...)" could be misconstrued as actually causing a compile to happen. Likewise various other methods were not harmonious with their effect, in that "BuildLinker()" returned a "new namespace::Link(...)" instead of a "new namespace::Linker(...)" which it now does. Exceptions: Clang and ClangAs are un-renamed. Those are their rightful names. And there is no particulary great way to name the "Lipo-er" and a few others. Differential Revision: http://reviews.llvm.org/D10595 llvm-svn: 240455
2015-06-24 04:42:09 +08:00
// CHECK-OUTPUT-NAME: "x86_64-apple-darwin10" - "darwin::Linker", inputs: [{{.*}}], output: "foo"
Driver/Darwin: Model dsymutil properly, as a separate action/tool kind which is added as the last output step, instead of just hacking it into the link step. - Among other things, this fixes dSYM generation when using multiple -arch options. llvm-svn: 105475
2010-06-05 02:28:41 +08:00
// CHECK-OUTPUT-NAME: "x86_64-apple-darwin10" - "darwin::Dsymutil", inputs: ["foo"], output: "foo.dSYM"
Driver/Darwin: Only run dsymutil when we are also compiling/assembling as part of the compilation. - <rdar://problem/8141387> clang is always invoking dsymutil llvm-svn: 107149
2010-06-30 00:38:33 +08:00
// Check that we only use dsymutil when needed.
//
// RUN: touch %t.o
rename -ccc-host-triple into -target llvm-svn: 148582
2012-01-21 06:01:23 +08:00
// RUN: %clang -target x86_64-apple-darwin10 -ccc-print-bindings \
Driver/Darwin: Only run dsymutil when we are also compiling/assembling as part of the compilation. - <rdar://problem/8141387> clang is always invoking dsymutil llvm-svn: 107149
2010-06-30 00:38:33 +08:00
// RUN: -o foo %t.o -g 2> %t
Replace 'grep foo | count 0' with 'not grep foo'. This avoids depending on pipefail not being used. llvm-svn: 185648
2013-07-04 23:22:16 +08:00
// RUN: not grep "Dsymutil" %t
Driver/Darwin: Dsymutil actions should put the dSYM adjacent to the output file. llvm-svn: 128292
2011-03-26 02:16:51 +08:00
// Check that we put the .dSYM in the right place.
rename -ccc-host-triple into -target llvm-svn: 148582
2012-01-21 06:01:23 +08:00
// RUN: %clang -target x86_64-apple-darwin10 -ccc-print-bindings \
Driver/Darwin: Dsymutil actions should put the dSYM adjacent to the output file. llvm-svn: 128292
2011-03-26 02:16:51 +08:00
// RUN: -o bar/foo %s -g 2> %t
// RUN: FileCheck -check-prefix=CHECK-LOCATION < %t %s
// CHECK-LOCATION: "x86_64-apple-darwin10" - "darwin::Dsymutil", inputs: ["bar/foo"], output: "bar/foo.dSYM"
Fix an assertion failure when invoking dsymutil. There is no bound architecture for the dsymutil action in the driver. Trying to check various properties of the target will cause an assertion failure because the target doesn't get initialized without a bound architecture. <rdar://problem/16111555> llvm-svn: 201830
2014-02-21 08:20:07 +08:00
// Check that we don't crash when translating arguments for dsymutil.
// RUN: %clang -m32 -arch x86_64 -g %s -###