From: Andrew Cagney <cagney@gnu.org>
To: Randolph Chung <tausq@debian.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch/resend/rfa] (2/4) Cleanup tm-hppa.h for multiarch.
Date: Thu, 15 Apr 2004 17:16:00 -0000 [thread overview]
Message-ID: <407EC36B.3080308@gnu.org> (raw)
In-Reply-To: <20040414062442.GK31873@tausq.org>
> obj_private_struct): Move to hppa-tdep.h.
This has been superseeded by objfile_data() (grep for examples).
Looking at the HP code it seems to contain two things:
- unwind info (unwind_info)
- shlib info (so_info, dp)
First, how much of this is used by GNU/Linux? If it isn't it can get
burried in hppa-hpux-tdep.[hc]. If it is (well the unwind_info bit I
migiht be? then that should be split out to its own private objfile_data.
Andrew
next prev parent reply other threads:[~2004-04-15 17:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-14 6:24 Randolph Chung
2004-04-15 16:22 ` Andrew Cagney
2004-04-17 17:21 ` Randolph Chung
2004-04-15 16:28 ` Andrew Cagney
2004-04-15 16:37 ` Randolph Chung
2004-04-15 17:16 ` Andrew Cagney [this message]
2004-04-15 17:26 ` Randolph Chung
2004-04-15 18:45 ` 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=407EC36B.3080308@gnu.org \
--to=cagney@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=tausq@debian.org \
/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