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
Multiple symbol definitions for x86-32-windows #5649
Comments
The warning is generated by our code, here: Line 192 in 42c5182
|
My wild guess: Those symbols are vector constants, where the name of the symbol is the value of the constant (in order to not store the same constant more than once) |
This has been a recurring issue on Windows for us as well; @slomp might have more to say about it. AFAICT, it is exactly what Andrew says: constants are named after the value of the constant, so we end up with multiple symbols of the same name. We should either make the warning better at diagnosing real issues, or get rid of it. |
Yeap, this is a minor annoyance, and it's precisely due to what Andrew stated. |
In a larger build system this would unnecessarily alarm users not in the know. When would this warn about something not ignorable? If thats rare/benign could we remove this warning? |
Yes, if this is WAI we should disable the warning for sure. |
Compiling a multitarget generator with the following list of targets
produces several concerning warnings:
Replacing
32-windows
with64-windows
in the targets list does not generate these warnings.The text was updated successfully, but these errors were encountered: