search for: llvm_define_once_flag

...PPC platforms during static initialization. The crash happens while calling std::call_once introduced by this patch in the wrapper used in getManagedStaticMutex. I understand this call is buggy for some platforms (or probably some oldish libstdc++ versions). Is this a known issue? Should we guard LLVM_DEFINE_ONCE_FLAG definition with platform specific macros to avoid the crash, at least for the moment? Thanks! Samuel -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20141103/68792fa3/attachment.html>

...ns while calling > > std::call_once introduced by this patch in the wrapper used in > > getManagedStaticMutex. > > > > I understand this call is buggy for some platforms (or probably some > > oldish libstdc++ versions). Is this a known issue? Should we guard > > LLVM_DEFINE_ONCE_FLAG definition with platform specific macros to > > avoid the crash, at least for the moment? > > > > Thanks! > > Samuel > > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/att...

...s patch in the wrapper used in > > > > getManagedStaticMutex. > > > > > > > > I understand this call is buggy for some platforms (or probably > > some > > > > oldish libstdc++ versions). Is this a known issue? Should we guard > > > > LLVM_DEFINE_ONCE_FLAG definition with platform specific macros to > > > > avoid the crash, at least for the moment? > > > > > > > > Thanks! > > > > Samuel > > > > > > > > > > > > > > > > > > > > -------------- nex...

...gt; getManagedStaticMutex. >>>>>> >>>>>> I understand this call is buggy for some platforms (or >> probably >>>> some >>>>>> oldish libstdc++ versions). Is this a known issue? Should we >> guard >>>>>> LLVM_DEFINE_ONCE_FLAG definition with platform specific macros >> to >>>>>> avoid the crash, at least for the moment? >>>>>> >>>>>> Thanks! >>>>>> Samuel >>>>>> >>>>>> >>>>> >>>&g...

...>> >>>>>> I understand this call is buggy for some platforms (or >> >> probably >> >>>> some >> >>>>>> oldish libstdc++ versions). Is this a known issue? Should we >> >> guard >> >>>>>> LLVM_DEFINE_ONCE_FLAG definition with platform specific macros >> >> to >> >>>>>> avoid the crash, at least for the moment? >> >>>>>> >> >>>>>> Thanks! >> >>>>>> Samuel >> >>>>>> >> &...