Displaying 6 results from an estimated 6 matches for "globalfunc1".
Did you mean:
global_func
2016 Dec 27
0
ThinLTO promotion is ending up with "invalid" IR before IR-Linking
...g of aliases that would result in the aliasee
> becoming available_externally. Presumably the resulting IRLinked dest
> module looks legit, otherwise we would have later verifier failures.
>
>
> So the source module is:
>
> @weakalias = weak alias void (...), bitcast (void ()* @globalfunc1 to void
> (...)*)
> define void @globalfunc1() #0 {
> entry:
> ret void
> }
>
> But we turn globalfunc1 into available_externally in
> renameModuleForThinLTO(), which make the alias invalid.
>
> We don’t import the IR so the destination module is OK.
>
Presumably...
2016 Dec 23
6
ThinLTO promotion is ending up with "invalid" IR before IR-Linking
...we specifically prevent importing of aliases that would result in the aliasee becoming available_externally. Presumably the resulting IRLinked dest module looks legit, otherwise we would have later verifier failures.
So the source module is:
@weakalias = weak alias void (...), bitcast (void ()* @globalfunc1 to void (...)*)
define void @globalfunc1() #0 {
entry:
ret void
}
But we turn globalfunc1 into available_externally in renameModuleForThinLTO(), which make the alias invalid.
We don’t import the IR so the destination module is OK.
36
>
>
> I’m hesitant about breaking the IR verifie...
2016 Dec 23
2
ThinLTO promotion is ending up with "invalid" IR before IR-Linking
...we specifically prevent importing of aliases that would result in the aliasee becoming available_externally. Presumably the resulting IRLinked dest module looks legit, otherwise we would have later verifier failures.
So the source module is:
@weakalias = weak alias void (...), bitcast (void ()* @globalfunc1 to void (...)*)
define void @globalfunc1() #0 {
entry:
ret void
}
But we turn globalfunc1 into available_externally in renameModuleForThinLTO(), which make the alias invalid.
We don’t import the IR so the destination module is OK.
36
I’m hesitant about breaking the IR verifier like that bef...
2016 Dec 23
0
ThinLTO promotion is ending up with "invalid" IR before IR-Linking
On Thu, Dec 22, 2016 at 8:55 PM, Mehdi Amini <mehdi.amini at apple.com> wrote:
> 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.
>
2016 Dec 23
1
ThinLTO promotion is ending up with "invalid" IR before IR-Linking
...vent importing of aliases that would result in the aliasee becoming available_externally. Presumably the resulting IRLinked dest module looks legit, otherwise we would have later verifier failures.
>
> So the source module is:
>
> @weakalias = weak alias void (...), bitcast (void ()* @globalfunc1 to void (...)*)
> define void @globalfunc1() #0 {
> entry:
> ret void
> }
>
> But we turn globalfunc1 into available_externally in renameModuleForThinLTO(), which make the alias invalid.
>
> We don’t import the IR so the destination module is OK.
> 36
>
>
>...
2016 Dec 23
0
ThinLTO promotion is ending up with "invalid" IR before IR-Linking
...ould result in the aliasee becoming available_externally. Presumably the resulting IRLinked dest module looks legit, otherwise we would have later verifier failures.
>>>
>>> So the source module is:
>>>
>>> @weakalias = weak alias void (...), bitcast (void ()* @globalfunc1 to void (...)*)
>>> define void @globalfunc1() #0 {
>>> entry:
>>> ret void
>>> }
>>>
>>> But we turn globalfunc1 into available_externally in renameModuleForThinLTO(), which make the alias invalid.
>>>
>>> We don’t import...