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 tree-optimization/103837] [9/10/11/12 Regression] '-fcompare-debug' failure (length) w/ -Og -fmove-loop-invariants -fnon-call-exceptions -fno-tree-dce
Date: Mon, 27 Dec 2021 11:35:12 +0000	[thread overview]
Message-ID: <bug-103837-4-GNWwAMFKmw@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103837-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
It looks like can_move_invariant_reg is not ignoring debug insns.

  parent reply	other threads:[~2021-12-27 11:35 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-26 16:45 [Bug debug/103837] New: [12 " asolokha at gmx dot com
2021-12-26 21:10 ` [Bug debug/103837] " pinskia at gcc dot gnu.org
2021-12-27 11:28 ` [Bug tree-optimization/103837] [9/10/11/12 " jakub at gcc dot gnu.org
2021-12-27 11:35 ` pinskia at gcc dot gnu.org [this message]
2021-12-27 11:40 ` jakub at gcc dot gnu.org
2021-12-27 12:19 ` jakub at gcc dot gnu.org
2021-12-27 12:50 ` [Bug rtl-optimization/103837] " jakub at gcc dot gnu.org
2021-12-28 16:40 ` cvs-commit at gcc dot gnu.org
2021-12-28 16:43 ` [Bug rtl-optimization/103837] [9/10/11 " jakub at gcc dot gnu.org
2022-01-04 13:37 ` rguenth at gcc dot gnu.org
2022-01-24  9:20 ` cvs-commit at gcc dot gnu.org
2022-01-24  9:30 ` [Bug rtl-optimization/103837] [9/10 " jakub at gcc dot gnu.org
2022-05-10  8:22 ` cvs-commit at gcc dot gnu.org
2022-05-11  6:23 ` cvs-commit at gcc dot gnu.org
2022-05-11  6:36 ` jakub 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-103837-4-GNWwAMFKmw@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).