From: "Joseph S. Myers" <joseph@codesourcery.com>
To: Nathan Froyd <froydnj@codesourcery.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [lto] handle function types without argument types
Date: Thu, 06 Dec 2007 22:24:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.0712062223110.16377@digraph.polyomino.org.uk> (raw)
In-Reply-To: <20071206220400.GP14706@codesourcery.com>
On Thu, 6 Dec 2007, Nathan Froyd wrote:
> Joseph, do you know if there's an easy may to ensure that full argument
> type information makes it from the C front-end all the way to DWARF? Or
> are there problems with doing that (presumably the current approach has
> some reason for being the way it is)?
In C terms, argument types from an old-style declaration (in
DECL_ARGUMENTS, not TYPE_ARG_TYPES) are not part of the function type. I
don't know enough about DWARF to judge if including them in the type in
debug info nevertheless, but not marking that declaration with
DW_AT_prototyped, would be incorrect or cause problems with DWARF
consumers.
--
Joseph S. Myers
joseph@codesourcery.com
prev parent reply other threads:[~2007-12-06 22:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-06 22:04 Nathan Froyd
2007-12-06 22:24 ` Joseph S. Myers [this message]
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=Pine.LNX.4.64.0712062223110.16377@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=froydnj@codesourcery.com \
--cc=gcc-patches@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).