From: Joel Brobecker <brobecker@gnat.com>
To: Andrew Cagney <ac131313@redhat.com>
Cc: gdb@sources.redhat.com
Subject: Re: [6] What if EXTRA_FRAME_INFO wasn't required
Date: Mon, 31 Mar 2003 22:32:00 -0000 [thread overview]
Message-ID: <20030331223213.GF916@gnat.com> (raw)
In-Reply-To: <3E878942.3000700@redhat.com>
> The attached appears to drag HP, kicking and screaming, into multi-arch
> partial. It isn't a ``get out of goal free card'' though. HP/UX needs
> to leap-frog all the init frame stuff and start using the latest frame
> code. Otherwize it will just be deleted for relying on deprecated
> mechanisms.
>
> I also don't know if it actually works.
Will try it out. I also identified a few macros that were not converted
yet, but all of them should be easy to do, except one (FIX_CALL_DUMMY)
which I understand should be replaced in the relatively near future.
Can I commit your patch if it turns out to be working, or would you
prefer to do it?
Thanks,
--
Joel
BTW: The next steps in the plan, once HP/UX is multiarch partial, is to
shuffle a bit all the declarations in tm-hppa.h to put them either in
a hppa-tdep.h file, or even hppa-tdep.c if possible. This should help us
reduce the size of tm-hppa.h, and pave the way to its eventual deletion.
Next will be the multi-arching of hppa64, which I hope will be a
reasonably small task, given that hppa is already done.
Then I will look at getting rid of the deprecated mechanisms.
Next (if I'm not dead by then :-) will be to have a look at these
HP-specific macros they added. Maybe I'll even look at them before
working on the use of deprecated functions.
next prev parent reply other threads:[~2003-03-31 22:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-28 21:34 Andrew Cagney
2003-03-28 21:39 ` Joel Brobecker
2003-03-31 0:18 ` Andrew Cagney
2003-03-31 22:32 ` Joel Brobecker [this message]
2003-03-31 23:36 ` Andrew Cagney
2003-04-08 22:08 ` Andrew Cagney
2003-04-08 22:17 ` Joel Brobecker
2003-03-31 22:24 ` Joel Brobecker
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=20030331223213.GF916@gnat.com \
--to=brobecker@gnat.com \
--cc=ac131313@redhat.com \
--cc=gdb@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).