public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "luoxhu at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/61837] missed loop invariant expression optimization Date: Mon, 13 Apr 2020 10:31:28 +0000 [thread overview] Message-ID: <bug-61837-4-jJs2Rdnvo0@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-61837-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61837 --- Comment #5 from luoxhu at gcc dot gnu.org --- "-O2 -funswitch-loops" could generate expected code for s<=0, unswitch-loops is enabled by -O3, so this issue is reduced to duplicate of PR67288? foo: .LFB0: .cfi_startproc cmpwi 0,5,0 blelr 0 rldicl 5,5,0,32 addi 4,4,-1 li 6,0 li 7,0 .p2align 4,,15 .L2: rldicl 8,5,0,32 mr 10,4 mtctr 8 mr 9,3 .p2align 5 .L5: lbzu 8,1(10) cmpw 0,8,7 bne 0,.L4 stw 6,0(9) .L4: addi 9,9,4 bdnz .L5 addi 6,6,88 addi 7,7,1 cmpwi 0,6,8888 extsw 7,7 extsw 6,6 bne 0,.L2 blr .long 0 .byte 0,0,0,0,0,0,0,0 .cfi_endproc .LFE0:
next prev parent reply other threads:[~2020-04-13 10:31 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-61837-4@http.gcc.gnu.org/bugzilla/> 2020-04-07 7:30 ` luoxhu at gcc dot gnu.org 2020-04-07 16:37 ` segher at gcc dot gnu.org 2020-04-13 10:31 ` luoxhu at gcc dot gnu.org [this message] 2020-04-14 6:42 ` segher at gcc dot gnu.org 2020-04-14 7:01 ` luoxhu at gcc dot gnu.org 2020-04-14 7:26 ` segher at gcc dot gnu.org 2020-04-14 7:52 ` luoxhu at gcc dot gnu.org 2020-04-14 10:37 ` rguenth at gcc dot gnu.org 2020-05-15 3:27 ` cvs-commit at gcc dot gnu.org 2021-07-29 0:43 ` cvs-commit at gcc dot gnu.org 2021-08-12 2:17 ` guojiufu 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-61837-4-jJs2Rdnvo0@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).