public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/42801] C VLAs should use DW_AT_allocated
Date: Mon, 24 May 2010 14:38:00 -0000	[thread overview]
Message-ID: <20100524143832.4664.qmail@sourceware.org> (raw)
In-Reply-To: <bug-42801-12292@http.gcc.gnu.org/bugzilla/>



------- Comment #3 from jakub at gcc dot gnu dot org  2010-05-24 14:38 -------
Created an attachment (id=20735)
 --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=20735&action=view)
gcc46-pr42801.patch

Patch for the -O2 issue.
The standard says:
"Concrete inlined instance entries may omit attributes that are not specific to
the concrete instance (but present in the abstract instance) and need include
only attributes that are specific to the concrete instance (but omitted in the
abstract instance).", which I read as not forbidding duplication of the
DW_AT_type attribute (dropping DW_AT_type in the abstract instance doesn't seem
to be a good idea, even when bounds aren't known the type otherwise gives
useful info).  Perhaps we should handle DW_TAG_formal_parameters the same way
in dwarf2out.c.
Unfortunately, gdb prints 0 instead of 24 in the second case.


-- 


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


  parent reply	other threads:[~2010-05-24 14:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-19 10:18 [Bug debug/42801] New: " jan dot kratochvil at redhat dot com
2010-01-19 10:58 ` [Bug debug/42801] " jan dot kratochvil at redhat dot com
2010-05-24  8:52 ` jakub at gcc dot gnu dot org
2010-05-24 14:38 ` jakub at gcc dot gnu dot org [this message]
2010-05-24 19:54 ` jan dot kratochvil at redhat dot com
2010-05-25 16:16 ` jakub 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=20100524143832.4664.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: 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).