public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "aoliva at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/53135] [4.7/4.8 Regression] internal compiler error: in value_format, at dwarf2out.c:8010
Date: Tue, 07 Aug 2012 02:28:00 -0000	[thread overview]
Message-ID: <bug-53135-4-BpFTMcDgP0@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-53135-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53135

--- Comment #7 from Alexandre Oliva <aoliva at gcc dot gnu.org> 2012-08-07 02:26:55 UTC ---
Created attachment 27954
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=27954
Patch that fixes (or works around?) the problem

We have a relatively large expression to represent the outgoing “mode”
parameter, computed from “perms”, that requires more than 64KiB to represent. 
block2 is not enough for that.  Jakub, is it intentional that we ICE in this
case, or is this patch a reasonable change?  We successfully output the
location expression; surely 64KiB+ expressions might be excessive, but I don't
think an ICE is the most desirable way to deal with such large expressions if
we build them in the first place.


  parent reply	other threads:[~2012-08-07  2:28 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-27  5:59 [Bug c++/53135] New: " raj.khem at gmail dot com
2012-04-27  6:00 ` [Bug c++/53135] " raj.khem at gmail dot com
2012-07-13  7:29 ` [Bug debug/53135] " dushistov at mail dot ru
2012-07-13  7:41 ` [Bug debug/53135] [4.7/4.8 Regression] " rguenth at gcc dot gnu.org
2012-07-14 22:18 ` dushistov at mail dot ru
2012-07-15 18:36 ` mikpe at it dot uu.se
2012-07-24 13:03 ` ramana at gcc dot gnu.org
2012-08-07  1:55 ` aoliva at gcc dot gnu.org
2012-08-07  2:28 ` aoliva at gcc dot gnu.org [this message]
2012-08-07 18:48 ` aoliva at gcc dot gnu.org
2012-08-20 14:04 ` jakub at gcc dot gnu.org
2012-09-07 11:30 ` rguenth at gcc dot gnu.org
2012-09-20 10:28 ` jakub at gcc dot gnu.org
2012-09-27 18:48 ` pinskia at gcc dot gnu.org
2012-10-02 20:05 ` aoliva at gcc dot gnu.org
2012-10-02 20:18 ` aoliva at gcc dot gnu.org
2012-10-03  4:03 ` aoliva at gcc dot gnu.org
2013-01-20  6:25 ` [Bug debug/53135] Duplicates cause size explosion (vta/dwarf) law at redhat dot com
2013-04-11  7:58 ` rguenth at gcc dot gnu.org
2014-06-12 13:53 ` rguenth at gcc dot gnu.org
2022-11-04 20:26 ` ramana at gcc dot gnu.org
2022-11-05  1:04 ` law at gcc dot gnu.org
2022-11-05  8:19 ` ramana 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-53135-4-BpFTMcDgP0@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).