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/51517] [4.5/4.6/4.7 Regression] Wrong debug information for pointers with negative strides. Date: Wed, 14 Dec 2011 15:20:00 -0000 [thread overview] Message-ID: <bug-51517-4-jmZfOGQvwI@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-51517-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51517 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED AssignedTo|unassigned at gcc dot |jakub at gcc dot gnu.org |gnu.org | --- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> 2011-12-14 15:14:22 UTC --- Created attachment 26081 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=26081 gcc47-pr51517.patch Untested fix. OT, can anyone please explain the following in trans-decl.c (gfc_trans_deferred_vars): else if ((!sym->attr.dummy || sym->ts.deferred) && (sym->ts.type == BT_CLASS && CLASS_DATA (sym)->attr.pointer)) break; ? The break there will IMHO just cause the rest of the *->tlink chain deferred vars not to be processed at all, is that the right thing to do? continue; or ; would make much more sense to me...
next prev parent reply other threads:[~2011-12-14 15:14 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-12-12 21:58 [Bug debug/51517] New: [4.4 regression ] " nikolay at totalviewtech dot com 2011-12-13 11:21 ` [Bug debug/51517] [4.5/4.6/4.7 Regression] " rguenth at gcc dot gnu.org 2011-12-14 14:37 ` jakub at gcc dot gnu.org 2011-12-14 15:20 ` jakub at gcc dot gnu.org [this message] 2011-12-15 11:09 ` jakub at gcc dot gnu.org 2011-12-15 11:11 ` [Bug debug/51517] [4.5/4.6 " jakub at gcc dot gnu.org 2012-02-09 17:14 ` jakub at gcc dot gnu.org 2012-06-20 13:12 ` [Bug debug/51517] [4.5 " rguenth at gcc dot gnu.org 2012-07-02 10:20 ` 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-51517-4-jmZfOGQvwI@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).