This breaks C and C++ semantics because it can cause the address
of the global inside the module to differ from the address outside
of the module.
Details
Details
Diff Detail
Diff Detail
- Repository
- rL LLVM
- Build Status
Buildable 25631 Build 25630: arc lint + arc unit
Event Timeline
| llvm/lib/LTO/LTO.cpp | ||
|---|---|---|
| 363 | Use !GLobalValue::isAvailableExternallyLinkage(S->linkage()) instead? Also, we should update the earlier comment. | |
Comment Actions
Add comment
| llvm/lib/LTO/LTO.cpp | ||
|---|---|---|
| 363 | I'd prefer not to since it boils down to a comparison and it's slightly clearer to be explicit. Added comment and changed the other condition to be explicit as well. | |
| llvm/lib/LTO/LTO.cpp | ||
|---|---|---|
| 362–363 | Just making it consistent with the code I'm adding below. | |
Use !GLobalValue::isAvailableExternallyLinkage(S->linkage()) instead?
Also, we should update the earlier comment.