public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/96513] building terminated with -O3
Date: Fri, 07 Aug 2020 06:03:38 +0000	[thread overview]
Message-ID: <bug-96513-4-t0xnihTkhK@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-96513-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #1 from Marc Glisse <glisse at gcc dot gnu.org> ---
What you could do, even if it is private code, is reduce it
(https://gcc.gnu.org/wiki/A_guide_to_testcase_reduction) until it is very small
and doesn't give away any IP, and then post it. Otherwise, there is not much we
can do from your report and we are probably just going to close it...

  reply	other threads:[~2020-08-07  6:03 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-07  2:31 [Bug c/96513] New: " zhenglin.huang at qdreamer dot com
2020-08-07  6:03 ` glisse at gcc dot gnu.org [this message]
2020-08-07  7:16 ` [Bug tree-optimization/96513] " rguenth at gcc dot gnu.org
2020-08-12  7:39 ` zhenglin.huang at qdreamer dot com
2020-08-12  7:40 ` zhenglin.huang at qdreamer dot com
2020-08-12  7:59 ` glisse at gcc dot gnu.org
2020-08-12  8:11 ` [Bug tree-optimization/96513] [9/10 Regression] ICE in vect_get_vec_def_for_operand_1, at tree-vect-stmts.c:1475 since r9-3644-g4dd7c0dcd87c86aa marxin at gcc dot gnu.org
2021-04-30  8:08 ` rguenth at gcc dot gnu.org
2021-04-30  9:05 ` rguenth at gcc dot gnu.org
2021-04-30  9:15 ` cvs-commit at gcc dot gnu.org
2021-04-30  9:16 ` cvs-commit at gcc dot gnu.org
2021-04-30 11:00 ` cvs-commit at gcc dot gnu.org
2021-05-18  7:05 ` [Bug tree-optimization/96513] [9 " cvs-commit at gcc dot gnu.org
2021-05-18  7:06 ` 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-96513-4-t0xnihTkhK@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).