search for: reducem

I'm not sure if this helps, but here it is in case it does. I typically use bugpoint in a way as to keep the actual failure that I'm after. For example, with the test case you've pasted, I was looking for a specific assert. So I used bugpoint this way: $ cat reduceme.sh #!/bin/bash llc -filetype=obj $1 2>&1 | grep 'Cannot lower calls with arbitrary operand bundles' RC=$? if [[ $RC -eq 0 ]] then exit 1 fi exit 0 $ bugpoint -compile-custom -compile-command=$PWD/reduceme.sh input.ll That will ensure that bugpoint retains the specific desired fa...

...'m not sure if this helps, but here it is in case it does. > > I typically use bugpoint in a way as to keep the actual failure that I'm > after. For example, with the test case you've pasted, I was looking for a > specific assert. So I used bugpoint this way: > > $ cat reduceme.sh > #!/bin/bash > llc -filetype=obj $1 2>&1 | grep 'Cannot lower calls with arbitrary operand > bundles' > RC=$? > if [[ $RC -eq 0 ]] > then > exit 1 > fi > exit 0 > > $ bugpoint -compile-custom -compile-command=$PWD/reduceme.sh input.ll > >...

Thank you both! I was running into the issue that bugpoint was reducing my test-case into other failures and I hadn't managed yet to find the right point in the Julia pass pipeline to insert the module to reproduce the issue reliably from llc and that's why I started looking at using the MIR. I will go back at looking at the pass pipeline and the IR and get a reproducer that way!

Valentin, in terms of limitations as Sean pointed out, an important one is that .mir doesn't have MachineFunctionInfo which may result in failure on accesses to global variables due to use of register X2. The verifier considers it an undefined register. Also, it's probably easier to reduce test cases using bugpoint starting from an IR test case. With the code you provided, I get a