Skip to content

Conversation

yronglin
Copy link
Contributor

@yronglin yronglin commented Sep 4, 2023

No description provided.

Signed-off-by: yronglin <yronglin777@gmail.com>
@yronglin yronglin requested a review from a team as a code owner September 4, 2023 15:07
@philnik777 philnik777 added the clang Clang issues not falling into any other category label Sep 4, 2023
@yronglin yronglin added the clang:frontend Language frontend issues, e.g. anything involving "Sema" label Sep 4, 2023
@cor3ntin
Copy link
Contributor

cor3ntin commented Sep 4, 2023

This looks correct to me, but I'd like @sam-mccall to confirm that it was unintended.
Maybe we should keep the old code around as loops tend to share some code and we don't want if(!!;;) to crash either

Copy link
Collaborator

@sam-mccall sam-mccall left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

I don't have a strong opinion about keeping the old even-more-broken versions. They're not very likely, and we don't attempt to cover most things like that. A fuzzer is probably a better approach (we have one, it finds an ~infinite number of crashes).

@yronglin
Copy link
Contributor Author

yronglin commented Sep 5, 2023

Thanks a lot for your review! @sam-mccall @cor3ntin

@yronglin yronglin merged commit 111c1ba into llvm:main Sep 5, 2023
avillega pushed a commit to avillega/llvm-project that referenced this pull request Sep 11, 2023
Signed-off-by: yronglin <yronglin777@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
clang:frontend Language frontend issues, e.g. anything involving "Sema" clang Clang issues not falling into any other category
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants