search for: pr28180

...O build with lld. > I have a fix for that (Mehdi has one as well, apparently) in my local > tree, but I don't have time to reduce. If you can take care of that, > chances are that an upstream fix will be committed shortly after. > Just to clarify, I'm talking about the issue in PR28180. I can't comment about the ThinLTO one, sorry. -- Davide "There are no solved problems; there are only problems that are more or less solved" -- Henri Poincare

...I have a fix for that (Mehdi has one as well, apparently) in my local >> tree, but I don't have time to reduce. If you can take care of that, >> chances are that an upstream fix will be committed shortly after. >> > > Just to clarify, I'm talking about the issue in PR28180. I can't > comment about the ThinLTO one, sorry. If lld is setting enableDebugTypeODRUniquing(); on the context and isn’t using the IRMover to target an empty module, it can be the same bug. I mentioned that it should touch only ThinLTO but I had ld64 in mind. — Mehdi

...om> on behalf of Mehdi Amini <mehdi.amini at apple.com> Date: Friday, July 22, 2016 at 2:16 PM To: Taewook Oh <twoh at fb.com> Cc: via llvm-dev <llvm-dev at lists.llvm.org> Subject: Re: [llvm-dev] [ThinLTO] Using two different IRMovers for the same composite module? (related to PR28180) On Jul 22, 2016, at 1:50 PM, Taewook Oh via llvm-dev <llvm-dev at lists.llvm.org<mailto:llvm-dev at lists.llvm.org>> wrote: Hello, While trying ThinLTO, I ran into an assertion failure in IRMover: https://llvm.org/bugs/show_bug.cgi?id=28180<https://urldefense.proofpoint.com/v2/...

Hello, While trying ThinLTO, I ran into an assertion failure in IRMover: https://llvm.org/bugs/show_bug.cgi?id=28180. I found that the assertion failure is happening because IRMover tries to map the metadata that already mapped in the destination module, and it seems that this happens because two different IRMovers are used for the same destination (or composite) module. During LTO, an IRMover