Skip to content
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

Add pragma(LDC_no_moduleinfo) to all gccbuiltin generated .di files. #4443

Closed
wants to merge 3 commits into from

Conversation

JohanEngelen
Copy link
Member

Moduleinfo is not needed, because there are no module ctors, nor unittests, etc. This prevents missing Moduleinfo symbol linking problems for some use cases.

Resolves #4442

Moduleinfo is not needed, because there are no module ctors, nor unittests, etc.
This prevents missing Moduleinfo symbol linking problems for some use cases.
@ljmf00
Copy link
Contributor

ljmf00 commented Jul 17, 2023

Do we do the check the other way around? I think we only check for LDC_no_moduleinfo on creation but not on referencing. I read the code a bit and haven't seen a testcase that proves it.

I think this can be extended to any .di intrinsics.

@JohanEngelen
Copy link
Member Author

I think this can be extended to any .di intrinsics.

I'm a bit wary of just blanket removing moduleinfo without needing to do so. But I've removed it from ldc.profile too (that module is intentionally template-only and not linking into druntime).

@JohanEngelen JohanEngelen marked this pull request as draft September 5, 2023 19:35
@JohanEngelen
Copy link
Member Author

converted to draft, this actually does not fix issue #4442

@JohanEngelen
Copy link
Member Author

why draft, it's simple, this does not fix #4442

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.

LDC is trying to reference ModuleInfo from ldc.gccbuiltins and friends
2 participants