From: Mark Kettenis <kettenis@chello.nl>
To: cagney@gnu.org
Cc: gdb-patches@sources.redhat.com, eliz@is.elta.co.il
Subject: Re: [patch/rfc] Separate gdbarch_data_register_pre_init
Date: Mon, 08 Mar 2004 22:41:00 -0000 [thread overview]
Message-ID: <200403082241.i28MfAcH000896@elgar.kettenis.dyndns.org> (raw)
In-Reply-To: <404CC940.70805@gnu.org> (message from Andrew Cagney on Mon, 08 Mar 2004 14:28:00 -0500)
Date: Mon, 08 Mar 2004 14:28:00 -0500
From: Andrew Cagney <cagney@gnu.org>
The dwarf2-frame code is then modified to use the first mechanism. I've
left the other clients alone (but did deprecate set_gdbarch_data as that
should now be redundant).
I'm not so sure that set_gdbarch_data is now redundant. I can imagine
that one would like to set a per-architecture data thingy to a
different value after its initial initialization. So I'd rather you
wouldn't deprecate the interface.
Also note the name changes (better suggestions?).
The names look fine to me.
Mark
WARNING: multiple messages have this Message-ID
From: Mark Kettenis <kettenis@chello.nl>
To: cagney@gnu.org
Cc: gdb-patches@sources.redhat.com, eliz@is.elta.co.il
Subject: Re: [patch/rfc] Separate gdbarch_data_register_pre_init
Date: Fri, 19 Mar 2004 00:09:00 -0000 [thread overview]
Message-ID: <200403082241.i28MfAcH000896@elgar.kettenis.dyndns.org> (raw)
Message-ID: <20040319000900.d3t775egMWXMWLhu680mskY-0lUOp3OQQ_NcfJkWJ48@z> (raw)
In-Reply-To: <404CC940.70805@gnu.org> (message from Andrew Cagney on Mon, 08 Mar 2004 14:28:00 -0500)
Date: Mon, 08 Mar 2004 14:28:00 -0500
From: Andrew Cagney <cagney@gnu.org>
The dwarf2-frame code is then modified to use the first mechanism. I've
left the other clients alone (but did deprecate set_gdbarch_data as that
should now be redundant).
I'm not so sure that set_gdbarch_data is now redundant. I can imagine
that one would like to set a per-architecture data thingy to a
different value after its initial initialization. So I'd rather you
wouldn't deprecate the interface.
Also note the name changes (better suggestions?).
The names look fine to me.
Mark
next prev parent reply other threads:[~2004-03-08 22:41 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-08 19:28 Andrew Cagney
2004-03-08 22:41 ` Mark Kettenis [this message]
2004-03-19 0:09 ` Mark Kettenis
2004-03-19 0:09 ` Andrew Cagney
2004-03-08 23:51 ` Andrew Cagney
2004-03-15 20:44 ` Andrew Cagney
2004-03-19 0:09 ` Andrew Cagney
2004-03-19 0:09 ` Andrew Cagney
2004-03-15 17:21 ` Andrew Cagney
2004-03-15 19:55 ` Eli Zaretskii
2004-03-15 21:13 ` Andrew Cagney
2004-03-17 11:30 ` Eli Zaretskii
2004-03-19 0:09 ` Andrew Cagney
2004-03-19 0:09 ` Eli Zaretskii
2004-03-19 0:09 ` Andrew Cagney
2004-03-15 21:18 ` Andrew Cagney
2004-03-19 0:09 ` Andrew Cagney
2004-03-19 0:09 ` Eli Zaretskii
2004-03-19 0:09 ` Andrew Cagney
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=200403082241.i28MfAcH000896@elgar.kettenis.dyndns.org \
--to=kettenis@chello.nl \
--cc=cagney@gnu.org \
--cc=eliz@is.elta.co.il \
--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