Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

pushprajnaik
Copy link

Edited printModule function.

Edited printModule function.
@repo-lockdown
Copy link

repo-lockdown bot commented Oct 2, 2020

This repository does not accept pull requests. Please follow http://llvm.org/docs/Contributing.html#how-to-submit-a-patch for contribution to LLVM.

@repo-lockdown repo-lockdown bot closed this Oct 2, 2020
@repo-lockdown repo-lockdown bot locked and limited conversation to collaborators Oct 2, 2020
@erichkeane erichkeane added the invalid Resolved as invalid, i.e. not a bug label Oct 2, 2020
@asl asl added the spam label Oct 3, 2020
pysuxing pushed a commit to pysuxing/llvm-project that referenced this pull request Jul 17, 2024
I think it's time to claim that CIR supports recursive types (many
thanks to llvm#303 and to @sitio-couto :) )
And we can bring back the `get_member` verification back, with no checks
for incomplete types. What do you think?

And we can close llvm#256 as well
pysuxing pushed a commit to pysuxing/llvm-project that referenced this pull request Jul 17, 2024
I think it's time to claim that CIR supports recursive types (many
thanks to llvm#303 and to @sitio-couto :) )
And we can bring back the `get_member` verification back, with no checks
for incomplete types. What do you think?

And we can close llvm#256 as well
keryell pushed a commit to keryell/llvm-project that referenced this pull request Oct 19, 2024
I think it's time to claim that CIR supports recursive types (many
thanks to llvm#303 and to @sitio-couto :) )
And we can bring back the `get_member` verification back, with no checks
for incomplete types. What do you think?

And we can close llvm#256 as well
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
invalid Resolved as invalid, i.e. not a bug
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants