Changes in basic.ll

a87f618e - [PlaceSafepoints] Pin tests to legacy PM

Mon, 26 Oct 2020 20:21:39 +0000

[PlaceSafepoints] Pin tests to legacy PMThis pass isn't used in tree and can be ported to the NPM later on if desired.Differential Revision: https://reviews.llvm.org/D90189 List of files: /llvm-project-15.0.7/llvm/test/Transforms/PlaceSafepoints/basic.ll

cee313d2 - Revert "Temporarily Revert "Add basic loop fusion pass.""

Wed, 17 Apr 2019 04:52:47 +0000

Revert "Temporarily Revert "Add basic loop fusion pass.""The reversion apparently deleted the test/Transforms directory.Will be re-reverting again.llvm-svn: 358552 List of files: /llvm-project-15.0.7/llvm/test/Transforms/PlaceSafepoints/basic.ll

f7302c8b - [PlaceSafepoints] Clamp NoStatepoints to true

Thu, 28 Jan 2016 21:51:14 +0000

[PlaceSafepoints] Clamp NoStatepoints to trueThis change permanently clamps -spp-no-statepoints to true (the codedeletion will come later). Tests that specifically testedPlaceSafepoint's ability to wrap calls in gc.statepoint have been movedto RS4GC's test suite.llvm-svn: 259096 List of files: /llvm-project-15.0.7/llvm/test/Transforms/PlaceSafepoints/basic.ll

2321a4cd - [PlaceSafepoints] Clean up tests; NFC

Thu, 28 Jan 2016 18:01:03 +0000

[PlaceSafepoints] Clean up tests; NFCUse `opt < %s` instead of `opt %s` as specified inhttp://llvm.org/docs/TestingGuide.html#fragile-tests.llvm-svn: 259062 List of files: /llvm-project-15.0.7/llvm/test/Transforms/PlaceSafepoints/basic.ll

d1beb07d - Have a single way for creating unique value names.

Sun, 22 Nov 2015 00:16:24 +0000

Have a single way for creating unique value names.We had two code paths. One would create names like "foo.1" and the othernames like "foo1".For globals it is important to use "foo.1" to help C++ name demangling.For locals there is no strong reason to go one way or the other so Ikept the most common mangling (foo1).llvm-svn: 253804 List of files: /llvm-project-15.0.7/llvm/test/Transforms/PlaceSafepoints/basic.ll

a1d39ba9 - [Statepoints] Support for "patchable" statepoints.

Tue, 12 May 2015 23:52:24 +0000

[Statepoints] Support for "patchable" statepoints.Summary:This change adds two new parameters to the statepoint intrinsic, `i64 id`and `i32 num_patch_bytes`. `id` gets propagated to the ID fieldin the generated StackMap section. If the `num_patch_bytes` isnon-zero then the statepoint is lowered to `num_patch_bytes` bytes ofnops instead of a call (the spill and reload code remains unchanged).A non-zero `num_patch_bytes` is useful in situations where a languageruntime requires complete control over how a call is lowered.This change brings statepoints one step closer to patchpoints. Withsome additional work (that is not part of this patch) it should bepossible to get rid of `TargetOpcode::STATEPOINT` altogether.PlaceSafepoints generates `statepoint` wrappers with `id` set to`0xABCDEF00` (the old default value for the ID reported in the stackmap)and `num_patch_bytes` set to `0`. This can be made more sophisticatedlater.Reviewers: reames, pgavlin, swaroop.sridhar, AndyAyersSubscribers: llvm-commitsDifferential Revision: http://reviews.llvm.org/D9546llvm-svn: 237214 List of files: /llvm-project-15.0.7/llvm/test/Transforms/PlaceSafepoints/basic.ll

d79dfcbc - Changed renaming of local symbols by inserting a dot vefore the numeric suffix.

Tue, 12 May 2015 16:47:30 +0000

Changed renaming of local symbols by inserting a dot vefore the numeric suffix.One code change and several test changes to match thatdetails in http://reviews.llvm.org/D9481llvm-svn: 237150 List of files: /llvm-project-15.0.7/llvm/test/Transforms/PlaceSafepoints/basic.ll

