[Bug sanitizer/84629] sanitizer warnings and errors on Linux

2018-10-24 Thread marxin at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84629 --- Comment #6 from Martin Liška --- I'm curious about: /home/marxin/Programming/gcc/libsanitizer/sanitizer_common/sanitizer_linux.cc: In function ‘void* __sanitizer::internal_start_thread(void (*)(void*), void*)’:

[Bug sanitizer/84629] sanitizer warnings and errors on Linux

2018-03-01 Thread jakub at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84629 Jakub Jelinek changed: What|Removed |Added Status|WAITING |RESOLVED Resolution|---

[Bug sanitizer/84629] sanitizer warnings and errors on Linux

2018-02-28 Thread jay.krell at cornell dot edu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84629 --- Comment #4 from Jay --- -disable-multilib fixed the errors. I didn't watch for the warnings.

[Bug sanitizer/84629] sanitizer warnings and errors on Linux

2018-02-28 Thread jay.krell at cornell dot edu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84629 --- Comment #3 from Jay --- This is ubuntu xenial I think, on WSL. Which doesn't have multi-arch. So I'll try configure -disable-multilib.

[Bug sanitizer/84629] sanitizer warnings and errors on Linux

2018-02-28 Thread jakub at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84629 --- Comment #2 from Jakub Jelinek --- The __NR_* macros are actually provided by kernel headers rather than glibc, /usr/include/asm*/unistd*.h So this looks like a distro bug to me.

[Bug sanitizer/84629] sanitizer warnings and errors on Linux

2018-02-28 Thread pinskia at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84629 Andrew Pinski changed: What|Removed |Added Status|UNCONFIRMED |WAITING Last reconfirmed|