search for: d50710

...at 8:48 AM Alastair Murray via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Hi Kern, > > We also had issues with mixing GCC/Clang builds when testing the 7.0 > release branch. > > My colleague submitted a patch that fixed the issue for us: > * https://reviews.llvm.org/D50710 > > I no longer have a copy of the error we were seeing to see if it was the > same, but the fix is to llvm::OptionalStorage and your error message > involves llvm::Optional. The patch removes a GCC specific ifdef, and > hopefully fixes the issue that made that necessary in the firs...

...org> wrote: >>> >>> Hi Kern, >>> >>> We also had issues with mixing GCC/Clang builds when testing the 7.0 >>> release branch. >>> >>> My colleague submitted a patch that fixed the issue for us: >>> * https://reviews.llvm.org/D50710 >>> >>> I no longer have a copy of the error we were seeing to see if it was the >>> same, but the fix is to llvm::OptionalStorage and your error message >>> involves llvm::Optional. The patch removes a GCC specific ifdef, and >>> hopefully fixes the is...

Hi folks, Not sure if this is the right mailing list target, but I'm trying out the new LLVM 7.0 packages found at http://apt.llvm.org by porting over an existing LLVM 6.0 project of ours to the new version. In doing so, I found that the executable always segfaulted at the same spot with no explanation: 0x0000000000fefe33 in