llvm-project/llvm/test/Feature
Eli Friedman 4532a50899 Infer alignment of unmarked loads in IR/bitcode parsing.
For IR generated by a compiler, this is really simple: you just take the
datalayout from the beginning of the file, and apply it to all the IR
later in the file. For optimization testcases that don't care about the
datalayout, this is also really simple: we just use the default
datalayout.

The complexity here comes from the fact that some LLVM tools allow
overriding the datalayout: some tools have an explicit flag for this,
some tools will infer a datalayout based on the code generation target.
Supporting this properly required plumbing through a bunch of new
machinery: we want to allow overriding the datalayout after the
datalayout is parsed from the file, but before we use any information
from it. Therefore, IR/bitcode parsing now has a callback to allow tools
to compute the datalayout at the appropriate time.

Not sure if I covered all the LLVM tools that want to use the callback.
(clang? lli? Misc IR manipulation tools like llvm-link?). But this is at
least enough for all the LLVM regression tests, and IR without a
datalayout is not something frontends should generate.

This change had some sort of weird effects for certain CodeGen
regression tests: if the datalayout is overridden with a datalayout with
a different program or stack address space, we now parse IR based on the
overridden datalayout, instead of the one written in the file (or the
default one, if none is specified). This broke a few AVR tests, and one
AMDGPU test.

Outside the CodeGen tests I mentioned, the test changes are all just
fixing CHECK lines and moving around datalayout lines in weird places.

Differential Revision: https://reviews.llvm.org/D78403
2020-05-14 13:03:50 -07:00
..
OperandBundles Add, and infer, a nofree function attribute 2019-07-08 15:57:56 +00:00
NamedMDNode.ll
NamedMDNode2.ll
README.txt
alias2.ll
aliases.ll
alignment.ll
attributes.ll
basictest.ll
callingconventions.ll
calltest.ll
casttest.ll
cfgstructures.ll
cold.ll
comdat.ll
const_pv.ll
constexpr.ll
constpointer.ll
elf-deplibs.ll [ELF] Implement Dependent Libraries Feature 2019-05-17 03:44:15 +00:00
elf-linker-options.ll
escaped_label.ll
exception.ll
float.ll
fold-fpcast.ll
forwardreftest.ll
fp-intrinsics.ll This adds constrained intrinsics for the signed and unsigned conversions 2019-12-17 10:06:51 -05:00
global_pv.ll [IR] Disallow llvm.global_ctors and llvm.global_dtors of the 2-field form in textual format 2019-05-15 02:35:32 +00:00
global_section.ll
globalredefinition3.ll
globalvars.ll
indirectcall.ll
indirectcall2.ll
inlineasm.ll
instructions.ll
intrinsic-noduplicate.ll
intrinsics.ll [FunctionAttrs] Annotate "willreturn" for intrinsics 2019-07-28 06:09:56 +00:00
load_extension.ll [examples] Skip building the Bye pass plugin on windows 2020-05-13 13:40:56 +03:00
load_module.ll [Bugpoint] Only run plugins tests if plugins are enabled 2019-05-17 06:41:04 +00:00
md_on_instruction.ll Infer alignment of unmarked loads in IR/bitcode parsing. 2020-05-14 13:03:50 -07:00
memorymarkers.ll
metadata.ll
minsize_attr.ll
newcasts.ll
optnone-llc.ll
optnone-opt.ll [LoopExtractor] Convert LoopExtractor from LoopPass to ModulePass 2020-02-09 12:25:21 +02:00
optnone.ll
packed.ll
packed_struct.ll
paramattrs.ll
ppcld.ll
prefixdata.ll
prologuedata.ll
properties.ll
prototype.ll
recursivetype.ll
seh-nounwind.ll
simplecalltest.ll
small.ll
smallest.ll
sparcld.ll
strip_names.ll IR: print value numbers for unnamed function arguments 2019-08-03 14:28:34 +00:00
terminators.ll
testalloca.ll
testconstants.ll
testlogical.ll
testtype.ll
testvarargs.ll
undefined.ll [IR] Keep a double break between functions when printing a module 2020-01-27 15:31:09 -08:00
unreachable.ll
varargs.ll
varargs_new.ll
vector-cast-constant-exprs.ll
weak_constant.ll Temporarily Revert "[SLP] allow forming 2-way reduction patterns" and update testcases. 2019-11-20 16:00:53 -08:00
weirdnames.ll
x86ld.ll

README.txt

This directory contains test cases for individual source features of LLVM.
It is designed to make sure that the major components of LLVM support all of the
features of LLVM, for very small examples.  Entire programs should not go here.

Regression tests for individual bug fixes should go into the test/Regression dir.