From: Orjan Friberg <orjan.friberg@axis.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [CRIS] dwarf2 frame sniffer problem?
Date: Fri, 19 Mar 2004 00:09:00 -0000 [thread overview]
Message-ID: <4051BFDE.8060603@axis.com> (raw)
In-Reply-To: <40518F6A.2080806@axis.com>
Orjan Friberg wrote:
> Ugh, I had totally missed that (i.e. I don't even have a CRIS-specific
> DWARF2_REG_TO_REGNUM). Looking at the other targets' implementations I
> don't understand where they got the dwarf2 register mapping from (though
> amd64-tdep.c mentions System V psABI), and the dwarf2 spec says in
> "2.4.2 Register Name Operators" it should be in the architecture's ABI
> spec. I'll go bug my compiler guy, or go look in gcc myself.
Too trigger happy on the send button... The mn10300 told me where to
find it (gcc/config/cris/cris.h). It seems only the SRP needs special
handling (besides the ones that aren't mapped at all).
--
Orjan Friberg
Axis Communications
WARNING: multiple messages have this Message-ID
From: Orjan Friberg <orjan.friberg@axis.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [CRIS] dwarf2 frame sniffer problem?
Date: Fri, 12 Mar 2004 13:50:00 -0000 [thread overview]
Message-ID: <4051BFDE.8060603@axis.com> (raw)
Message-ID: <20040312135000.FdURGFz8o_hZrPU6-qEvNJFKlovmH5qZwiHZkBCf-tM@z> (raw)
In-Reply-To: <40518F6A.2080806@axis.com>
Orjan Friberg wrote:
> Ugh, I had totally missed that (i.e. I don't even have a CRIS-specific
> DWARF2_REG_TO_REGNUM). Looking at the other targets' implementations I
> don't understand where they got the dwarf2 register mapping from (though
> amd64-tdep.c mentions System V psABI), and the dwarf2 spec says in
> "2.4.2 Register Name Operators" it should be in the architecture's ABI
> spec. I'll go bug my compiler guy, or go look in gcc myself.
Too trigger happy on the send button... The mn10300 told me where to
find it (gcc/config/cris/cris.h). It seems only the SRP needs special
handling (besides the ones that aren't mapped at all).
--
Orjan Friberg
Axis Communications
next prev parent reply other threads:[~2004-03-12 13:50 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-10 16:53 Orjan Friberg
2004-03-10 16:59 ` Daniel Jacobowitz
2004-03-19 0:09 ` Daniel Jacobowitz
2004-03-19 0:09 ` Orjan Friberg
2004-03-11 14:09 ` Orjan Friberg
2004-03-11 15:55 ` Orjan Friberg
2004-03-11 17:05 ` Andrew Cagney
2004-03-19 0:09 ` Orjan Friberg
2004-03-12 12:00 ` Orjan Friberg
2004-03-19 0:09 ` Andrew Cagney
2004-03-11 17:11 ` Daniel Jacobowitz
2004-03-12 10:23 ` Orjan Friberg
2004-03-19 0:09 ` Orjan Friberg [this message]
2004-03-12 13:50 ` Orjan Friberg
2004-03-19 0:09 ` Orjan Friberg
2004-03-12 15:38 ` Orjan Friberg
2004-03-19 0:09 ` Daniel Jacobowitz
2004-03-12 15:38 ` Daniel Jacobowitz
2004-03-15 10:19 ` Orjan Friberg
2004-03-19 0:09 ` Orjan Friberg
2004-03-16 16:26 ` Orjan Friberg
2004-03-16 19:13 ` Daniel Jacobowitz
2004-03-16 20:51 ` Hans-Peter Nilsson
2004-03-16 22:27 ` Daniel Jacobowitz
2004-03-16 23:38 ` Hans-Peter Nilsson
2004-03-16 23:58 ` Daniel Jacobowitz
2004-03-19 0:09 ` Daniel Jacobowitz
2004-03-19 0:09 ` Hans-Peter Nilsson
2004-03-19 0:09 ` Daniel Jacobowitz
2004-03-19 0:09 ` Hans-Peter Nilsson
2004-03-19 0:09 ` Daniel Jacobowitz
2004-03-19 0:09 ` Orjan Friberg
2004-03-19 0:09 ` Orjan Friberg
2004-03-19 0:09 ` Daniel Jacobowitz
2004-03-19 0:09 ` Orjan Friberg
2004-03-19 0:09 ` Orjan Friberg
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=4051BFDE.8060603@axis.com \
--to=orjan.friberg@axis.com \
--cc=drow@false.org \
--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