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 target/107183] [10/11/12/13 Regression] -fcompare-debug failure (length) with -fsanitize=float-cast-overflow since r7-5708-gcfd719e7769fd43f
Date: Fri, 18 Nov 2022 14:29:25 +0000	[thread overview]
Message-ID: <bug-107183-4-uCZhUItc21@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107183-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107183

--- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Seems the bug is in swap_rtx_condition.
It is called on:
(insn 10023 10021 10024 4 (set (reg:CCFP 17 flags)
        (unspec:CCFP [
                (compare:CCFP (reg:XF 9 st(1) [orig:84 _3 ] [84])
                    (reg:XF 8 st [107]))
            ] UNSPEC_NOTRAP)) "pr107183.c":6:18 discrim 1 45 {*cmpiuxf_i387}
     (expr_list:REG_DEAD (reg:XF 9 st(1) [orig:84 _3 ] [84])
        (expr_list:REG_DEAD (reg:XF 8 st [107])
            (nil))))
on the first next_flags_user call in the function it sets insn to:
(insn 10110 10024 10111 4 (set (reg:QI 3 bx [105])
        (unordered:QI (reg:CCFP 17 flags)
            (const_int 0 [0]))) "pr107183.c":6:18 discrim 1 949 {*setcc_qi}
     (nil))
(still the same between -g and -g0, but already that one could differ),
but then next_flags_user (the 3rd one in the function) finds
(debug_insn 4 10029 10030 4 (var_location:SI D#1 (if_then_else:SI (uneq
(reg:CCFP 17 flags)
            (const_int 0 [0]))
        (reg:SI 3 bx [105])
        (reg:SI 0 ax [111]))) -1
     (nil))
with -g and
(insn 10030 10029 10032 4 (set (reg:SI 3 bx [orig:90 iftmp.0_9 ] [90])
        (if_then_else:SI (uneq (reg:CCFP 17 flags)
                (const_int 0 [0]))
            (reg:SI 3 bx [105])
            (reg:SI 0 ax [111]))) "pr107183.c":6:18 discrim 1 1269
{*movsicc_noc}
     (expr_list:REG_DEAD (reg:CCFP 17 flags)
        (expr_list:REG_DEAD (reg:SI 0 ax [111])
            (expr_list:REG_EQUAL (if_then_else:SI (uneq (reg:CCFP 17 flags)
                        (const_int 0 [0]))
                    (reg:SI 3 bx [105])
                    (const_int 1 [0x1]))
                (nil)))))
with -g0.

  parent reply	other threads:[~2022-11-18 14:29 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-07 18:14 [Bug debug/107183] New: -fcompare-debug failure (length) with -fsanitize=float-cast-overflow zsojka at seznam dot cz
2022-10-07 20:18 ` [Bug target/107183] [10/11/12/13 Regression] " pinskia at gcc dot gnu.org
2022-10-10 13:00 ` [Bug target/107183] [10/11/12/13 Regression] -fcompare-debug failure (length) with -fsanitize=float-cast-overflow since r7-5708-gcfd719e7769fd43f marxin at gcc dot gnu.org
2022-10-10 15:20 ` pinskia at gcc dot gnu.org
2022-10-18  8:33 ` rguenth at gcc dot gnu.org
2022-11-18 14:29 ` jakub at gcc dot gnu.org [this message]
2022-11-18 16:13 ` jakub at gcc dot gnu.org
2022-11-20 16:44 ` cvs-commit at gcc dot gnu.org
2022-11-20 23:11 ` cvs-commit at gcc dot gnu.org
2022-11-21  9:23 ` cvs-commit at gcc dot gnu.org
2022-11-21  9:31 ` [Bug target/107183] [10 " jakub at gcc dot gnu.org
2023-05-03 15:19 ` cvs-commit at gcc dot gnu.org
2023-05-04  7:20 ` 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-107183-4-uCZhUItc21@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: link
Be 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).