This is an archive of the discontinued LLVM Phabricator instance.

ARM32 unwinding on EHABI has issues with static analysis
ClosedPublic

Authored by kant2002 on Aug 4 2021, 10:43 PM.

Details

Reviewers
compnerd
danielkiss
Group Reviewers
Restricted Project
Commits
rG08a5ac36b956: libunwind: add missing break statements in EHABI
Summary

Based on limited understanding these breaks just missing from the original submission time.

Diff Detail

Event Timeline

kant2002 created this revision.Aug 4 2021, 10:43 PM
Herald added 1 blocking reviewer(s): Restricted Project. · View Herald TranscriptAug 4 2021, 10:43 PM
kant2002 requested review of this revision.Aug 4 2021, 10:43 PM
Herald added a project: Restricted Project. · View Herald TranscriptAug 4 2021, 10:43 PM

change looks good but right now it always runs into the assert or failure. I'm wondering why nobody reported yet.
none of the existing tests in llvm runs into the outer while loop.

compnerd accepted this revision.Aug 5 2021, 9:43 AM
compnerd added a subscriber: compnerd.

That is rather surprising @danielkiss but I think that trying to figure out what happened there while getting this fixed is the better approach here.

This revision is now accepted and ready to land.Aug 5 2021, 9:43 AM

BTW, this might be a good thing to pull into the release branch (CC: @tstellar)

Can you create a bug for this?

danielkiss accepted this revision.Aug 5 2021, 9:57 AM

not against the fix just made me curious.

@kant2002 do you have commit rights or do you need someone to commit this on your behalf? @tstellar filled PR51393 to track.

@comnerd This is my first time contribution. So I assume that I do not have commit rights

@compnerd I first time made a mistake in you nickname. So I would repeat that that I do not have commit rights. And other question. Where I can look at bugs? I assume in bugzilla, and I should follow standard process described in docs. Correct?

You need to provide so that git commit --amend='name <email>' so that the commit can get proper attrition.

You didn't upload the patch via arc diff and the information is unavailable.

This revision was automatically updated to reflect the committed changes.

@kant2002 you should be able to see the bug at https://llvm.org/PR51393