public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/53373] [4.8 regression] ICE on valid code with -march-native Date: Wed, 16 May 2012 10:17:00 -0000 [thread overview] Message-ID: <bug-53373-4-4hnbk6nHNk@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-53373-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53373 Richard Guenther <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Last reconfirmed| |2012-05-16 CC| |bernds at gcc dot gnu.org Component|tree-optimization |rtl-optimization Target Milestone|--- |4.8.0 Ever Confirmed|0 |1 --- Comment #1 from Richard Guenther <rguenth at gcc dot gnu.org> 2012-05-16 10:05:29 UTC --- Confirmed. Caused by Bernds call-return value stuff. Program received signal SIGSEGV, Segmentation fault. 0x000000000064528e in save_call_clobbered_regs () at /space/rguenther/src/svn/trunk/gcc/caller-save.c:876 876 rtx dest = SET_DEST (call_set); (gdb) p call_set $1 = (rtx) 0x0 (gdb) call debug_rtx (insn) (call_insn 1344 1343 1347 114 (parallel [ (set (reg:DI 0 ax) (call (mem:QI (symbol_ref:DI ("memcpy") [flags 0x41] <function_decl 0x7ffff5aab200 memcpy>) [0 memcpy S1 A8]) (const_int 0 [0]))) (unspec [ (const_int 2 [0x2]) ] UNSPEC_CALL_NEEDS_VZEROUPPER) ]) libfftpack/fftpack.c:308 632 {*call_value_vzeroupper} (expr_list:REG_DEAD (reg:DI 5 di) (expr_list:REG_DEAD (reg:DI 4 si) (expr_list:REG_DEAD (reg:DI 1 dx) (expr_list:REG_UNUSED (reg:DI 0 ax) (expr_list:REG_RETURNED (reg:DI 2 cx [orig:769 ivtmp.2819 ] [769]) (expr_list:REG_EH_REGION (const_int 0 [0]) (nil))))))) (expr_list:REG_FRAME_RELATED_EXPR (set (reg:DI 0 ax) (reg:DI 5 di)) (expr_list:REG_FRAME_RELATED_EXPR (use (reg:DI 5 di)) (expr_list:REG_FRAME_RELATED_EXPR (use (reg:DI 4 si)) (expr_list:REG_FRAME_RELATED_EXPR (use (reg:DI 1 dx)) (nil))))))
next prev parent reply other threads:[~2012-05-16 10:15 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-05-16 9:09 [Bug tree-optimization/53373] New: " martin@mpa-garching.mpg.de 2012-05-16 10:17 ` rguenth at gcc dot gnu.org [this message] 2012-05-16 10:39 ` [Bug rtl-optimization/53373] " rguenth at gcc dot gnu.org 2012-05-18 11:47 ` rguenth at gcc dot gnu.org 2012-05-18 11:51 ` rguenth at gcc dot gnu.org 2012-05-18 14:25 ` evstupac at gmail dot com 2012-05-20 17:47 ` vincenzo.innocente at cern dot ch 2012-05-20 17:47 ` danglin at gcc dot gnu.org 2012-05-20 18:25 ` dave.anglin at bell dot net 2012-05-20 20:12 ` [Bug rtl-optimization/53373] [4.8 regression] ICE on valid code with -mavx hjl.tools at gmail dot com 2012-05-20 22:06 ` [Bug rtl-optimization/53373] [4.8 regression] ICE on valid code with -march-native pinskia at gcc dot gnu.org 2012-05-21 21:50 ` [Bug rtl-optimization/53373] [4.8 regression] ICE on valid code with -mavx bernds at gcc dot gnu.org 2012-05-23 9:24 ` vincenzo.innocente at cern dot ch 2012-05-25 18:29 ` bernds 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-53373-4-4hnbk6nHNk@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).