From: Andrew Cagney <ac131313@redhat.com>
To: Shrinivas Atre <ShrinivasA@kpit.com>
Cc: gcc-patches@gcc.gnu.org, gdb-patches@sources.redhat.com
Subject: Re: [RFA/PATCH]: H8/300 - Update the generated debug information
Date: Tue, 25 Feb 2003 16:55:00 -0000 [thread overview]
Message-ID: <3E5BA097.8090003@redhat.com> (raw)
In-Reply-To: <69595093233BB547BB70CF5E492B63F2DA6751@sohm.kpit.com>
> gdb/ChangeLog
> 2003-02-24 Shrinivas Atre <shrinivasa@kpit.com>
>
> * gdb/h8300-tdep.c (h8300_gdbarch_init): Make default integer size as 32 bits.
>
>
> GDB Patch -
>
> --- gdb/h8300-tdep.orig.c Mon Feb 24 16:47:05 2003
> +++ gdb/h8300-tdep.c Mon Feb 24 16:47:45 2003
> @@ -1170,7 +1170,7 @@ h8300_gdbarch_init (struct gdbarch_info
> set_gdbarch_fix_call_dummy (gdbarch, generic_fix_call_dummy);
> set_gdbarch_breakpoint_from_pc (gdbarch, h8300_breakpoint_from_pc);
>
> - set_gdbarch_int_bit (gdbarch, 2 * TARGET_CHAR_BIT);
> + set_gdbarch_int_bit (gdbarch, 4 * TARGET_CHAR_BIT);
> set_gdbarch_long_bit (gdbarch, 4 * TARGET_CHAR_BIT);
> set_gdbarch_ptr_bit (gdbarch, BINWORD * TARGET_CHAR_BIT);
> set_gdbarch_addr_bit (gdbarch, BINWORD * TARGET_CHAR_BIT);
>
Just FYI, while the above is apparently trivial, the required change isn't.
GCC should be providing information (either via special headers or via
other debug info or magic sections) that informs GDB of the selected
size of an int. GDB can then adjust its configuration accordingly. See
other GDB architectures (MIPS, PPC, SH, ...) that do this.
Andrew
next prev parent reply other threads:[~2003-02-25 16:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-25 5:16 Shrinivas Atre
2003-02-25 16:48 ` Andrew Cagney
2003-02-25 16:55 ` Andrew Cagney [this message]
2003-02-26 4:22 ` Jim Wilson
2003-02-26 5:52 Shrinivas Atre
2003-02-26 5:55 Shrinivas Atre
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=3E5BA097.8090003@redhat.com \
--to=ac131313@redhat.com \
--cc=ShrinivasA@kpit.com \
--cc=gcc-patches@gcc.gnu.org \
--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