aboutsummaryrefslogtreecommitdiff
path: root/llvm/lib/Bitcode/Writer/BitcodeWriter.cpp
diff options
context:
space:
mode:
authorFangrui Song <i@maskray.me>2022-06-29 01:06:01 -0700
committerFangrui Song <i@maskray.me>2022-06-29 01:06:01 -0700
commit9d4a2baaa2c304066199ec6644da80aca7638dc6 (patch)
tree4d98d302452b925af7fd93857ea8cce71551320b /llvm/lib/Bitcode/Writer/BitcodeWriter.cpp
parent348ea34bcdbd4c62dd9b41cb05c7081f530f39cc (diff)
downloadllvm-9d4a2baaa2c304066199ec6644da80aca7638dc6.zip
llvm-9d4a2baaa2c304066199ec6644da80aca7638dc6.tar.gz
llvm-9d4a2baaa2c304066199ec6644da80aca7638dc6.tar.bz2
[flang][test] Remove RUN COMMANDS/EXPECTED OUTPUT/INPUT markers from test/Driver
Uses of these markers are contrary to all other llvm-project subprojects and carry no information for people who know the basics of a lit test. I understand that there is an argument "this makes beginners get started quickly" but I am unsure whether this is strong enough to deviate from all other projects. https://llvm.org/docs/TestingGuide.html covers the basics. Actually, some contributors were confused by the markers. Differential Revision: https://reviews.llvm.org/D128763
Diffstat (limited to 'llvm/lib/Bitcode/Writer/BitcodeWriter.cpp')
0 files changed, 0 insertions, 0 deletions