Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Shrinivas Atre" <ShrinivasA@kpit.com>
To: "Jim Wilson" <wilson@tuliptree.org>, <gcc-patches@gcc.gnu.org>,
	<gdb-patches@gcc.gnu.org>
Subject: RE: [RFA/PATCH]: H8/300 - Update the generated debug information
Date: Wed, 26 Feb 2003 05:55:00 -0000	[thread overview]
Message-ID: <69595093233BB547BB70CF5E492B63F2DA6B7C@sohm.kpit.com> (raw)

Hi Jim,

Thank you for review and suggestions.

> The SDB/coff debug format is old, limited, and unextensible.  It is 
> almost always wrong to use it.  Since you are using gdb, a better 
> solution is to use stabs which doesn't have this problem.
> 

Yes. This is problem of the COFF format. This is not observed in stabs or ELF.

> Or, alternatively, if you must fix the SDB/coff debug info, I suggest 
> doing the same thing Andrew Cagney suggested.  Make gcc emit a special
> directive (.int32) and/or pass an option to gas.  Have gas set an ELF 
> section header flag when it sees the directive or the option.  Then 
> modify gdb to set the int size appropriately depending on the ELF 
> section header flags.
> 

I will try to implement this.

> > 	* gcc/sdbout.c (plain_type_1): Update COFF debug output 
> information.
> > 					Output "short int" if 
> integer size is 16 bit.
> 
> This isn't OK.  It is wrong to emit a type of "short int" for 
> an "int" even if they are the same size, because they aren't the same 
> type.  This will break the gdb testsuite.

Thanks. I missed it out.

Regards,
Shrinivas


             reply	other threads:[~2003-02-26  5:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-26  5:55 Shrinivas Atre [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-02-26  5:52 Shrinivas Atre
2003-02-25  5:16 Shrinivas Atre
2003-02-25 16:48 ` Andrew Cagney
2003-02-25 16:55 ` Andrew Cagney
2003-02-26  4:22 ` Jim Wilson

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=69595093233BB547BB70CF5E492B63F2DA6B7C@sohm.kpit.com \
    --to=shrinivasa@kpit.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gdb-patches@gcc.gnu.org \
    --cc=wilson@tuliptree.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