public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "williambader at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/89965] [8 Regression] wrong code with -O -mtune=nano-x2 -fcaller-saves -fexpensive-optimizations -fno-tree-dce -fno-tree-ter
Date: Mon, 15 Mar 2021 00:41:03 +0000	[thread overview]
Message-ID: <bug-89965-4-vyN4hwi5ST@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-89965-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #18 from William Bader <williambader at hotmail dot com> ---
I did a bisection for the bug from my previous comment (which is still present
in the current gcc 11 in master):

058e97ecf33ad0dfd926b3876a4bcf59ac9556ff is the first bad commit
commit 058e97ecf33ad0dfd926b3876a4bcf59ac9556ff
Author: Vladimir Makarov <vmakarov@redhat.com>
Date:   Tue Aug 26 12:39:58 2008 +0000

`git diff '058e97ecf33ad0dfd926b3876a4bcf59ac9556ff^!' | wc -l` shows 16192
lines.

gcc/caller-save.c has a lot of changes. I want it fixed in the current gcc. I
don't care about gcc 4, other than that the git bisect found that the bug was
introduced in a commit to gcc 4. Is it worth trying to fix it in gcc 4, or
would that just waste time making a patch that would not apply to the current
gcc?

      parent reply	other threads:[~2021-03-15  0:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-89965-4@http.gcc.gnu.org/bugzilla/>
2021-03-12  4:11 ` williambader at hotmail dot com
2021-03-15  0:41 ` williambader at hotmail dot com [this message]

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-89965-4-vyN4hwi5ST@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).