maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity
llvm-project/flang/test/Driver/emit-asm-from-llvm-bc.ll

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

21 lines
548 B
LLVM
Raw Normal View History

[flang] Fix triple in a couple of driver tests In https://reviews.llvm.org/D124667, I added tests that check the generated assembly. I verified the assembly on AArch64 and X86_64, but the PPC Flang buildbot [1] started failing (i.e. the assembly was not generic enough). In order to fix this, I'm changing these tests to be only run on AAarch64 - that's the architecture that most of public Flang buildbots use. I'm hoping that this is straightforward enough and am merging it without a review. [1] https://lab.llvm.org/buildbot/#/builders/21/builds/40256
2022-05-06 00:35:59 +08:00
; Verify that the driver can consume LLVM BC files.
; REQUIRES: aarch64-registered-target
[flang][driver] Add support for consuming LLVM IR/BC files This change makes sure that Flang's driver recognises LLVM IR and BC as supported file formats. To this end, `isFortran` is extended and renamed as `isSupportedByFlang` (the latter better reflects the new functionality). New tests are added to verify that the target triple is correctly overridden by the frontend driver's default value or the value specified with `-triple`. Strictly speaking, this is not a functionality that's new in this patch (it was added in D124664). This patch simply enables us to write such tests and hence I'm including them here. Differential Revision: https://reviews.llvm.org/D124667
2022-04-22 17:07:31 +08:00
; RUN: rm -f %t.bc
[flang] Fix triple in a couple of driver tests In https://reviews.llvm.org/D124667, I added tests that check the generated assembly. I verified the assembly on AArch64 and X86_64, but the PPC Flang buildbot [1] started failing (i.e. the assembly was not generic enough). In order to fix this, I'm changing these tests to be only run on AAarch64 - that's the architecture that most of public Flang buildbots use. I'm hoping that this is straightforward enough and am merging it without a review. [1] https://lab.llvm.org/buildbot/#/builders/21/builds/40256
2022-05-06 00:35:59 +08:00
; RUN: %flang_fc1 -triple aarch64-unknown-linux-gnu -emit-llvm-bc %s -o %t.bc
; RUN: %flang_fc1 -S -triple aarch64-unknown-linux-gnu -o - %t.bc | FileCheck %s
[flang][driver] Add support for consuming LLVM IR/BC files This change makes sure that Flang's driver recognises LLVM IR and BC as supported file formats. To this end, `isFortran` is extended and renamed as `isSupportedByFlang` (the latter better reflects the new functionality). New tests are added to verify that the target triple is correctly overridden by the frontend driver's default value or the value specified with `-triple`. Strictly speaking, this is not a functionality that's new in this patch (it was added in D124664). This patch simply enables us to write such tests and hence I'm including them here. Differential Revision: https://reviews.llvm.org/D124667
2022-04-22 17:07:31 +08:00
; RUN: rm -f %t.bc
; RUN: rm -f %t.bc
[flang] Fix triple in a couple of driver tests In https://reviews.llvm.org/D124667, I added tests that check the generated assembly. I verified the assembly on AArch64 and X86_64, but the PPC Flang buildbot [1] started failing (i.e. the assembly was not generic enough). In order to fix this, I'm changing these tests to be only run on AAarch64 - that's the architecture that most of public Flang buildbots use. I'm hoping that this is straightforward enough and am merging it without a review. [1] https://lab.llvm.org/buildbot/#/builders/21/builds/40256
2022-05-06 00:35:59 +08:00
; RUN: %flang -c -target aarch64-unknown-linux-gnu -emit-llvm %s -o %t.bc
; RUN: %flang -S -target aarch64-unknown-linux-gnu -o - %t.bc | FileCheck %s
[flang][driver] Add support for consuming LLVM IR/BC files This change makes sure that Flang's driver recognises LLVM IR and BC as supported file formats. To this end, `isFortran` is extended and renamed as `isSupportedByFlang` (the latter better reflects the new functionality). New tests are added to verify that the target triple is correctly overridden by the frontend driver's default value or the value specified with `-triple`. Strictly speaking, this is not a functionality that's new in this patch (it was added in D124664). This patch simply enables us to write such tests and hence I'm including them here. Differential Revision: https://reviews.llvm.org/D124667
2022-04-22 17:07:31 +08:00
; RUN: rm -f %t.bc
; CHECK-LABEL: foo:
; CHECK: ret
define void @foo() {
ret void
}