-
Notifications
You must be signed in to change notification settings - Fork 243
Linkage type fix for global variables translation #1148
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
Conversation
This is a workaround to fix translation of linkage type of "llvm.used" and "llvm.compiler.used" global variables that should be "appending" instead of "export".
@AlexeySotkin @AlexeySachkov @mlychkov @MrSidims please take a look |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, but one nit about the test.
; CHECK-LLVM: @llvm.compiler.used = appending global | ||
@llvm.compiler.used = appending global [1 x i8*] [i8* bitcast (%union.int_double addrspace(1)** @._c0.ref to i8*)] #0 | ||
|
||
attributes #0 = { "VCGlobalVariable" } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We can translate it to SPIR-V without any extensions if we remove this attribute. We don't need it for the purpose of this test, right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, we need it. I tried to remove this attribute and then translate, but @llvm.compiler.used also disappeared. But I found extensions, which are needed to translate this test insted of all.
This is a workaround to fix translation of linkage type of "llvm.used" and "llvm.compiler.used" global variables that should be "appending" instead of "export".
This is a workaround to fix translation of linkage type of "llvm.used" and "llvm.compiler.used" global variables that should be "appending" instead of "export".
This is a workaround to fix translation of linkage type of "llvm.used" and "llvm.compiler.used" global variables that should be "appending" instead of "export".
This is a workaround to fix translation of linkage type of "llvm.used" and "llvm.compiler.used" global variables that should be "appending" instead of "export".
This is a workaround to fix translation of linkage type of "llvm.used" and "llvm.compiler.used" global variables that should be "appending" instead of "export".
This is a workaround to fix translation of linkage type of "llvm.used" and "llvm.compiler.used" global variables that should be "appending" instead of "export".
This is a workaround to fix translation of linkage type of "llvm.used" and "llvm.compiler.used" global variables that should be "appending" instead of "export".
This is a workaround to fix translation of linkage type of "llvm.used" and "llvm.compiler.used" global variables that should be "appending" instead of "export".
This is a workaround to fix translation of linkage type of "llvm.used" and "llvm.compiler.used" global variables that should be "appending" instead of "export".
This is a workaround to fix translation of linkage type of "llvm.used" and "llvm.compiler.used" global variables that should be "appending" instead of "export".
This is a workaround to fix translation of linkage type of "llvm.used" and "llvm.compiler.used" global variables that should be "appending" instead of "export".
This is a workaround to fix translation of linkage type of "llvm.used" and "llvm.compiler.used" global variables that should be "appending" instead of "export".
This is a workaround to fix translation of linkage type of "llvm.used" and
"llvm.compiler.used" global variables that should be "appending" instead of
"export".