Displaying 7 results from an estimated 7 matches for "renamemoduleforthinlto".
2016 Dec 27
0
ThinLTO promotion is ending up with "invalid" IR before IR-Linking
...FunctionImport.cpp, and it does not pass (on
>> current trunk) in a few cases. One that I looked at ended up with aliases
>> pointing to available_externally functions for instance.
>>
>
> How do these look after IRLinking (in the dest module)? I looked at the
> logic in renameModuleForThinLTO and all the conversions to
> available_externally are predicated on it being in the provided
> GlobalsToImport set. But in FunctionImport.cpp selectCallee() we
> specifically prevent importing of aliases that would result in the aliasee
> becoming available_externally. Presumably the re...
2016 Dec 23
6
ThinLTO promotion is ending up with "invalid" IR before IR-Linking
...before running the IRLinker in FunctionImport.cpp, and it does not pass (on current trunk) in a few cases. One that I looked at ended up with aliases pointing to available_externally functions for instance.
>
> How do these look after IRLinking (in the dest module)? I looked at the logic in renameModuleForThinLTO and all the conversions to available_externally are predicated on it being in the provided GlobalsToImport set. But in FunctionImport.cpp selectCallee() we specifically prevent importing of aliases that would result in the aliasee becoming available_externally. Presumably the resulting IRLinked des...
2016 Dec 23
2
ThinLTO promotion is ending up with "invalid" IR before IR-Linking
...fier right before running the IRLinker in FunctionImport.cpp, and it does not pass (on current trunk) in a few cases. One that I looked at ended up with aliases pointing to available_externally functions for instance.
How do these look after IRLinking (in the dest module)? I looked at the logic in renameModuleForThinLTO and all the conversions to available_externally are predicated on it being in the provided GlobalsToImport set. But in FunctionImport.cpp selectCallee() we specifically prevent importing of aliases that would result in the aliasee becoming available_externally. Presumably the resulting IRLinked des...
2016 Dec 23
0
ThinLTO promotion is ending up with "invalid" IR before IR-Linking
...t; running the IRLinker in FunctionImport.cpp, and it does not pass (on
> current trunk) in a few cases. One that I looked at ended up with aliases
> pointing to available_externally functions for instance.
>
How do these look after IRLinking (in the dest module)? I looked at the
logic in renameModuleForThinLTO and all the conversions to
available_externally are predicated on it being in the provided
GlobalsToImport set. But in FunctionImport.cpp selectCallee() we
specifically prevent importing of aliases that would result in the aliasee
becoming available_externally. Presumably the resulting IRLinked des...
2016 Dec 23
1
ThinLTO promotion is ending up with "invalid" IR before IR-Linking
...running the IRLinker in FunctionImport.cpp, and it does not pass (on current trunk) in a few cases. One that I looked at ended up with aliases pointing to available_externally functions for instance.
>>
>> How do these look after IRLinking (in the dest module)? I looked at the logic in renameModuleForThinLTO and all the conversions to available_externally are predicated on it being in the provided GlobalsToImport set. But in FunctionImport.cpp selectCallee() we specifically prevent importing of aliases that would result in the aliasee becoming available_externally. Presumably the resulting IRLinked des...
2016 Dec 23
0
ThinLTO promotion is ending up with "invalid" IR before IR-Linking
...nker in FunctionImport.cpp, and it does not pass (on current trunk) in a few cases. One that I looked at ended up with aliases pointing to available_externally functions for instance.
>>>>
>>>> How do these look after IRLinking (in the dest module)? I looked at the logic in renameModuleForThinLTO and all the conversions to available_externally are predicated on it being in the provided GlobalsToImport set. But in FunctionImport.cpp selectCallee() we specifically prevent importing of aliases that would result in the aliasee becoming available_externally. Presumably the resulting IRLinked des...
2016 Dec 23
2
ThinLTO promotion is ending up with "invalid" IR before IR-Linking
Hey,
As I’m playing with Metadata lazy-loading, I added a verifier right before running the IRLinker in FunctionImport.cpp, and it does not pass (on current trunk) in a few cases. One that I looked at ended up with aliases pointing to available_externally functions for instance.
I’m hesitant about breaking the IR verifier like that before calling the IRLinker. The alternative I can see now would