From: Andrew Cagney <cagney@gnu.org>
To: Corinna Vinschen <vinschen@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] Add parse_dwarf2_calling_convention functionality
Date: Mon, 25 Oct 2004 23:03:00 -0000 [thread overview]
Message-ID: <417D85E8.7000805@gnu.org> (raw)
In-Reply-To: <16760.31952.258767.923659@localhost.redhat.com>
Elena Zannoni wrote:
> Corinna Vinschen writes:
> > Hi,
> >
> > Corinna
> >
> > * gdbarch.sh (parse_dwarf2_calling_convention): New method.
> > * gdbarch.h, gdbarch.c: Re-generate.
> > * arch-utils.c (default_parse_dwarf2_calling_convention): New function.
> > * arch-utils.h (default_parse_dwarf2_calling_convention): New extern
> > declaration.
> > * dwarf2read.c (read_subroutine_type): Evaluate
> > DW_AT_calling_convention attribute and call
> > gdbarch_parse_dwarf2_calling_convention appropriately.
>
>
> The dwarf2read.c part is approved if the rest gets approved.
One mod, rather than adding this:
> +# Evaluate DW_AT_calling_convention value and convert in a calling_convention
> +# value in the functions main type.
> +m::void:parse_dwarf2_calling_convention:int has_attr, unsigned long attr_val, unsigned char gcc_compiled, struct type *func_type:has_attr, attr_val, gcc_compiled, func_type:0:default_parse_dwarf2_calling_convention::0
to the architecture vector, take a look at:
13.2 Per-architecture module data
http://sources.redhat.com/gdb/current/onlinedocs/gdbint_13.html#SEC114
it lets dwarf2 locally manage that method while still being
per-architecture.
Andrew
next prev parent reply other threads:[~2004-10-25 23:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-07 9:53 Corinna Vinschen
2004-10-08 12:47 ` Corinna Vinschen
2004-10-22 3:31 ` Elena Zannoni
2004-10-25 23:03 ` Andrew Cagney [this message]
2004-12-14 16:36 ` Corinna Vinschen
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=417D85E8.7000805@gnu.org \
--to=cagney@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=vinschen@redhat.com \
/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