lmi
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [lmi] LLVM libc++


From: Vadim Zeitlin
Subject: Re: [lmi] LLVM libc++
Date: Wed, 5 Oct 2022 19:38:36 +0200

On Wed, 5 Oct 2022 16:45:48 +0000 Greg Chicares <gchicares@sbcglobal.net> wrote:

GC> On 10/5/22 16:39, Vadim Zeitlin wrote:
GC> > On Wed, 5 Oct 2022 15:58:03 +0000 Greg Chicares <gchicares@sbcglobal.net> 
wrote:
GC> > 
GC> > GC> On 10/4/22 16:12, Vadim Zeitlin wrote:
GC> > GC> > On Tue, 4 Oct 2022 15:02:26 +0000 Greg Chicares 
<gchicares@sbcglobal.net> wrote:
GC> > GC> > 
GC> > GC> > GC> I'm doing something equivalent to your patch, but I've run into 
two
GC> > GC> > GC> linker problems.
GC> > GC> 
GC> > GC> Without even addressing those problems yet, I've found another, which
GC> > GC> is triggered by llvm's unwind library, with gcc and libstdc++'s regex
GC> > GC> in combination with ubsan:
GC> > 
GC> >  Sorry, but how is this related to llvm libunwind? I must be missing
GC> > something, but I just don't see how does it affect this?
GC> 
GC> This problem is observed in the presence of llvm libunwind,
GC> but not observed in its absence (i.e., with HP libunwind).
GC> That's all I know.

 Please let me know if you'd like me to try to reproduce this and
understand what happens there. I won't do it immediately because, perhaps,
it's not really necessary if using pragmas provides a satisfactory
solution/workaround.

 Good luck!
VZ

Attachment: pgpjk6Vobpq5W.pgp
Description: PGP signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]