public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "andrey.vihrov at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug sanitizer/66343] New: "Error: .Lubsan_type3 already defined" with UBSan and precompiled headers Date: Sat, 30 May 2015 12:56:00 -0000 [thread overview] Message-ID: <bug-66343-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66343 Bug ID: 66343 Summary: "Error: .Lubsan_type3 already defined" with UBSan and precompiled headers Product: gcc Version: 5.1.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: sanitizer Assignee: unassigned at gcc dot gnu.org Reporter: andrey.vihrov at gmail dot com CC: dodji at gcc dot gnu.org, dvyukov at gcc dot gnu.org, jakub at gcc dot gnu.org, kcc at gcc dot gnu.org Target Milestone: --- Using this source as test.cpp: #include <iostream> int arr[2]; int main() { int d, i = 0; std::cin >> d; int x = arr[i] - arr[i+1]; int res = (d - 1) / d; } and compiling with g++ -o stdc++.h.gch -x c++-header /usr/include/c++/5.1.0/x86_64-unknown-linux-gnu/32/bits/stdc++.h -m32 -fsanitize=undefined && g++ -o test test.cpp -I. -include stdc++.h -m32 -fsanitize=undefined -Winvalid-pch (this command precompiles <bits/stdc++.h> as stdc++.h.gch, then uses it with the above program), the result is /tmp/ccw5nd8W.s: Assembler messages: /tmp/ccw5nd8W.s:86: Error: symbol `.Lubsan_type3' is already defined I'm not attaching a preprocessed source because this problem appears only with precompiled headers. gcc -v: Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-unknown-linux-gnu/5.1.0/lto-wrapper Target: x86_64-unknown-linux-gnu Configured with: /build/gcc-multilib/src/gcc-5-20150519/configure --prefix=/usr --libdir=/usr/lib --libexecdir=/usr/lib --mandir=/usr/share/man --infodir=/usr/share/info --with-bugurl=https://bugs.archlinux.org/ --enable-languages=c,c++,ada,fortran,go,lto,objc,obj-c++ --enable-shared --enable-threads=posix --enable-libmpx --with-system-zlib --with-isl --enable-__cxa_atexit --disable-libunwind-exceptions --enable-clocale=gnu --disable-libstdcxx-pch --disable-libssp --enable-gnu-unique-object --enable-linker-build-id --enable-lto --enable-plugin --enable-install-libiberty --with-linker-hash-style=gnu --enable-gnu-indirect-function --enable-multilib --disable-werror --enable-checking=release --with-default-libstdcxx-abi=c++98 Thread model: posix gcc version 5.1.0 (GCC)
next reply other threads:[~2015-05-30 12:56 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-05-30 12:56 andrey.vihrov at gmail dot com [this message] 2015-08-24 20:21 ` [Bug sanitizer/66343] " rogero at howzatt dot demon.co.uk
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-66343-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).