public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ro at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/115028] New: [15 regression] gcc.target/i386/pr101950-2.c FAILs Date: Fri, 10 May 2024 12:56:24 +0000 [thread overview] Message-ID: <bug-115028-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115028 Bug ID: 115028 Summary: [15 regression] gcc.target/i386/pr101950-2.c FAILs Product: gcc Version: 15.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: ro at gcc dot gnu.org Target Milestone: --- Target: i386-pc-solaris2.11 Between 20240506 (80c03ac8041340b29325f86ed58ea8bd40a55b99) and 20240507 (bf10f0db20db1598157505b373098bc93c66b915), the 64-bit gcc.target/i386/pr101950-2.c test regressed on Solaris/x86: FAIL: gcc.target/i386/pr101950-2.c scan-assembler-times \\txor[ql]\\t 2 There are 3 instances of xor[ql] now instead of the expected two: xorq %rax, %rdi xorl %eax, %edi xorl %eax, %eax where the gcc-14 branch has xorq %rdi, %rax xorl %edi, %eax The additional one is from @@ -20,8 +20,9 @@ .LFB1: movl %edi, %eax sarl $31, %eax - xorl %edi, %eax - lzcntl %eax, %eax + xorl %eax, %edi + xorl %eax, %eax + lzcntl %edi, %eax subl $1, %eax ret .LFE1: I'm attaching both gcc-14 and trunk assembler output.
next reply other threads:[~2024-05-10 12:56 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-05-10 12:56 ro at gcc dot gnu.org [this message] 2024-05-10 12:58 ` [Bug target/115028] " ro at gcc dot gnu.org 2024-05-10 12:59 ` ro at gcc dot gnu.org 2024-05-10 13:31 ` ro at gcc dot gnu.org 2024-05-10 13:45 ` rguenth at gcc dot gnu.org 2024-05-15 13:10 ` ro at gcc dot gnu.org 2024-05-15 15:13 ` haochen.jiang at intel dot com 2024-05-15 16:17 ` rguenth at gcc dot gnu.org 2024-05-17 3:08 ` lingling.kong7 at gmail 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=bug-115028-4@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).