public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "qing.zhao at oracle dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/99421] ICE:in code_motion_process_successors, at sel-sched.c:6389 on aarch64
Date: Tue, 09 Mar 2021 16:39:33 +0000	[thread overview]
Message-ID: <bug-99421-4-4o2KEka34i@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99421-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #8 from Qing Zhao <qing.zhao at oracle dot com> ---
> On Mar 8, 2021, at 11:58 AM, marxin at gcc dot gnu.org <gcc-bugzilla@gcc.gnu.org> wrote:
> 
> Sure. I used C-Vise:
> https://github.com/marxin/cvise

>From my understanding, cvise is similar as creduce, but faster.
So, I am still wondering why creduce cannot reduce testing cases when using
profiling feedback due to
Profiling mismatch? But cvise can do this? Does Cvise reduce source code and
.gcda file at the same 
time?

  parent reply	other threads:[~2021-03-09 16:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-05 20:31 [Bug rtl-optimization/99421] New: " qinzhao at gcc dot gnu.org
2021-03-06  8:30 ` [Bug rtl-optimization/99421] " marxin at gcc dot gnu.org
2021-03-06 16:33 ` qinzhao at gcc dot gnu.org
2021-03-08  8:16 ` marxin at gcc dot gnu.org
2021-03-08  8:16 ` marxin at gcc dot gnu.org
2021-03-08 15:39 ` qinzhao at gcc dot gnu.org
2021-03-08 17:58 ` marxin at gcc dot gnu.org
2021-03-09  9:49 ` marxin at gcc dot gnu.org
2021-03-09  9:50 ` marxin at gcc dot gnu.org
2021-03-09 16:39 ` qing.zhao at oracle dot com [this message]
2021-03-09 17:12 ` marxin 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-99421-4-4o2KEka34i@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).