cc0431d1 - Extend the statepoint intrinsic to allow statepoints to be marked as transitions from GC-aware code to code that is not GC-aware.

Fri, 08 May 2015 18:07:42 +0000

Extend the statepoint intrinsic to allow statepoints to be marked as transitions from GC-aware code to code that is not GC-aware.This changes the shape of the statepoint intrinsic from: @llvm.experimental.gc.statepoint(anyptr target, i32 # call args, i32 unused, ...call args, i32 # deopt args, ...deopt args, ...gc args)to: @llvm.experimental.gc.statepoint(anyptr target, i32 # call args, i32 flags, ...call args, i32 # transition args, ...transition args, i32 # deopt args, ...deopt args, ...gc args)This extension offers the backend the opportunity to insert (somewhat) arbitrary code to manage the transition from GC-aware code to code that is not GC-aware and back.In order to support the injection of transition code, this extension wraps the STATEPOINT ISD node generated by the usual lowering lowering with two additional nodes: GC_TRANSITION_START and GC_TRANSITION_END. The transition arguments that were passed passed to the intrinsic (if any) are lowered and provided as operands to these nodes and may be used by the backend during code generation.Eventually, the lowering of the GC_TRANSITION_{START,END} nodes should be informed by the GC strategy in use for the function containing the intrinsic call; for now, these nodes are instead replaced with no-ops.Differential Revision: http://reviews.llvm.org/D9501llvm-svn: 236888 List of files: /llvm-project-15.0.7/llvm/test/Transforms/PlaceSafepoints/basic.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/Transforms/PlaceSafepoints/basic.ll

3408f3e2 - PlaceSafepoints: use IRBuilder helpers

Thu, 26 Feb 2015 00:35:56 +0000

PlaceSafepoints: use IRBuilder helpersUse the IRBuilder helpers for gc.statepoint and gc.result, instead ofcoding the construction by hand. Note that the gc.statepoint IRBuilderhandles only CallInst, not InvokeInst; retain that part of hand-coding.Differential Revision: http://reviews.llvm.org/D7518llvm-svn: 230591 List of files: /llvm-project-15.0.7/llvm/test/Transforms/PlaceSafepoints/basic.ll

0b1b3874 - [PlaceSafepoints] Adjust enablement logic to default to off and be GC configurable per GC

Sat, 21 Feb 2015 00:09:09 +0000

[PlaceSafepoints] Adjust enablement logic to default to off and be GC configurable per GCPreviously, this pass ran over every function in the Module if added to the pass order. With this change, it runs only over those with a GC attribute where the GC explicitly opts in. A GC can also choose which of entry safepoint polls, backedge safepoint polls, and call safepoints it wants. I hope to get these exposed as checks on the GCStrategy at some point, but for now, the checks are manual string comparisons.llvm-svn: 230097 List of files: /llvm-project-15.0.7/llvm/test/Transforms/PlaceSafepoints/basic.ll

2e4b9e0a - PlaceSafepoints: modernize gc.result.* -> gc.result

Mon, 09 Feb 2015 23:00:40 +0000

PlaceSafepoints: modernize gc.result.* -> gc.resultDifferential Revision: http://reviews.llvm.org/D7516llvm-svn: 228625 List of files: /llvm-project-15.0.7/llvm/test/Transforms/PlaceSafepoints/basic.ll

5fc82fd6 - Minor test cleanup

Mon, 09 Feb 2015 21:50:31 +0000

Minor test cleanupa) add gc attributeb) remove unused paramllvm-svn: 228612 List of files: /llvm-project-15.0.7/llvm/test/Transforms/PlaceSafepoints/basic.ll

b1ed02f7 - Add basic tests for PlaceSafepoints

Mon, 09 Feb 2015 21:48:05 +0000

Add basic tests for PlaceSafepointsThis is just adding really simple tests which should have been part of the original submission. When doing so, I discovered that I'd mistakenly removed required pieces when preparing the patch for upstream submission. I fixed two such bugs in this submission.llvm-svn: 228610 List of files: /llvm-project-15.0.7/llvm/test/Transforms/PlaceSafepoints/basic.ll