public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rogero at howzatt dot demon.co.uk" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug sanitizer/66343] "Error: .Lubsan_type3 already defined" with UBSan and precompiled headers Date: Mon, 24 Aug 2015 20:21:00 -0000 [thread overview] Message-ID: <bug-66343-4-V8ISQMpX9i@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-66343-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66343 --- Comment #1 from Roger Orr <rogero at howzatt dot demon.co.uk> --- Fails for me (with a very slightly different label: Lubsan_type0) on gcc-trunk (as of 2015-08-22) without needing the -m32: $ /usr/share/gcc-trunk/bin/gcc -v Using built-in specs. COLLECT_GCC=/usr/share/gcc-trunk/bin/gcc COLLECT_LTO_WRAPPER=/usr/share/gcc-trunk/libexec/gcc/x86_64-unknown-cygwin/6.0.0/lto-wrapper.exe Target: x86_64-unknown-cygwin Configured with: /cygdrive/c/projects/gcc/objdir/../gcctrunk/configure --enable-languages=c,c++ --prefix=/usr/share/gcc-trunk : (reconfigured) ../gcctrunk/configure --prefix=/usr/share/gcc-trunk/ : (reconfigured) ../gcctrunk/configure --prefix=/usr/share/gcc-trunk/ --enable-languages=c,c++ Thread model: single gcc version 6.0.0 20150822 (experimental) (GCC) $ /usr/share/gcc-trunk/bin/g++ -o stdc++.h.gch -x c++-header /usr/share/gcc-tru nk/include/c++/6.0.0/x86_64-unknown-cygwin/bits/stdc++.h -fsanitize=undefined $ /usr/share/gcc-trunk/bin/g++ -o test test.cpp -I. -include stdc++.h -fsanitize=undefined -Winvalid-pch gwin /tmp/ccJdB2eu.s: Assembler messages: /tmp/ccJdB2eu.s:171: Error: symbol `.Lubsan_type0' is already defined
prev parent reply other threads:[~2015-08-24 20:21 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-05-30 12:56 [Bug sanitizer/66343] New: " andrey.vihrov at gmail dot com 2015-08-24 20:21 ` rogero at howzatt dot demon.co.uk [this message]
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-V8ISQMpX9i@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).