5 Commits

Author	SHA1	Message	Date
Duncan P. N. Exon Smith	d5508bfe28	verify-uselistorder: Change the default -num-shuffles=5 ... Change the default for `-num-shuffles` to 5 and better document the algorithm in the header docs of `verify-uselistorder`. llvm-svn: 214419	2014-07-31 18:46:24 +00:00
Duncan P. N. Exon Smith	f58c944271	verify-uselistorder: Add RUN lines to cases in test/Assembly ... Add RUN line for `verify-uselistorder` to every test in `test/Assembly`, unless it's a negative check (assembler rejects it) or verification fails. There are three files that verification fails on (so I've left out the RUN lines): - 2002-08-22-DominanceProblem.ll - ConstantExprFold.ll - ConstantExprFoldCast.ll This is part of PR5680. llvm-svn: 214365	2014-07-31 00:10:27 +00:00
Bill Wendling	74351693ea	Modify the LLVM assembly output so that it uses references to represent function attributes. ... This makes the LLVM assembly look better. E.g.: define void @foo() #0 { ret void } attributes #0 = { nounwind noinline ssp } llvm-svn: 175605	2013-02-20 07:21:42 +00:00
Rafael Espindola	29e8317caa	Move unnamed_addr after the function arguments on Sabre's request. ... llvm-svn: 124209	2011-01-25 19:09:56 +00:00
Rafael Espindola	9f526bcf4d	First step in fixing PR8927: ... Add a unnamed_addr bit to global variables and functions. This will be used to indicate that the address is not significant and therefore the constant or function can be merged with others. If an optimization pass can show that an address is not used, it can set this. Examples of things that can have this set by the FE are globals created to hold string literals and C++ constructors. Adding unnamed_addr to a non-const global should have no effect unless an optimization can transform that global into a constant. Aliases are not allowed to have unnamed_addr since I couldn't figure out any use for it. llvm-svn: 123063	2011-01-08 16:42:36 +00:00