public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/109777] [14 regression] Compare-debug failure after recent changes
Date: Mon, 08 May 2023 19:52:23 +0000 [thread overview]
Message-ID: <bug-109777-4-Anb2V02Oxk@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109777-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109777
--- Comment #5 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Jeffrey A. Law from comment #4)
> If it's inside the bfin bundling code, let's just mark it as a p4 and we can
> chase it down whenever it's convenient. My primary motivation is to catch
> generic issues. A target specific issue on a barely used target just isn't
> that interesting IMHO.
Thanks, it actaully might be the scheduler which is introducing the difference
such that bfin bundling is different.
I just noticed the modes of the two instructions:
(insn:SI # # # 6 (set (reg:SI 3 R3 [177])
(ashift:SI (reg:SI 4 R4 [orig:87 x$0 ] [87])
(const_int 1 [0x1]))) "t.c":44:47# {*ashlsi3_insn}
(nil))
vs with -g:
(insn:TI # # # 6 (set (reg:SI 3 R3 [177])
(ashift:SI (reg:SI 4 R4 [orig:87 x$0 ] [87])
(const_int 1 [0x1]))) "t.c":44:47# {*ashlsi3_insn}
(nil))
---
I think this is caused by having the debug insn afterwards:
(debug_insn # # # 6 (var_location:SI D#14 (ior:SI (reg:SI 3 R3 [177])
(const_int 31 [0x1f])))#
(nil))
which might be saying it is scheduled with the above one while without -g, it
is not schedule with another instruction; hence the SImode.
next prev parent reply other threads:[~2023-05-08 19:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-08 18:20 [Bug tree-optimization/109777] New: " law at gcc dot gnu.org
2023-05-08 18:38 ` [Bug middle-end/109777] " pinskia at gcc dot gnu.org
2023-05-08 18:51 ` [Bug target/109777] " pinskia at gcc dot gnu.org
2023-05-08 19:05 ` pinskia at gcc dot gnu.org
2023-05-08 19:37 ` law at gcc dot gnu.org
2023-05-08 19:52 ` pinskia at gcc dot gnu.org [this message]
2024-05-07 7:40 ` [Bug target/109777] [14/15 " 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-109777-4-Anb2V02Oxk@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).