public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "doko at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/60648] New: [4.8 Regression] ICE (segmentation fault) in expand_binop Date: Tue, 25 Mar 2014 11:46:00 -0000 [thread overview] Message-ID: <bug-60648-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60648 Bug ID: 60648 Summary: [4.8 Regression] ICE (segmentation fault) in expand_binop Product: gcc Version: 4.9.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: doko at gcc dot gnu.org Created attachment 32445 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=32445&action=edit preprocessed source seen with trunk r208764 on i686-linux-gnu, works on x86_64-linux-gnu, works with the 4.8 branch, can be worked around with -O2. $ gcc -O3 -fPIC -c vec.ii In file included from ../../../src/meep.hpp:23:0, from ../../../src/meep_internals.hpp:18, from ../../../src/vec.cpp:23: ../../../src/meep/vec.hpp: In function 'double (* meep::derived_component_func(meep::derived_component, const meep::grid_volume&, int&, meep::component*))(const std::complex<double>*, const meep::vec&, void*)': ../../../src/meep/vec.hpp:325:3: internal compiler error: Segmentation fault Please submit a full bug report, with preprocessed source if appropriate. Program received signal SIGSEGV, Segmentation fault. 0x084f5382 in expand_binop(machine_mode, optab_tag, rtx_def*, rtx_def*, rtx_def*, int, optab_methods) () (gdb) bt #0 0x084f5382 in expand_binop(machine_mode, optab_tag, rtx_def*, rtx_def*, rtx_def*, int, optab_methods) () #1 0x083c1b6d in force_operand(rtx_def*, rtx_def*) () #2 0x083a6f1d in memory_address_addr_space(machine_mode, rtx_def*, unsigned char) () #3 0x083c2d96 in try_tablejump(tree_node*, tree_node*, tree_node*, tree_node*, rtx_def*, rtx_def*, int) () #4 0x08594c63 in ?? () #5 0x08596f25 in expand_case(gimple_statement_base*) () #6 0x0830a7a1 in ?? () #7 0x0830b5f8 in ?? () #8 0x0830d897 in ?? () #9 0x08506fc9 in execute_one_pass(opt_pass*) () #10 0x0850720f in execute_pass_list(opt_pass*) () #11 0x0832b4b8 in ?? () #12 0x0832cd6f in compile() () #13 0x0832d1c8 in finalize_compilation_unit() () #14 0x081eb3f1 in cp_write_global_declarations() () #15 0x085a0d25 in ?? () #16 0x085a28e6 in toplev_main(int, char**) () #17 0x081881cb in main ()
next reply other threads:[~2014-03-25 11:46 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-03-25 11:46 doko at gcc dot gnu.org [this message] 2014-03-25 11:57 ` [Bug target/60648] " trippels at gcc dot gnu.org 2014-03-25 13:37 ` [Bug target/60648] [4.9 " trippels at gcc dot gnu.org 2014-03-25 14:29 ` law at redhat dot com 2014-03-25 14:39 ` law at redhat dot com 2014-03-28 22:21 ` law at redhat dot com 2014-03-29 11:11 ` jakub at gcc dot gnu.org
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-60648-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).