public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/64511] [5 Regression] ICE at -O3 with -g enabled on x86_64-linux-gnu Date: Wed, 21 Jan 2015 10:30:00 -0000 [thread overview] Message-ID: <bug-64511-4-qCcfmLdxnW@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-64511-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64511 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |aoliva at gcc dot gnu.org --- Comment #11 from Jakub Jelinek <jakub at gcc dot gnu.org> --- The #c0 issue is different (with the reorder_operands call commented out), there var-tracking creates a huge (.5GB in text *.vartracking dump) NOTE_INSN_CALL_ARG_LOCATION note and another huge (again about .5GB) NOTE_INSN_VAR_LOCATION note. Don't understand how it got created, we have the various depths limit in var-tracking expansion (expand_depth struct). With --param max-vartrack-expr-depth=11 the testcase still compiles and even the vartrack dump is 10 times smaller than with depth 12, on the other side depth of 12 was needed for various real-world examples. So perhaps we don't need to count just complexity/depth but should count also number of rtxes involved and just give up if it goes over yet another parameter (say 1000 or 10000 rtxes by default). That said, I'd like to fix #c8 independently.
next prev parent reply other threads:[~2015-01-21 10:30 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-01-06 19:01 [Bug c/64511] New: " su at cs dot ucdavis.edu 2015-01-06 21:03 ` [Bug c/64511] [5 Regression] " hjl.tools at gmail dot com 2015-01-06 22:07 ` [Bug debug/64511] " glisse at gcc dot gnu.org 2015-01-08 9:06 ` rguenth at gcc dot gnu.org 2015-01-12 14:51 ` rguenth at gcc dot gnu.org 2015-01-13 12:40 ` rguenth at gcc dot gnu.org 2015-01-13 15:31 ` jakub at gcc dot gnu.org 2015-01-20 17:42 ` jakub at gcc dot gnu.org 2015-01-21 6:38 ` su at cs dot ucdavis.edu 2015-01-21 9:02 ` rguenther at suse dot de 2015-01-21 10:04 ` jakub at gcc dot gnu.org 2015-01-21 10:30 ` jakub at gcc dot gnu.org [this message] 2015-01-21 22:00 ` jakub at gcc dot gnu.org 2015-01-22 7:44 ` su at cs dot ucdavis.edu 2015-01-22 7:48 ` jakub at gcc dot gnu.org 2015-01-22 7:51 ` su at cs dot ucdavis.edu 2015-01-22 14:06 ` jakub at gcc dot gnu.org 2015-02-01 17:32 ` jakub at gcc dot gnu.org 2015-02-01 22:01 ` jakub at gcc dot gnu.org 2015-02-03 20:41 ` aoliva at gcc dot gnu.org 2015-02-04 14:29 ` jakub 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-64511-4-qCcfmLdxnW@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: linkBe 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).