Skip to content

Remove getPointerElementType calls that can be removed without further support in master. #293

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 10 commits into from
Apr 30, 2025

Conversation

DutChen18
Copy link
Member

Several months of work in this PR.

@DutChen18 DutChen18 requested a review from yuri91 April 23, 2025 09:08
Copy link
Member

@yuri91 yuri91 left a comment

Choose a reason for hiding this comment

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

Looks good, but the CI failed in the clang tests.

Please investigate

@DutChen18
Copy link
Member Author

I see ASAN tests are still failing. I'm looking into it now.

LLVM sets the type of the this parameter of virtual method thunks to the
derived class. This was changed for Cheerp in
88d9836 and there are a dozen or so
commits after it to deal with crashes caused by this change. With opaque
pointers, the signature of these thunks won't be different anyways
(the this type will just be an opaque pointer), and going back to
upstream LLVM's behaviour allows us to get rid of some GPETs. This also
affects the type of a downcast instruction in the thunk, but I do not
think this matters much.
@DutChen18
Copy link
Member Author

Rebased on master.

@yuri91 yuri91 merged commit 737534b into master Apr 30, 2025
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants