On Wed, Jan 20, 2016 at 9:40 AM, Hanno Böck <[email protected]> wrote:
> On Wed, 20 Jan 2016 09:14:53 -0800 > Konstantin Serebryany <[email protected]> wrote: > > > Are you talking about gcc or clang? > > gcc in this case. > > > In gcc looks like this does not happen. > > (I'd say this needs to be fixed in gcc, just for compatibility, at > > least) > > Okay, so should we open a bug report for gcc? > It won't hurt. I don't know what the gcc folks think about this, but once we file a bug we'll know. :) > Anyway, given that the gcc-deployment-to-distro process is taking quite > a while I wonder if corresponding configure changes should be attempted > anyway. > As Dmitry suggested, if you always use "-fsanitize=address -lpthread" it will work with both clang and gcc. So it might be the simplest fix (no need to change the config scripts) Just document it that -lpthread is there due to the gcc bug/feature. > > -- > Hanno Böck > http://hboeck.de/ > > mail/jabber: [email protected] > GPG: BBB51E42 > > -- > You received this message because you are subscribed to the Google Groups > "address-sanitizer" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "address-sanitizer" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
