public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "burnus at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/39791] [4.3 Regression] Bad Dwarf debug information from gfortran for a character string. Date: Fri, 24 Apr 2009 07:19:00 -0000 [thread overview] Message-ID: <20090424071937.19523.qmail@sourceware.org> (raw) In-Reply-To: <bug-39791-17588@http.gcc.gnu.org/bugzilla/> ------- Comment #3 from burnus at gcc dot gnu dot org 2009-04-24 07:19 ------- Subject: Bug 39791 Author: burnus Date: Fri Apr 24 07:19:12 2009 New Revision: 146672 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=146672 Log: 2009-04-24 Tobias Burnus <burnus@net-b.de> PR fortran/39791 Backport from mainline: 2008-08-22 Jakub Jelinek <jakub@redhat.com> * dwarf2out.c (add_subscript_info): Stop on Fortran * TYPE_STRING_FLAG types. (gen_array_type_die): Emit DW_TAG_string_type for Fortran character types. Modified: branches/gcc-4_3-branch/gcc/ChangeLog branches/gcc-4_3-branch/gcc/dwarf2out.c -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39791
next prev parent reply other threads:[~2009-04-24 7:19 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-04-17 1:45 [Bug fortran/39791] New: " david dot sagan at gmail dot com 2009-04-17 4:40 ` [Bug fortran/39791] " burnus at gcc dot gnu dot org 2009-04-21 17:45 ` [Bug fortran/39791] [4.3 Regression] " pinskia at gcc dot gnu dot org 2009-04-22 13:35 ` rguenth at gcc dot gnu dot org 2009-04-24 7:19 ` burnus at gcc dot gnu dot org [this message] 2009-04-24 7:25 ` burnus at gcc dot gnu dot org 2009-05-11 9:17 ` burnus at gcc dot gnu dot 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=20090424071937.19523.qmail@sourceware.org \ --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).