[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug binutils/28602] binutils/testsuite/lib/binutils-common.exp: Support

From: i at maskray dot me
Subject: [Bug binutils/28602] binutils/testsuite/lib/binutils-common.exp: Support free-form shell commands and check patterns
Date: Thu, 18 Nov 2021 03:09:28 +0000


--- Comment #1 from Fangrui Song <i at maskray dot me> ---
>From https://maskray.me/blog/2021-08-08-toolchain-testing#split-file

In Aug 2020, I added `split-file` to llvm-project which allows you to place
multiple extra files in one file. It'd be nice if binutils has something

Use case A (organizing input of different formats (e.g. linker
script+assembly) in one file).

# RUN: split-file %s %t
# RUN: llvm-mc %t/asm -o %t.o
# RUN: ld.lld -T %t/lds %t.o -o %t
This is sometimes better than the %S/Inputs/ approach because the user
can see the auxiliary files immediately and don't have to open another file.

# asm
# lds

Use case B (for utilities which don't have built-in input splitting feature):

// RUN: split-file %s %t
// RUN: llc < %t/1.ll | FileCheck %s --check-prefix=CASE1
// RUN: llc < %t/2.ll | FileCheck %s --check-prefix=CASE2
Combing tests prudently can improve readability.
For example, when testing parsing errors if the recovery mechanism isn't
grouping the tests in one file can more readily see test coverage/strategy.

//--- 1.ll
//--- 2.ll

You are receiving this mail because:
You are on the CC list for the bug.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]