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

comdat mismatches win32 #11

Open
callumenator opened this issue Aug 5, 2014 · 1 comment
Open

comdat mismatches win32 #11

callumenator opened this issue Aug 5, 2014 · 1 comment

Comments

@callumenator
Copy link

Using ylink under win32 I keep getting comdat mismatch errors with symbols in phobos (https://github.com/yebblies/ylink/blob/master/symboltable.d#L84). I'm building dmd/phobos from git master.

I can get it to run properly by not throwing if either of the conflicting symbols is Comdat.Any, but I'm not sure what the standard behaviour is meant to be regarding multiple symbols if one of them is marked Unique (i.e. should the linker throw a multiple definition error even if the other symbol is marked Any?).

@yebblies
Copy link
Owner

yebblies commented Aug 5, 2014

The real question is - why on earth is _D3std5stdio8__assertFiZv (in the test I just did) coming out as Comdat.Unique?

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

No branches or pull requests

2 participants