From: Richard Earnshaw <rearnsha@arm.com>
To: Jason R Thorpe <thorpej@wasabisystems.com>
Cc: gdb-patches@sources.redhat.com, Richard.Earnshaw@arm.com
Subject: Re: [PATCH/RFA] Updated: Generic OS ABI handling
Date: Wed, 22 May 2002 02:53:00 -0000 [thread overview]
Message-ID: <200205211236.NAA05469@cam-mail2.cambridge.arm.com> (raw)
In-Reply-To: Your message of "Fri, 17 May 2002 13:02:00 PDT." <20020517130200.G14437@dr-evil.shagadelic.org>
thorpej@wasabisystems.com said:
> Changes from the last:
> * Notion of "generic" and "specific" sniffers, and a
> "specific" sniffer added for ARM ELF.
> * Docs updated to reflect above, plus other comments from
> Eli.
> OK to commit?
> * Makefile.in (SFILES): Add osabi.c.
> (COMMON_OBS): Add osabi.o.
> (osabi.o): New dependency list.
> * osabi.c: New file.
> * osabi.h: New file.
> * doc/gdbint.texinfo: Document new generic OS ABI framework.
> * Makefile.in (alpha_tdep_h): Define and use instead of
> alpha-tdep.h.
> * alpha-tdep.c (alpha_abi_names, process_note_abi_tag_sections,
>
> get_elfosabi, alpha_abi_handler_list, alpha_gdbarch_register_os
> _abi):
> Remove.
> (alpha_gdbarch_init, alpha_dump_tdep): Use generic OS ABI
> framework.
> * alpha-tdep.h: Include osabi.h.
> (alpha_abi): Remove.
> (gdbarch_tdep): Use generic OS ABI framework.
> * alpha-linux-tdep.c (_initialize_alpha_linux_tdep): Use
> gdbarch_register_osabi.
> * alpha-osf1-tdep.c (_initialize_alpha_osf1_tdep): Likewise.
> * alphafbsd-tdep.c (_initialize_alphafbsd_tdep): Likewise.
> * alphanbsd-tdep.c (_initialize_alphanbsd_tdep): Likewise.
> * Makefile.in (sh_tdep_h): Add osabi.h.
> * sh-tdep.h (sh_osabi): Remove.
> (gdbarch_tdep): Use generic OS ABI framework.
> * sh-tdep.c (sh_osabi_names, process_note_abi_tag_sections,
> sh_osabi_handler_list, sh_gdbarch_register_os_abi): Remove.
> (sh_gdbarch_init, sh_dump_tdep): Use generic OS ABI framework.
> * shnbsd-tdep.c (_initialize_shnbsd_tdep): Use
> gdbarch_register_osabi.
> * Makefile.in (arm_tdep_h): Define and use instead of
> arm-tdep.h.
> * arm-linux-tdep.c (_initialize_arm_linux_tdep): Use
> gdbarch_register_osabi.
> * arm-tdep.c (arm_abi_names, process_note_abi_tag_sections,
> arm_abi_handler_list, arm_gdbarch_register_os_abi): Remove.
> (get_elfosabi): Rename to...
> (arm_elf_osabi_sniffer): ...this. Adjust to use generic OS
> ABI framework support routines.
> (arm_gdbarch_init): Use generic OS ABI framework.
> (arm_dump_tdep): Likewise.
> (_initialize_arm_tdep): Likewise.
> * arm-tdep.h: Include osabi.h.
> (arm_abi): Remove.
> (gdbarch_tdep): Remove arm_abi and abi_name members. Add
> osabi member.
> (arm_gdbarch_register_os_abi): Remove prototype.
> * armnbsd-tdep.c (arm_netbsd_aout_osabi_sniffer): New
> function.
> (_initialize_arm_netbsd_tdep): Use gdbarch_register_osabi.
> * Makefile.in (mips-tdep.o): Add osabi.h to dependency list.
> * mips-tdep.c: Include osabi.h.
> (gdbarch_tdep, mips_gdbarch_init, mips_dump_tdep): Use generic
> OS ABI framework.
Yes, I think the ARM bits are OK now (though patch is doing its utmost
here to make it hard to be sure ;-)
R.
prev parent reply other threads:[~2002-05-22 9:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-17 13:02 Jason R Thorpe
2002-05-18 3:57 ` Eli Zaretskii
2002-05-22 2:53 ` Richard Earnshaw [this message]
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=200205211236.NAA05469@cam-mail2.cambridge.arm.com \
--to=rearnsha@arm.com \
--cc=Richard.Earnshaw@arm.com \
--cc=gdb-patches@sources.redhat.com \
--cc=thorpej@wasabisystems.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