public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mark at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/57369] type-less DW_TAG_const_type
Date: Tue, 25 Feb 2014 11:25:00 -0000	[thread overview]
Message-ID: <bug-57369-4-QxSZrgV9ke@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-57369-4@http.gcc.gnu.org/bugzilla/>

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

Mark Wielaard <mark at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mark at gcc dot gnu.org

--- Comment #1 from Mark Wielaard <mark at gcc dot gnu.org> ---
Replicated with GNU C++ 4.9.0 20140219 (experimental)

 [   219]    typedef
             name                 (strp) "__compar_fn_t"
             decl_file            (data1) 5
             decl_line            (data2) 742
             type                 (ref4) [   225]
 [   225]    pointer_type
             byte_size            (data1) 8
             type                 (ref4) [   22b]
 [   22b]    subroutine_type
             type                 (ref4) [   12b]
             sibling              (ref4) [   23f]
 [   234]      formal_parameter
               type                 (ref4) [   23f]
 [   239]      formal_parameter
               type                 (ref4) [   23f]
 [   23f]    pointer_type
             byte_size            (data1) 8
             type                 (ref4) [   245]
 [   245]    const_type

The DW_TAG_const_type at 245 doesn't have any attributes.

The typedef is defined in /usr/include/stdlib.h as:
typedef int (*__compar_fn_t) (__const void *, __const void *);


      reply	other threads:[~2014-02-25 11:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-22 14:00 [Bug debug/57369] New: " tromey at gcc dot gnu.org
2014-02-25 11:25 ` mark at gcc dot gnu.org [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=bug-57369-4-QxSZrgV9ke@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: 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).