public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: Haoxin Tu <haoxintu@gmail.com>
To: gcc-bugs@gcc.gnu.org
Subject: Re: How GCC treats ice-on-invalid-code?
Date: Tue, 30 Jun 2020 11:09:04 +0800	[thread overview]
Message-ID: <CALDyosbc97mNi6e2eyi57bXirgCAhsnOvbqVQR0O-Y=o4gLJnQ@mail.gmail.com> (raw)
In-Reply-To: <CALDyosbeDaiRKTzDbk4wsnbmLd3trWmZeZcSjE_dOn+xjmUn6g@mail.gmail.com>

I am sorry maybe I send this in a wrong place, I have sent this again in
gcc-bug-request@gcc.gun.org.

Haoxin Tu <haoxintu@gmail.com> 于2020年6月30日周二 上午10:32写道：

> Hi, there,
>
> Our team just develop a c++ code generator tool to testing the compiler,
> and those days I have reported 13 ICE bugs in ice-on-invalid-bugs.
>
> Here are the bugs links:
>
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95972
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95956
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95955
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95954
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95925
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95930
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95931
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95927
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95932
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95935
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95945
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95938
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95937
>
> Until now, only the last two cases are confirmed. So I am wondering that
> how GCC treats with those cases in ice-on-invalid-code? I mean, our team is
> focusing on improving the quality of the mature productive compilers. If
> those bugs are useless for GCC, maybe I should stop reporting similar
> issues.
>
> Waiting for your reply. Thank you very much!
>
>
> Best regrades,
> Haoxin
>


  reply	other threads:[~2020-06-30  3:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-30  2:32 Haoxin Tu
2020-06-30  3:09 ` Haoxin Tu [this message]
2020-06-30 14:28   ` Jonathan Wakely
2020-06-30 13:22 ` Richard Sandiford
2020-06-30 14:38   ` Jonathan Wakely
2020-07-01  8:05     ` Eric Botcazou
2020-07-01 11:24       ` Richard Sandiford
2020-07-02  8:51         ` Eric Botcazou

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='CALDyosbc97mNi6e2eyi57bXirgCAhsnOvbqVQR0O-Y=o4gLJnQ@mail.gmail.com' \
    --to=haoxintu@gmail.com \
    --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).