Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: John Darrington <john@darrington.wattle.id.au>
To: Simon Marchi <simon.marchi@polymtl.ca>
Cc: John Darrington <john@darrington.wattle.id.au>,
	gdb-patches@sourceware.org
Subject: Re: [PATCH 1/3] gdb: Added builtin types for 24 bit integers.
Date: Fri, 24 Aug 2018 06:11:00 -0000	[thread overview]
Message-ID: <20180824061125.7vjvlopdx4bstg4l@jocasta.intra> (raw)
In-Reply-To: <603c98bc68bec04acb84d809c838abb0@polymtl.ca>

On Thu, Aug 23, 2018 at 04:35:25PM -0400, Simon Marchi wrote:

     It is clear now, but somebody doing a git blame to know why 24-bit
     integer types were added would only find the patch that adds them by
     itself and wonder who uses that.  A little message like
     
       This patch adds 24-bit integer types, used when debugging on the S12Z
     architecture (added by a later patch in this series).
     
     clears that up.  That might looks a bit silly, but I think it helps in
     the long run.

I fully agree with you.   I've worked on other projects however had a
different opinion - they insisted that the checkin comment NOT contain
any rationale for the change, instead it should just summarize what
changed.  I find that rather pointless but anyway ....
     
     > It seems that up till now there has been no 24 bit targets, so the
     > other
     > two patches as some necessary things to make that possible.
     
     Thanks.  Coming back to the code of the patch, I was wondering if these
     24-bit types are useful or even relevant for any other architecture.

There most certainly are plenty of 24 bit architectures  especially in the 
embedded world  - just apparently none that gdb currently supports :(

     Would it work if you only defined the types for s12z architectures,
     storing the reference in the gdbarch_tdep object?

My first reaction is that it probably *could* be made to work, but not 
in an elegant fashion.   Somehow I'd have to avoid that gdb ever calls the 
read_encoded_value function. 

I do concede that  adding DW_EH_PE_udata3 might be problematic since
it's not part of the dwarf standard.  An alternative might be to rework
the read_encoded_value function to not rely on the dwarf enums (all it
really cares about is the size of the target's address space.

Regards

John




-- 
Avoid eavesdropping.  Send strong encrypted email.
PGP Public key ID: 1024D/2DE827B3 
fingerprint = 8797 A26D 0854 2EAB 0285  A290 8A67 719C 2DE8 27B3
See http://sks-keyservers.net or any PGP keyserver for public key.


  reply	other threads:[~2018-08-24  6:11 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-23 17:35 John Darrington
2018-08-23 17:35 ` [PATCH 2/3] GDB: Add support for 24 bit addresses John Darrington
2018-08-24 20:34   ` Simon Marchi
2018-08-25  4:56     ` John Darrington
2018-08-23 17:35 ` [PATCH 3/3] GDB: New target s12z John Darrington
2018-08-23 17:56   ` Eli Zaretskii
2018-08-26 17:19   ` Simon Marchi
2018-08-26 17:41     ` John Darrington
2018-08-26 18:16       ` Simon Marchi
2018-08-26 22:55         ` Simon Marchi
2018-08-27  6:30           ` John Darrington
2018-08-27 12:54             ` Simon Marchi
2018-08-28 15:35         ` Tom Tromey
2018-08-23 17:55 ` [PATCH 1/3] gdb: Added builtin types for 24 bit integers Eli Zaretskii
2018-08-23 19:41 ` Simon Marchi
2018-08-23 20:04   ` John Darrington
2018-08-23 20:35     ` Simon Marchi
2018-08-24  6:11       ` John Darrington [this message]
2018-08-24 15:09         ` Simon Marchi
2018-08-24 15:29           ` John Darrington
2018-08-24 20:37             ` Simon Marchi

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=20180824061125.7vjvlopdx4bstg4l@jocasta.intra \
    --to=john@darrington.wattle.id.au \
    --cc=gdb-patches@sourceware.org \
    --cc=simon.marchi@polymtl.ca \
    /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