From: Elena Zannoni <ezannoni@redhat.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [RFA] Add parse_dwarf2_calling_convention functionality
Date: Fri, 22 Oct 2004 03:31:00 -0000 [thread overview]
Message-ID: <16760.31952.258767.923659@localhost.redhat.com> (raw)
In-Reply-To: <20041008124826.GZ6702@cygbert.vinschen.de>
Corinna Vinschen writes:
> Hi,
>
> On Oct 7 11:54, Corinna Vinschen wrote:
> > the second patch to prepare the calling convention stuff. It just adds
> > the parse_dwarf2_calling_convention functionality to gdbarch. The
> > below patch contains only the patch to gdbarch.sh (not the auto-generated
> > gdbarch.[ch]) and the new default_parse_dwarf2_calling_convention function
> > in arch-utils.
>
> Corrected patch below. It seems to be more useful to use the producer
> field of the compilation unit instead of an artificial "gcc_compiled"
> flag. The producer string is easily scanned and the information given
> is more detailed than just a gcc_compiled flag.
>
> The below patch overrides the previous patch and also contains the
> necessary change to dwarf2read.c now.
>
> 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.
next prev parent reply other threads:[~2004-10-22 3:31 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 [this message]
2004-10-25 23:03 ` Andrew Cagney
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=16760.31952.258767.923659@localhost.redhat.com \
--to=ezannoni@redhat.com \
--cc=gdb-patches@sources.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