[all-commits] [llvm/llvm-project] ea8e02: [clang][IFS] Driver Pipeline: generate stubs after...

[Puyan Lotfi via All-commits]

  Branch: refs/heads/master
  Home:   https://github.com/llvm/llvm-project
  Commit: ea8e02822341e2421b94167d828d3f224e767424
      https://github.com/llvm/llvm-project/commit/ea8e02822341e2421b94167d828d3f224e767424
  Author: Puyan Lotfi <puyan at puyan.org>
  Date:   2019-11-19 (Tue, 19 Nov 2019)

  Changed paths:
    M clang/lib/Driver/Driver.cpp
    M clang/lib/Driver/ToolChains/InterfaceStubs.cpp
    M clang/lib/Driver/Types.cpp
    M clang/test/InterfaceStubs/driver-test.c
    A clang/test/InterfaceStubs/driver-test2.c
    A clang/test/InterfaceStubs/ppc.cpp
    M clang/test/InterfaceStubs/windows.cpp

  Log Message:
  -----------
  [clang][IFS] Driver Pipeline: generate stubs after standard pipeline (2)

Second Landing Attempt:

Up until now, clang interface stubs has replaced the standard
PP -> C -> BE -> ASM -> LNK pipeline. With this change, it will happen in
conjunction with it. So what when you build your code you will get an
a.out or lib.so as well as an interface stub file.

Example:

clang -shared -o libfoo.so -emit-interface-stubs ...

will generate both a libfoo.so and a libfoo.ifso. The .so file will
contain the code from the standard compilation pipeline and the .ifso
file will contain the ELF stub library.

Differential Revision: https://reviews.llvm.org/D70274