public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/52727] [4.7/4.8 Regression] internal compiler error at dwarf2cfi.c2:685 Date: Tue, 27 Mar 2012 16:53:00 -0000 [thread overview] Message-ID: <bug-52727-4-9Evf0THPkv@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-52727-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52727 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rth at gcc dot gnu.org --- Comment #9 from Jakub Jelinek <jakub at gcc dot gnu.org> 2012-03-27 16:49:37 UTC --- Looks like a problem during CSA. Before *.csa we have (insn 18 is a stack adjustment after a call): (insn 18 17 19 2 (parallel [ (set (reg/f:SI 7 sp) (plus:SI (reg/f:SI 7 sp) (const_int 4 [0x4]))) (clobber (reg:CC 17 flags)) ]) pr52727.ii:29 251 {*addsi_1} (expr_list:REG_UNUSED (reg:CC 17 flags) (expr_list:REG_ARGS_SIZE (const_int 0 [0]) (nil)))) ... (insn 205 27 206 2 (set (mem:SI (pre_dec:SI (reg/f:SI 7 sp)) [0 S4 A8]) (reg:SI 0 ax [115])) pr52727.ii:31 43 {*pushsi2} (expr_list:REG_DEAD (reg:SI 0 ax [115]) (nil))) (insn 206 205 207 2 (set (reg:DF 8 st [112]) (plus:DF (float:DF (mem:SI (reg/f:SI 7 sp) [0 S4 A8])) (reg:DF 8 st [112]))) pr52727.ii:31 765 {*fop_df_2_i387} (nil)) (insn 207 206 171 2 (set (reg/f:SI 7 sp) (plus:SI (reg/f:SI 7 sp) (const_int 4 [0x4]))) pr52727.ii:31 245 {*leasi_2} (nil)) but then CSA decides to remove insn 18 and adjust insn 205, so that it no longer pushes the value, but stores it to *sp. Unfortunately it means REG_ARGS_SIZE is dropped, there is no REG_ARGS_SIZE note on insn 207. Insns 205/206/207 were introduced during split2. Not sure what to do though, adding REG_ARGS_SIZE notes in the ix86_free_from_memory and ix86_force_to_memory would mean we'd have to find out what the current REG_ARGS_SIZE depth at that point is. And to solve this in csa pass, we'd need to find out that if we are removing stack deallocation with REG_ARGS_SIZE note against later stack allocation without REG_ARGS_SIZE, there must be some following stack deallocation on which we would force REG_ARGS_SIZE note. Richard?
next prev parent reply other threads:[~2012-03-27 16:49 UTC|newest] Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-03-26 16:51 [Bug c++/52727] New: [4.7] " florian at openwrt dot org 2012-03-26 16:52 ` [Bug c++/52727] " florian at openwrt dot org 2012-03-26 17:03 ` florian at openwrt dot org 2012-03-26 17:33 ` jakub at gcc dot gnu.org 2012-03-27 8:12 ` florian at openwrt dot org 2012-03-27 8:25 ` florian at openwrt dot org 2012-03-27 9:22 ` jakub at gcc dot gnu.org 2012-03-27 12:44 ` florian at openwrt dot org 2012-03-27 13:16 ` jakub at gcc dot gnu.org 2012-03-27 13:19 ` [Bug debug/52727] [4.7/4.8 Regression] " jakub at gcc dot gnu.org 2012-03-27 16:53 ` jakub at gcc dot gnu.org [this message] 2012-03-27 18:01 ` rth at gcc dot gnu.org 2012-03-27 23:22 ` rth at gcc dot gnu.org 2012-03-29 16:44 ` rth at gcc dot gnu.org 2012-03-30 18:23 ` rth at gcc dot gnu.org 2012-03-30 19:14 ` rth at gcc dot gnu.org 2012-04-10 13:39 ` florian at openwrt dot org 2012-04-13 13:14 ` [Bug debug/52727] [4.7 " rguenth at gcc dot gnu.org 2012-05-16 17:57 ` rth at gcc dot gnu.org 2012-05-16 18:02 ` rth at gcc dot gnu.org 2014-01-30 21:11 ` ppluzhnikov at google dot com 2014-01-31 0:05 ` [Bug debug/52727] [4.9 " jakub at gcc dot gnu.org 2014-01-31 6:42 ` jakub at gcc dot gnu.org 2014-02-05 18:42 ` rth at gcc dot gnu.org 2014-02-05 18:45 ` rth at gcc dot gnu.org 2014-02-05 18:48 ` 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-52727-4-9Evf0THPkv@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).