Changes in print-shift.ll

a6241a5d - [AVR] Remove unneeded XFAILs from the Generic CodeGen tests

Sun, 20 Jan 2019 11:16:58 +0000

[AVR] Remove unneeded XFAILs from the Generic CodeGen testsThese have been in place for quite a while now.Several bugs have since been fixed, and these tests now pass.llvm-svn: 351679 List of files: /llvm-project-15.0.7/llvm/test/CodeGen/Generic/print-shift.ll

5c8a50bd - [AVR] Add/remove XFAILs to get the backend passing Generic CodeGen tests

Sun, 16 Jul 2017 23:33:50 +0000

[AVR] Add/remove XFAILs to get the backend passing Generic CodeGen testsA few tests have since been fixed, and a few since now fail.llvm-svn: 308151 List of files: /llvm-project-15.0.7/llvm/test/CodeGen/Generic/print-shift.ll

23af6484 - [opaque pointer type] Add textual IR support for explicit type parameter to the call instruction

Thu, 16 Apr 2015 23:24:18 +0000

[opaque pointer type] Add textual IR support for explicit type parameter to the call instructionSee r230786 and r230794 for similar changes to gep and loadrespectively.Call is a bit different because it often doesn't have a single explicittype - usually the type is deduced from the arguments, and just thereturn type is explicit. In those cases there's no need to change theIR.When that's not the case, the IR usually contains the pointer type ofthe first operand - but since typed pointers are going away, thatrepresentation is insufficient so I'm just stripping the "pointerness"of the explicit type away.This does make the IR a bit weird - it /sort of/ reads like the type ofthe first operand: "call void () %x(" but %x is actually of type "void()*" and will eventually be just of type "ptr". But this seems not toobad and I don't think it would benefit from repeating the type("void (), void () * %x(" and then eventually "void (), ptr %x(") as hasbeen done with gep and load.This also has a side benefit: since the explicit type is no longer apointer, there's no ambiguity between an explicit type and a functionthat returns a function pointer. Previously this case needed an explicittype (eg: a function returning a void() function was written as"call void () () * @x(" rather than "call void () * @x(" because of theambiguity between a function returning a pointer to a void() functionand a function returning void).No ambiguity means even function pointer return types can just bewritten alone, without writing the whole function's type.This leaves /only/ the varargs case where the explicit type is required.Given the special type syntax in call instructions, the regex-fu usedfor migration was a bit more involved in its own unique way (as everyone of these is) so here it is. Use it in conjunction with the apply.shscript and associated find/xargs commands I've provided in rr230786 tomigrate your out of tree tests. Do let me know if any of this doesn'tcover your cases & we can iterate on a more general script/regexes tohelp others with out of tree tests.About 9 test cases couldn't be automatically migrated - half of thosewere functions returning function pointers, where I just had to manuallydelete the function argument types now that we didn't need an explicitfunction type there. The other half were typedefs of function types usedin calls - just had to manually drop the * from those.import fileinputimport sysimport repat = re.compile(r'((?:=|:|^|\s)call\s(?:[^@]*?))(\s*$|\s*(?:(?:\[\[[a-zA-Z0-9_]+\]\]|[@%](?:(")?[\\\?@a-zA-Z0-9_.]*?(?(3)"|)|{{.*}}))(?:$|$)|undef|inttoptr|bitcast|null|asm).*$)')addrspace_end = re.compile(r"addrspace\(\d+$\s*\*$")func_end = re.compile("(?:void.*|\)\s*)\*$")def conv(match, line): if not match or re.search(addrspace_end, match.group(1)) or not re.search(func_end, match.group(1)): return line return line[:match.start()] + match.group(1)[:match.group(1).rfind('*')].rstrip() + match.group(2) + line[match.end():]for line in sys.stdin: sys.stdout.write(conv(re.search(pat, line), line))llvm-svn: 235145 List of files: /llvm-project-15.0.7/llvm/test/CodeGen/Generic/print-shift.ll

a79ac14f - [opaque pointer type] Add textual IR support for explicit type parameter to load instruction

Fri, 27 Feb 2015 21:17:42 +0000

[opaque pointer type] Add textual IR support for explicit type parameter to load instructionEssentially the same as the GEP change in r230786.A similar migration script can be used to update test cases, though a few moretest case improvements/changes were required this time around: (r229269-r229278)import fileinputimport sysimport repat = re.compile(r"((?:=|:|^)\s*load (?:atomic )?(?:volatile )?(.*?))(| addrspace$\d+$ *)\*($| *(?:%|@|null|undef|blockaddress|getelementptr|addrspacecast|bitcast|inttoptr|\[\[[a-zA-Z]|\{\{).*$)")for line in sys.stdin: sys.stdout.write(re.sub(pat, r"\1, \2\3*\4", line))Reviewers: rafael, dexonsmith, grosserDifferential Revision: http://reviews.llvm.org/D7649llvm-svn: 230794 List of files: /llvm-project-15.0.7/llvm/test/CodeGen/Generic/print-shift.ll

