From: Andrew Cagney <cagney@gnu.org>
To: Kevin Buettner <kevinb@redhat.com>
Cc: gdb-patches@sources.redhat.com,
peter.schauer@regent.e-technik.tu-muenchen.de
Subject: Re: [rfa:rs6000] Framefy rs6000 (and GNU/Linux PPC)
Date: Wed, 03 Mar 2004 15:36:00 -0000 [thread overview]
Message-ID: <4045FB6B.9080700@gnu.org> (raw)
Message-ID: <20040303153600.1B1cgs50NFj4MgwKxALGPSC3yujUo2GtjuM-r44Dq_E@z> (raw)
In-Reply-To: <20040302160100.573bbadc@saguaro>
This will leave AIX. At present it is handled with the blatant hack:
+ default:
+ set_gdbarch_deprecated_save_dummy_frame_tos (gdbarch,
generic_save_dummy_frame_tos);
+ set_gdbarch_believe_pcc_promotion (gdbarch, 1);
+ set_gdbarch_deprecated_pop_frame (gdbarch, rs6000_pop_frame);
+ set_gdbarch_deprecated_frame_args_address (gdbarch,
rs6000_frame_args_address);
+ set_gdbarch_deprecated_frame_locals_address (gdbarch,
rs6000_frame_args_address);
+ set_gdbarch_deprecated_saved_pc_after_call (gdbarch,
rs6000_saved_pc_after_call);
+ set_gdbarch_deprecated_frameless_function_invocation (gdbarch,
rs6000_frameless_function_invocation);
+ set_gdbarch_deprecated_frame_chain (gdbarch, rs6000_frame_chain);
+ set_gdbarch_deprecated_frame_saved_pc (gdbarch,
rs6000_frame_saved_pc);
+ set_gdbarch_deprecated_frame_init_saved_regs (gdbarch,
rs6000_frame_init_saved_regs);
+ set_gdbarch_deprecated_init_extra_frame_info (gdbarch,
rs6000_init_extra_frame_info);
+ set_gdbarch_deprecated_init_frame_pc_first (gdbarch,
rs6000_init_frame_pc_first);
while that might be ok for the 6.1 branch, I don't think it is ok for
the mainline. We've already waited too long for someone to frameify the
PPC :-( Do you or Peter have timely plans for fixing that part of the code?
>>> static void
>>> ppc_linux_init_abi (struct gdbarch_info info,
>>> struct gdbarch *gdbarch)
>>> @@ -1051,6 +1157,7 @@
>>> PowerOpen struct convention. */
>>> set_gdbarch_return_value (gdbarch, ppc_linux_return_value);
>>>
>>> +#if 0
>>> /* Note: kevinb/2002-04-12: See note in rs6000_gdbarch_init regarding
>>> *_push_arguments(). The same remarks hold for the methods below. */
>>> set_gdbarch_deprecated_frameless_function_invocation (gdbarch, ppc_linux_frameless_function_invocation);
>>> @@ -1061,9 +1168,11 @@
>>> ppc_linux_frame_init_saved_regs);
>>> set_gdbarch_deprecated_init_extra_frame_info (gdbarch,
>>> ppc_linux_init_extra_frame_info);
>>> +#endif
>
>
> Is there any reason to retain this #if 0'd code?
With this patch approved, deleting the #if0 and removing the unused
functions becomes an "obvious" cleanups.
Andrew
next prev parent reply other threads:[~2004-03-03 15:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-01 1:18 Andrew Cagney
2004-03-02 23:01 ` Kevin Buettner
2004-03-19 0:09 ` Kevin Buettner
2004-03-19 0:09 ` Andrew Cagney [this message]
2004-03-03 15:36 ` Andrew Cagney
2004-03-15 18:28 ` Andrew Cagney
2004-03-19 0:09 ` Kevin Buettner
2004-03-15 20:15 ` Kevin Buettner
2004-03-19 0:09 ` Andrew Cagney
2004-03-15 22:51 ` Andrew Cagney
2004-03-16 15:56 ` Kevin Buettner
2004-03-19 0:09 ` Kevin Buettner
2004-03-19 0:09 ` Andrew Cagney
2004-03-19 0:09 ` Andrew Cagney
2004-03-20 5:03 ` Kevin Buettner
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=4045FB6B.9080700@gnu.org \
--to=cagney@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=kevinb@redhat.com \
--cc=peter.schauer@regent.e-technik.tu-muenchen.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