public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/40599] [4.5 regression] GCC error in pre_and_rev_post_order_compute, at cfganal.c:1045 Date: Fri, 10 Jul 2009 09:45:00 -0000 [thread overview] Message-ID: <20090710094444.22342.qmail@sourceware.org> (raw) In-Reply-To: <bug-40599-13657@http.gcc.gnu.org/bugzilla/> ------- Comment #6 from jakub at gcc dot gnu dot org 2009-07-10 09:44 ------- While this triggers only with -fvar-tracking, it is var-tracking related only in that vt_find_locations calls pre_and_rev_post_order_compute. The real problem is that there are 2 basic blocks (in my case 220 and 222) that have no predecessors, so aren't reachable from the entry block and therefore gcc_assert (pre_order_num == n_basic_blocks - NUM_FIXED_BLOCKS); assertion fails (pre_order_num is n_basic_blocks - NUM_FIXED_BLOCKS - 2). In *.split3 we have: (insn 4396 853 4397 204 pkg0017.adb:483 (set (mem/c:SF (plus:DI (reg/f:DI 6 bp) (const_int -1668 [0xfffffffffffff97c])) [0 S4 A32]) (reg:SF 21 xmm0 [orig:143 D.79246 ] [143])) 98 {*movsf_1} (expr_list:REG_DEAD (reg:SF 21 xmm0 [orig:143 D.79246 ] [143]) (nil))) (insn 4397 4396 854 204 pkg0017.adb:483 (set (reg:SF 8 st) (mem/c:SF (plus:DI (reg/f:DI 6 bp) (const_int -1668 [0xfffffffffffff97c])) [0 S4 A32])) 98 {*movsf_1} (nil)) (insn 854 4397 862 204 pkg0017.adb:483 (set (reg:XF 9 st(1) [orig:147 D.79250 ] [147]) (float_extend:XF (reg:SF 8 st))) 137 {*extendsfxf2_i387} (expr_list:REG_DEAD (reg:SF 8 st) (expr_list:REG_EH_REGION (const_int 387 [0x183]) (nil)))) ;; End of basic block 204 -> ( 205 220) ... ;; Start of basic block ( 204) -> 220 ;; bb 220 artificial_defs: { d-1(0){ }d-1(1){ }} ;; bb 220 artificial_uses: { u-1(6){ }u-1(7){ }u-1(16){ }u-1(20){ }} ;; lr in 6 [bp] 7 [sp] 16 [argp] 20 [frame] ;; lr use 6 [bp] 7 [sp] 16 [argp] 20 [frame] ;; lr def 0 [ax] 1 [dx] 42 [r13] ;; Pred edge 204 (ab,eh) (code_label 3492 4766 3497 220 941 "" [0 uses]) but in *.stack: (insn 4396 853 4397 204 pkg0017.adb:483 (set (mem/c:SF (plus:DI (reg/f:DI 6 bp) (const_int -1668 [0xfffffffffffff97c])) [0 S4 A32]) (reg:SF 21 xmm0 [orig:143 D.79246 ] [143])) 98 {*movsf_1} (expr_list:REG_DEAD (reg:SF 21 xmm0 [orig:143 D.79246 ] [143]) (nil))) (insn 4397 4396 862 204 pkg0017.adb:483 (set (reg:SF 8 st) (mem/c:SF (plus:DI (reg/f:DI 6 bp) (const_int -1668 [0xfffffffffffff97c])) [0 S4 A32])) 98 {*movsf_1} (nil)) ;; End of basic block 204 -> ( 205) ... ;; Start of basic block () -> 220 ;; bb 220 artificial_defs: { d-1(0){ }d-1(1){ }} ;; bb 220 artificial_uses: { u-1(6){ }u-1(7){ }u-1(16){ }u-1(20){ }} ;; lr in 6 [bp] 7 [sp] 16 [argp] 20 [frame] ;; lr use 6 [bp] 7 [sp] 16 [argp] 20 [frame] ;; lr def 0 [ax] 1 [dx] 42 [r13] (code_label 3492 4766 3497 220 941 "" [0 uses]) So, either the float_extend is considered throwing when it shouldn't (when would float_extend throw? Only for signalling NaN?), or reg-stack.c is forgetting to cleanup the CFG when it removed insns with REG_EH_REGION. In any case it definitely doesn't look like var-tracking.c's fault. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40599
next prev parent reply other threads:[~2009-07-10 9:45 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-06-30 10:29 [Bug ada/40599] New: " oliver dot kellogg at eads dot com 2009-06-30 10:34 ` [Bug ada/40599] " oliver dot kellogg at eads dot com 2009-06-30 10:49 ` oliver dot kellogg at eads dot com 2009-06-30 10:57 ` rguenth at gcc dot gnu dot org 2009-06-30 11:07 ` oliver dot kellogg at eads dot com 2009-06-30 14:56 ` [Bug debug/40599] [4.5 regression] " pinskia at gcc dot gnu dot org 2009-07-02 11:37 ` rguenth at gcc dot gnu dot org 2009-07-09 15:47 ` rguenth at gcc dot gnu dot org 2009-07-10 9:45 ` jakub at gcc dot gnu dot org [this message] 2009-07-12 4:41 ` oliver dot kellogg at eads dot com 2009-07-12 5:29 ` oliver dot kellogg at eads dot com 2009-07-17 17:49 ` oliver dot kellogg at eads dot com 2009-07-17 18:11 ` rguenth at gcc dot gnu dot org 2009-11-09 13:49 ` rguenth at gcc dot gnu dot org 2009-11-10 5:39 ` oliver dot kellogg at eads 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=20090710094444.22342.qmail@sourceware.org \ --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).