79e6c749 - [opaque pointer type] Add textual IR support for explicit type parameter to getelementptr instruction

Fri, 27 Feb 2015 19:29:02 +0000

[opaque pointer type] Add textual IR support for explicit type parameter to getelementptr instructionOne of several parallel first steps to remove the target type of pointers,replacing them with a single opaque pointer type.This adds an explicit type parameter to the gep instruction so that when thefirst parameter becomes an opaque pointer type, the type to gep through isstill available to the instructions.* This doesn't modify gep operators, only instructions (operators will be handled separately)* Textual IR changes only. Bitcode (including upgrade) and changing the in-memory representation will be in separate changes.* geps of vectors are transformed as: getelementptr <4 x float*> %x, ... ->getelementptr float, <4 x float*> %x, ... Then, once the opaque pointer type is introduced, this will ultimately look like: getelementptr float, <4 x ptr> %x with the unambiguous interpretation that it is a vector of pointers to float.* address spaces remain on the pointer, not the type: getelementptr float addrspace(1)* %x ->getelementptr float, float addrspace(1)* %x Then, eventually: getelementptr float, ptr addrspace(1) %xImportantly, the massive amount of test case churn has been automated bysame crappy python code. I had to manually update a few test cases thatwouldn't fit the script's model (r228970,r229196,r229197,r229198). Thepython script just massages stdin and writes the result to stdout, Ithen wrapped that in a shell script to handle replacing files, thenusing the usual find+xargs to migrate all the files.update.py:import fileinputimport sysimport reibrep = re.compile(r"(^.*?[^%\w]getelementptr inbounds )(((?:<\d* x )?)(.*?)(| addrspace$\d$) *\*(|>)(?:$| *(?:%|@|null|undef|blockaddress|getelementptr|addrspacecast|bitcast|inttoptr|\[\[[a-zA-Z]|\{\{).*$))")normrep = re.compile( r"(^.*?[^%\w]getelementptr )(((?:<\d* x )?)(.*?)(| addrspace$\d$) *\*(|>)(?:$| *(?:%|@|null|undef|blockaddress|getelementptr|addrspacecast|bitcast|inttoptr|\[\[[a-zA-Z]|\{\{).*$))")def conv(match, line): if not match: return line line = match.groups()[0] if len(match.groups()[5]) == 0: line += match.groups()[2] line += match.groups()[3] line += ", " line += match.groups()[1] line += "\n" return linefor line in sys.stdin: if line.find("getelementptr ") == line.find("getelementptr inbounds"): if line.find("getelementptr inbounds") != line.find("getelementptr inbounds ("): line = conv(re.match(ibrep, line), line) elif line.find("getelementptr ") != line.find("getelementptr ("): line = conv(re.match(normrep, line), line) sys.stdout.write(line)apply.sh:for name in "$@"do python3 `dirname "$0"`/update.py < "$name" > "$name.tmp" && mv "$name.tmp" "$name" rm -f "$name.tmp"doneThe actual commands:From llvm/src:find test/ -name *.ll | xargs ./apply.shFrom llvm/src/tools/clang:find test/ -name *.mm -o -name *.m -o -name *.cpp -o -name *.c | xargs -I '{}' ../../apply.sh "{}"From llvm/src/tools/polly:find test/ -name *.ll | xargs ./apply.shAfter that, check-all (with llvm, clang, clang-tools-extra, lld,compiler-rt, and polly all checked out).The extra 'rm' in the apply.sh script is due to a few files in clang's testsuite using interesting unicode stuff that my python script was throwingexceptions on. None of those files needed to be migrated, so it seemedsufficient to ignore those cases.Reviewers: rafael, dexonsmith, grosserDifferential Revision: http://reviews.llvm.org/D7636llvm-svn: 230786 List of files: /llvm-project-15.0.7/llvm/test/CodeGen/Generic/print-shift.ll

c8054d90 - Eliminate more uses of llvm-as and llvm-dis.

Wed, 09 Sep 2009 00:09:15 +0000

Eliminate more uses of llvm-as and llvm-dis.llvm-svn: 81293 List of files: /llvm-project-15.0.7/llvm/test/CodeGen/Generic/print-shift.ll

3f04773f - Remove llvm-upgrade and update tests.

Tue, 19 Feb 2008 01:41:04 +0000

Remove llvm-upgrade and update tests.llvm-svn: 47296 List of files: /llvm-project-15.0.7/llvm/test/CodeGen/Generic/print-shift.ll

83b3d826 - Regression is gone, don't try to find it on clean target.

Wed, 17 Jan 2007 07:59:14 +0000

Regression is gone, don't try to find it on clean target.llvm-svn: 33296 List of files: /llvm-project-15.0.7/llvm/test/CodeGen/Generic/print-shift.ll