This is an archive of the discontinued LLVM Phabricator instance.

[update_llc_test_checks] Handle mixed asm and ISel debug output
AcceptedPublic

Authored by arichardson on May 10 2022, 4:04 AM.

Details

Summary

I noticed a potentially uninitialized variable warning after D119368.
While this is a false(-ish) positive warning, it did highlight that the
output_type variable was being set based on the last RUN line, so mixed
ISel and ASM checks will not work. This commit allows mixed ISel and ASM
output and also fixes the IntelliJ warning. I have deleted the
add_checks() function from isel.py as it is identical to the one in asm.py
and restored the old name (which fixes the formatting too).

Diff Detail

Event Timeline

arichardson created this revision.May 10 2022, 4:04 AM
Herald added a project: Restricted Project. · View Herald TranscriptMay 10 2022, 4:04 AM
arichardson requested review of this revision.May 10 2022, 4:04 AM
Herald added a project: Restricted Project. · View Herald TranscriptMay 10 2022, 4:04 AM

Thank you so much for the improvements, Alexander! It would be nice to support isel and asm at the same time. Although I do have a few questions and one concern with regard to an ongoing change of mine.

I noticed a potentially uninitialized variable warning after D119368.

Would you mind pointing me to that warning? Is it complaining about output_type? And after your change the warning is gone? That does sound quite false positive-ish...

I have deleted the add_checks() function from isel.py as it is identical to the one in asm.py

Please don't delete that add_checks() function yet. It is only identical to the one in asm.py because we are still working on it... I have a review D122824 in progress (Sorry this one took a bit too long for me to get back to it, but I do plan to get back to it in the next few days.)

restored the old name (which fixes the formatting too)

Did the warning complained about the naming as well? I am quite confused here. Is it the fact that this line was using output_type that caused the warning or the function name add_checks() has cause the warning? What is the motivation for changing back the name here? Is it because the add_checks() in isel.py is removed so we prefer the old name?

Thanks for the improvement of the feature and thanks in advance for your patience with all my questions. :)

Thank you so much for the improvements, Alexander! It would be nice to support isel and asm at the same time. Although I do have a few questions and one concern with regard to an ongoing change of mine.

I noticed a potentially uninitialized variable warning after D119368.

Would you mind pointing me to that warning? Is it complaining about output_type? And after your change the warning is gone? That does sound quite false positive-ish...

I have deleted the add_checks() function from isel.py as it is identical to the one in asm.py

Please don't delete that add_checks() function yet. It is only identical to the one in asm.py because we are still working on it... I have a review D122824 in progress (Sorry this one took a bit too long for me to get back to it, but I do plan to get back to it in the next few days.)

Ah I didn't see that one. For mixed ISel and non-ISel output this will need a different approach though since the correct prefix depends on the current RUN: line.

restored the old name (which fixes the formatting too)

Did the warning complained about the naming as well? I am quite confused here. Is it the fact that this line was using output_type that caused the warning or the function name add_checks() has cause the warning? What is the motivation for changing back the name here? Is it because the add_checks() in isel.py is removed so we prefer the old name?

No warning here, I just noticed that the function call line continuations were no longer aligned after you renamed the function. I'll make a suggestion on that review.

Thanks for the improvement of the feature and thanks in advance for your patience with all my questions. :)

Matt added a subscriber: Matt.Aug 9 2022, 11:02 PM
sebastian-ne accepted this revision.Aug 16 2022, 5:33 AM
This revision is now accepted and ready to land.Aug 16 2022, 5:33 AM