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/106609] [12/13 Regression] sh3eb-elf cross compiler is being miscompiled since r12-1525-g3155d51bfd1de8b6c4645
Date: Thu, 24 Nov 2022 13:13:49 +0000 [thread overview]
Message-ID: <bug-106609-4-E9UUUBrmIO@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106609-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106609
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed| |2022-11-24
Status|UNCONFIRMED |NEW
CC| |jakub at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #13 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
(In reply to Mikael Pettersson from comment #12)
> I tried compiling the gcc-13 cross compiler using the broken gcc-12 host
> compiler and -mtune-ctrl=^use_bt but that didn't help.
>
> I then tried rebuilding the broken gcc-12 host compiler with the new
> splitters disabled, one by one. Disabling the "*bt<mode>_setcqi" one did
> unbreak the gcc-13 cross-compiler:
>
> diff --git a/gcc/config/i386/i386.md b/gcc/config/i386/i386.md
> index 48532eb7ddf..0780ba992f3 100644
> --- a/gcc/config/i386/i386.md
> +++ b/gcc/config/i386/i386.md
> @@ -12830,7 +12830,7 @@
> (const_int 1)
> (zero_extend:SI (match_operand:QI 2 "register_operand"))))
> (clobber (reg:CC FLAGS_REG))]
> - "TARGET_USE_BT && ix86_pre_reload_split ()"
> + "0 && TARGET_USE_BT && ix86_pre_reload_split ()"
> "#"
> "&& 1"
> [(set (reg:CCC FLAGS_REG)
Ok, reproduced with last night's gcc trunk as the x86_64-linux system compiler
(with/without the above patch) and r12-8924-ga6b1f6126de5e4 as 12 branch for
the cross-compiler. The difference appears first in the
sh_treg_combine2 dump
-not a condition store
-other set found - aborting trace
+inverted condition store
+tracing ccreg
+set of ccreg not found
+
+cbranch trace summary:
etc.
And bisection points to insn-preds.o.
next prev parent reply other threads:[~2022-11-24 13:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-13 17:31 [Bug c/106609] New: [SH] miscompilation of loop involving noreturn call sebastien.michelland@ens-lyon.fr
2022-08-15 8:28 ` [Bug middle-end/106609] " rguenth at gcc dot gnu.org
2022-08-15 9:47 ` sebastien.michelland@ens-lyon.fr
2022-08-15 15:52 ` [Bug target/106609] " pinskia at gcc dot gnu.org
2022-08-16 21:03 ` [Bug target/106609] [SH] miscompilation due to incorrect elimination of comparisons to 0 sebastien.michelland@ens-lyon.fr
2022-08-16 21:03 ` sebastien.michelland@ens-lyon.fr
2022-08-17 8:09 ` sebastien.michelland@ens-lyon.fr
2022-11-24 13:13 ` jakub at gcc dot gnu.org [this message]
2022-11-24 14:38 ` [Bug target/106609] [12 Regression] sh3eb-elf cross compiler is being miscompiled since r12-1525-g3155d51bfd1de8b6c4645 jakub at gcc dot gnu.org
2022-11-24 17:04 ` sebastien.michelland@ens-lyon.fr
2023-02-28 23:08 ` sam at gentoo dot org
2023-05-08 12:25 ` rguenth 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-106609-4-E9UUUBrmIO@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).