Displaying 20 results from an estimated 46 matches for "irlinked".
Did you mean:
irlinker
2016 Dec 23
0
ThinLTO promotion is ending up with "invalid" IR before IR-Linking
...leForThinLTO 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 dest
module looks legit, otherwise we would have later verifier failures.
> I’m hesitant about breaking the IR verifier like that before calling the
> IRLinker. The alternative I can see now would be:
> - to perform any handling that requires breaking the verifier as part of
> the IRL...
2016 Dec 23
6
ThinLTO promotion is ending up with "invalid" IR before IR-Linking
...leForThinLTO 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 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 renameMod...
2016 Jul 28
2
[ThinLTO] assert(GS != DefinedGlobals.end()) failed in FunctionImport.cpp
Encountered “assert(GS != DefinedGlobals.end())” failure while running ThinLTO. The assertion statement is in MustPreserveGV lambda function in llvm::thinLTOInternalizeModule (lib/Transforms/IPO/FunctionImport.cpp).
It seems that the assertion fails because it fails to recover the "original name" of the global value. ModuleSummaryIndex::getOriginalNameBeforePromote attempts to get the
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
2016 Jul 29
3
[ThinLTO] assert(GS != DefinedGlobals.end()) failed in FunctionImport.cpp
Hello Teresa,
Thank you for your reply. I’m trying to create a small repro but find it hard to nail down because originally it is a big build. This happens with gold linker.
Thanks,
Taewook
From: Teresa Johnson <tejohnson at google.com>
Date: Thursday, July 28, 2016 at 5:08 PM
To: Taewook Oh <twoh at fb.com>
Cc: via llvm-dev <llvm-dev at lists.llvm.org>
Subject: Re: [llvm-dev]
2016 Jul 29
2
[ThinLTO] assert(GS != DefinedGlobals.end()) failed in FunctionImport.cpp
Hello Teresa,
Thank you for your analysis. One thing to note is that the global materializer materializes the value as a function declaration, not a function definition. As I pasted on my first email,
; Materializable
; Function Attrs: nounwind uwtable
define weak_odr void @foo(%1*) unnamed_addr #7 comdat($comdat1) align 2 personality i32 (...)* @__gxx_personality_v0 {}
is materialized to
;
2016 Jul 29
0
[ThinLTO] assert(GS != DefinedGlobals.end()) failed in FunctionImport.cpp
On Thu, Jul 28, 2016 at 5:18 PM, Taewook Oh <twoh at fb.com> wrote:
> Hello Teresa,
>
>
>
> Thank you for your reply. I’m trying to create a small repro but find it
> hard to nail down because originally it is a big build. This happens with
> gold linker.
>
I think I need to see a smaller test case, looking through the code I'm not
sure how we ended up in this
2016 Jul 29
0
[ThinLTO] assert(GS != DefinedGlobals.end()) failed in FunctionImport.cpp
Hi Taewook,
On Thu, Jul 28, 2016 at 4:38 PM, Taewook Oh via llvm-dev <
llvm-dev at lists.llvm.org> wrote:
> Encountered “assert(GS != DefinedGlobals.end())” failure while running
> ThinLTO. The assertion statement is in MustPreserveGV lambda function in
> llvm::thinLTOInternalizeModule (lib/Transforms/IPO/FunctionImport.cpp).
>
>
>
> It seems that the assertion fails
2016 Jul 29
0
[ThinLTO] assert(GS != DefinedGlobals.end()) failed in FunctionImport.cpp
On Fri, Jul 29, 2016 at 2:25 PM, Taewook Oh <twoh at fb.com> wrote:
> Hello Teresa,
>
>
>
> Thank you for your analysis. One thing to note is that the global
> materializer materializes the value as a function declaration, not a
> function definition. As I pasted on my first email,
>
>
>
> ; Materializable
>
> ; Function Attrs: nounwind uwtable
>
2016 Dec 23
2
ThinLTO promotion is ending up with "invalid" IR before IR-Linking
...leForThinLTO 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 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 renameMod...
2016 Jul 29
2
[ThinLTO] assert(GS != DefinedGlobals.end()) failed in FunctionImport.cpp
It was r274523. I’m not sure it was the same module. By mistake I restarted the build with the previous version without backing backing up the build artifacts :(
Thanks,
Taewook
From: Teresa Johnson <tejohnson at google.com>
Date: Friday, July 29, 2016 at 3:30 PM
To: Taewook Oh <twoh at fb.com>
Cc: via llvm-dev <llvm-dev at lists.llvm.org>
Subject: Re: [llvm-dev] [ThinLTO]
2016 Dec 27
0
ThinLTO promotion is ending up with "invalid" IR before IR-Linking
...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 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
> }
>
>...
2016 Jul 29
0
[ThinLTO] assert(GS != DefinedGlobals.end()) failed in FunctionImport.cpp
On Fri, Jul 29, 2016 at 3:40 PM, Taewook Oh <twoh at fb.com> wrote:
> It was r274523. I’m not sure it was the same module. By mistake I
> restarted the build with the previous version without backing backing up
> the build artifacts :(
>
So a couple things were added to gold since then, index-based linkonce/weak
resolution and some more aggressive internalization. I don't
2016 Jul 30
2
[ThinLTO] assert(GS != DefinedGlobals.end()) failed in FunctionImport.cpp
Yes, if I drop the debug flag then the original problem (assertion failure) comes back.
Thanks,
Taewook
From: Teresa Johnson <tejohnson at google.com>
Date: Friday, July 29, 2016 at 3:52 PM
To: Taewook Oh <twoh at fb.com>
Cc: via llvm-dev <llvm-dev at lists.llvm.org>
Subject: Re: [llvm-dev] [ThinLTO] assert(GS != DefinedGlobals.end()) failed in FunctionImport.cpp
On Fri, Jul
2016 Jul 30
1
[ThinLTO] assert(GS != DefinedGlobals.end()) failed in FunctionImport.cpp
Ok, good to know.
Any luck on a smaller test case for either of the problems?
I tried building all the C/C++ SPEC cpu2006 benchmarks with -g -flto=thin
at head and didn't get the failure. Let me try to look into how the debug
metadata is normally dropped from the imported decl. In the meantime, could
you find out the answers to the questions I had (see below) about the
linkage type of the
2016 Aug 15
2
[ThinLTO] assert(GS != DefinedGlobals.end()) failed in FunctionImport.cpp
Hi Taewook,
I had a better fix for this approved (D23015), but when I went to merge
this with the new LTO API I committed for pcc last week I discovered that
his new API already has the same effect. I will update the bug with this
info as well. Can you confirm that with a compiler built after 278338 that
this problem no longer occurs?
Also, any luck on a smaller test case for the -g issue? Now
2016 Aug 15
2
[ThinLTO] assert(GS != DefinedGlobals.end()) failed in FunctionImport.cpp
No problem! I want to make sure you aren't blocked on trying ThinLTO.
Thanks,
Teresa
On Mon, Aug 15, 2016 at 2:50 PM, Taewook Oh <twoh at fb.com> wrote:
> Hello Teresa,
>
>
>
> Sorry I was working on another LLVM issue that more urgent for us, so
> didn’t have much time to work on smaller test case. I’ll try the new API
> and see if the issus is gone. Thanks!
>
2016 Dec 23
1
ThinLTO promotion is ending up with "invalid" IR before IR-Linking
...leForThinLTO 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 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...
2016 Dec 23
0
ThinLTO promotion is ending up with "invalid" IR before IR-Linking
...leForThinLTO 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 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...
2016 Dec 07
4
[ThinLTO] Reducing imported debug metadata
A couple weeks ago I sat down with David Blaikie to figure out what we
could trim when importing debug metadata during function importing. I have
a prototype that reduces the resulting .o sizes significantly with ThinLTO
-g. However, I ran into some issues when cleaning up part of this in
preparation for a patch. Since Mehdi indicated that he and Adrian were
going to be looking at this as well