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/51570] [4.7/4.8 Regression] FAIL: gcc.dg/guality/pr45003-[23].c Date: Fri, 13 Apr 2012 15:56:00 -0000 [thread overview] Message-ID: <bug-51570-4-PmaGtdCzdj@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-51570-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51570 --- Comment #7 from Alexandre Oliva <aoliva at gcc dot gnu.org> 2012-04-13 15:56:00 UTC --- Author: aoliva Date: Fri Apr 13 15:55:52 2012 New Revision: 186420 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=186420 Log: PR debug/51570 * var-tracking.c (expand_depth): New type. (onepart_aux, expand_loc_callback_data): Change depth type to it. (loc_exp_dep_alloc): Adjust initializer. (update_depth): Use new type. Add entryvals. (vt_expand_var_loc_chain): Take note of expansions with ENTRY_VALUEs, but don't accept them right away. Run an optional second pass accepting the minimum ENTRY_VALUE count found in the first pass. (vt_expand_loc_callback, INIT_ELCD): Adjust. Modified: trunk/gcc/ChangeLog trunk/gcc/var-tracking.c
next prev parent reply other threads:[~2012-04-13 15:56 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-12-15 16:12 [Bug debug/51570] New: [4.7 " rguenth at gcc dot gnu.org 2011-12-15 16:28 ` [Bug debug/51570] " rguenth at gcc dot gnu.org 2011-12-16 9:15 ` jakub at gcc dot gnu.org 2012-01-19 12:55 ` rguenth at gcc dot gnu.org 2012-01-19 13:04 ` jakub at gcc dot gnu.org 2012-02-27 10:38 ` rguenth at gcc dot gnu.org 2012-02-28 7:12 ` aoliva at gcc dot gnu.org 2012-03-22 9:19 ` [Bug debug/51570] [4.7/4.8 " rguenth at gcc dot gnu.org 2012-04-13 15:56 ` aoliva at gcc dot gnu.org [this message] 2012-04-18 0:25 ` [Bug debug/51570] [4.7 " aoliva at gcc dot gnu.org 2012-06-14 8:41 ` rguenth at gcc dot gnu.org 2012-09-20 10:28 ` jakub at gcc dot gnu.org 2012-11-08 3:06 ` aoliva 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-51570-4-PmaGtdCzdj@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).