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/96058] ICE in c_getstr at gcc/fold-const.c:15475
Date: Sat, 04 Jul 2020 14:09:01 +0000	[thread overview]
Message-ID: <bug-96058-4-LdakLjvPRf@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-96058-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Multi delta should be able to reduce this. Normally reduce which .o files are
needed and then reduce the .ii files that needed to produce the .o files is the
way to reduce this ...

  parent reply	other threads:[~2020-07-04 14:09 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-04  9:16 [Bug tree-optimization/96058] New: " marxin at gcc dot gnu.org
2020-07-04  9:19 ` [Bug tree-optimization/96058] " marxin at gcc dot gnu.org
2020-07-04 14:09 ` pinskia at gcc dot gnu.org [this message]
2020-07-04 16:33 ` marxin at gcc dot gnu.org
2020-07-06  7:19 ` rguenth at gcc dot gnu.org
2020-07-07 11:51 ` marxin at gcc dot gnu.org
2020-07-07 17:59 ` msebor at gcc dot gnu.org
2020-07-07 19:02 ` jakub at gcc dot gnu.org
2020-07-08  7:04 ` marxin at gcc dot gnu.org
2020-07-15  6:54 ` [Bug tree-optimization/96058] [10/11 Regression] " rguenth at gcc dot gnu.org
2020-07-23  6:51 ` rguenth at gcc dot gnu.org
2020-07-23 13:41 ` marxin at gcc dot gnu.org
2020-07-27 10:30 ` marxin at gcc dot gnu.org
2020-07-27 14:18 ` cvs-commit at gcc dot gnu.org
2020-07-27 14:22 ` [Bug tree-optimization/96058] [11 " marxin at gcc dot gnu.org
2020-07-28 10:37 ` cvs-commit at gcc dot gnu.org
2020-07-28 10:39 ` [Bug tree-optimization/96058] " marxin at gcc dot gnu.org
2020-08-18  6:47 ` asolokha at gmx dot com
2020-08-18  7:21 ` marxin at gcc dot gnu.org
2020-08-18  7:21 ` 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-96058-4-LdakLjvPRf@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).