public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "fabian@ritter-vogt.de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug lto/61048] New: compiling with -fsanitize=address crashes GCC if pointers are used Date: Sat, 03 May 2014 18:31:00 -0000 [thread overview] Message-ID: <bug-61048-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=61048 Bug ID: 61048 Summary: compiling with -fsanitize=address crashes GCC if pointers are used Product: gcc Version: 4.9.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: lto Assignee: unassigned at gcc dot gnu.org Reporter: fabian@ritter-vogt.de test.cpp: include <iostream> int main() { int *i = reinterpret_cast<int*>(0xC1000000); std::cout << *i << std::endl; } Compile with: arm-none-eabi-g++ test.cpp -c -o test.o -fsanitize=address -flto Link with: arm-none-eabi-g++ test.o -o test -Wl,-flto arm-none-eabi-g++ -v: Using built-in specs. COLLECT_GCC=arm-none-eabi-g++ COLLECT_LTO_WRAPPER=/opt/nspire/Ndless/ndless-sdk/toolchain/install/lib/gcc/arm-none-eabi/4.9.0/lto-wrapper Target: arm-none-eabi Configured with: ../gcc-4.9.0/configure --target=arm-none-eabi --prefix=/opt/nspire/Ndless/ndless-sdk/toolchain/install --enable-interwork --enable-multilib --enable-languages=c,c++ --with-system-zlib --with-newlib --with-headers=../newlib-2.0.0/newlib/libc/include --disable-shared --with-gnu-as --with-gnu-ld --with-float=soft --disable-werror Thread model: single gcc version 4.9.0 (GCC) Result: lto1: internal compiler error: in streamer_get_builtin_tree, at tree-streamer-in.c:1124 0x914191 streamer_get_builtin_tree(lto_input_block*, data_in*) ../../gcc-4.9.0/gcc/tree-streamer-in.c:1124 0x6f55d4 lto_input_tree_1(lto_input_block*, data_in*, LTO_tags, unsigned int) ../../gcc-4.9.0/gcc/lto-streamer-in.c:1265 0x6f57c1 lto_input_scc(lto_input_block*, data_in*, unsigned int*, unsigned int*) ../../gcc-4.9.0/gcc/lto-streamer-in.c:1193 0x50375e lto_read_decls ../../gcc-4.9.0/gcc/lto/lto.c:1879 0x504ef5 lto_file_finalize ../../gcc-4.9.0/gcc/lto/lto.c:2214 0x504ef5 lto_create_files_from_ids ../../gcc-4.9.0/gcc/lto/lto.c:2224 0x504ef5 lto_file_read ../../gcc-4.9.0/gcc/lto/lto.c:2264 0x504ef5 read_cgraph_and_symbols ../../gcc-4.9.0/gcc/lto/lto.c:2967 0x504ef5 lto_main() ../../gcc-4.9.0/gcc/lto/lto.c:3412 Please submit a full bug report, with preprocessed source if appropriate. Please include the complete backtrace with any bug report. See <http://gcc.gnu.org/bugs.html> for instructions. lto-wrapper: /opt/nspire/Ndless/ndless-sdk/toolchain/install/bin/arm-none-eabi-g++ returned 1 exit status /opt/nspire/Ndless/ndless-sdk/toolchain/install/arm-none-eabi/bin/ld.real: lto-wrapper failed collect2: error: ld returned 1 exit status It compiles fine if I remove "-flto" (disregarding undefined references)
next reply other threads:[~2014-05-03 18:31 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-05-03 18:31 fabian@ritter-vogt.de [this message] 2014-10-13 11:47 ` [Bug lto/61048] " i.palachev at samsung dot com 2014-10-14 16:41 ` i.palachev at samsung dot com 2014-10-14 16:42 ` i.palachev at samsung dot com 2014-10-14 17:01 ` i.palachev at samsung dot com 2014-10-15 14:57 ` i.palachev at samsung dot com
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-61048-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).