From: Andrew Cagney <cagney@gnu.org>
To: Mark Kettenis <kettenis@chello.nl>
Cc: drow@false.org, weigand@i1.informatik.uni-erlangen.de,
gdb-patches@gcc.gnu.org
Subject: Re: [PATCH/RFC] Per-architecture DWARF CFI register state initialization hooks
Date: Wed, 18 Feb 2004 18:40:00 -0000 [thread overview]
Message-ID: <4033B1A6.5060508@gnu.org> (raw)
In-Reply-To: <200402181658.i1IGwAUp000574@elgar.kettenis.dyndns.org>
> Thanks Andrew. Can't say I'm too happy with yet another function, but
> if that's the it's supposed to work... Perhaps we should revisit the
> way these per-architecture keys work someday.
It's how it works. Revising how it is supposed to work at some stage
would be useful..
Andrew
next prev parent reply other threads:[~2004-02-18 18:40 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-16 1:28 Ulrich Weigand
2004-02-16 1:56 ` Daniel Jacobowitz
2004-02-16 13:01 ` Ulrich Weigand
2004-02-16 19:47 ` Daniel Jacobowitz
2004-02-16 20:50 ` Andrew Cagney
2004-02-16 20:55 ` Andrew Cagney
2004-02-18 16:59 ` Mark Kettenis
2004-02-18 18:40 ` Andrew Cagney [this message]
2004-02-16 21:31 ` [PATCH/RFC] Per-architecture DWARF CFI register state initialization Ulrich Weigand
-- strict thread matches above, loose matches on Subject: below --
2004-02-07 22:38 [PATCH/RFC] Per-architecture DWARF CFI register state initialization hooks Mark Kettenis
2004-02-07 23:03 ` Daniel Jacobowitz
2004-02-07 23:48 ` Andrew Cagney
2004-02-15 15:31 ` Mark Kettenis
2004-02-15 16:04 ` Andrew Cagney
2004-02-15 18:09 ` Daniel Jacobowitz
2004-02-15 19:49 ` Andrew Cagney
2004-02-15 20:37 ` Daniel Jacobowitz
2004-02-15 21:37 ` Andrew Cagney
2004-02-15 22:54 ` Daniel Jacobowitz
2004-02-15 21:31 ` Mark Kettenis
2004-02-08 1:01 ` Ulrich Weigand
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=4033B1A6.5060508@gnu.org \
--to=cagney@gnu.org \
--cc=drow@false.org \
--cc=gdb-patches@gcc.gnu.org \
--cc=kettenis@chello.nl \
--cc=weigand@i1.informatik.uni-erlangen.de \
/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