public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/104054] [9/10/11/12 Regression] '-fcompare-debug' failure (length) w/ -Os -funroll-loops since r8-3946-gfe94440235cfaa57
Date: Mon, 17 Jan 2022 12:38:43 +0000	[thread overview]
Message-ID: <bug-104054-4-wQr3hIB3ul@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104054-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from Uroš Bizjak <ubizjak at gmail dot com> ---
Could be a red herring, but in _.rnreg dump:

Register r9 (1): 75 [GENERAL_REGS] 18 [ALL_REGS] 97 [GENERAL_REGS]
Register r10 (1): 76 [GENERAL_REGS] 18 [ALL_REGS] 23 [GENERAL_REGS]
...
Register di (1): 55 [ALL_REGS]

the pass w/ -g also records hard registers in debug insns. Probably this drives
some decisions to make different choices with respect to register renaming.

  parent reply	other threads:[~2022-01-17 12:38 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-16 17:54 [Bug debug/104054] New: '-fcompare-debug' failure (length) w/ -Os -funroll-loops asolokha at gmx dot com
2022-01-17 10:44 ` [Bug debug/104054] [9/10/11/12 Regression] '-fcompare-debug' failure (length) w/ -Os -funroll-loops since r8-3946-gfe94440235cfaa57 marxin at gcc dot gnu.org
2022-01-17 10:54 ` [Bug rtl-optimization/104054] " pinskia at gcc dot gnu.org
2022-01-17 12:22 ` ubizjak at gmail dot com
2022-01-17 12:24 ` ubizjak at gmail dot com
2022-01-17 12:38 ` ubizjak at gmail dot com [this message]
2022-01-17 17:45 ` jakub at gcc dot gnu.org
2022-01-18 13:47 ` rguenth at gcc dot gnu.org
2022-01-19 10:56 ` ubizjak at gmail dot com
2022-01-19 12:52 ` ubizjak at gmail dot com
2022-05-27  9:47 ` [Bug rtl-optimization/104054] [10/11/12/13 " rguenth at gcc dot gnu.org
2022-06-28 10:47 ` jakub at gcc dot gnu.org
2023-02-03  9:44 ` ubizjak at gmail dot com
2023-07-07 10:42 ` [Bug rtl-optimization/104054] [11/12/13/14 " 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-104054-4-wQr3hIB3ul@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).