public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "xry111 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/109086] Bug of builtin_strcmp in the case of using the adddi3 instruction patterns
Date: Wed, 15 Mar 2023 02:04:46 +0000	[thread overview]
Message-ID: <bug-109086-4-EsnTYtE4ZW@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109086-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #7 from Xi Ruoyao <xry111 at gcc dot gnu.org> ---
Things are already wrong in 255r:

(jump_insn 17 16 42 4 (set (pc)
        (if_then_else (ne (reg:DI 90)
                (const_int 0 [0]))
            (label_ref 20)
            (pc))) "t.c":4:23 discrim 1 -1
     (int_list:REG_BR_PROB 536870916 (nil))
 -> 20)
(note 42 17 18 5 [bb 5] NOTE_INSN_BASIC_BLOCK)
(insn 18 42 19 5 (set (reg:SI 91)
        (zero_extend:SI (mem:QI (plus:DI (reg/v/f:DI 82 [ filename ])
                    (const_int 1 [0x1])) [0 MEM <char[1:2]> [(void
*)filename_3(D)]+1 S1 A8]))) "t.c":4:23 discrim 1 -1
     (nil))
(insn 19 18 20 5 (set (reg:DI 92)
        (plus:DI (subreg:DI (reg:SI 91) 0)
            (const_int 0 [0]))) "t.c":4:23 discrim 1 -1
     (nil))
(code_label 20 19 43 6 3 (nil) [1 uses])
(note 43 20 21 6 [bb 6] NOTE_INSN_BASIC_BLOCK)
(insn 21 43 22 6 (set (reg:DI 80 [ _1 ])
        (sign_extend:DI (subreg:SI (reg:DI 92) 0))) "t.c":4:23 discrim 1 -1
     (nil))

Note that the jump_insn jumps over insn 19 which initializes the vreg 92 (which
would become r13).

  parent reply	other threads:[~2023-03-15  2:04 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-10  7:36 [Bug target/109086] New: " liwei at loongson dot cn
2023-03-10  7:38 ` [Bug target/109086] " liwei at loongson dot cn
2023-03-10  8:18 ` [Bug rtl-optimization/109086] " rguenth at gcc dot gnu.org
2023-03-10  9:31 ` liwei at loongson dot cn
2023-03-10 13:12 ` rguenth at gcc dot gnu.org
2023-03-14 14:59 ` xry111 at gcc dot gnu.org
2023-03-15  2:00 ` xry111 at gcc dot gnu.org
2023-03-15  2:04 ` xry111 at gcc dot gnu.org [this message]
2023-03-15  2:17 ` liwei at loongson dot cn
2023-03-15  3:02 ` xry111 at gcc dot gnu.org
2023-03-15  4:52 ` liwei at loongson dot cn
2023-03-15  7:33 ` [Bug other/109086] __builtin_strcmp generates wrong code if expand_simple_binop assigns new pseudo-register for result xry111 at gcc dot gnu.org
2023-03-15  7:36 ` rguenth at gcc dot gnu.org
2023-03-15  9:28 ` cvs-commit at gcc dot gnu.org
2023-03-15  9:29 ` xry111 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-109086-4-EsnTYtE4ZW@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).