public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Simon Marchi <simon.marchi@polymtl.ca>
To: John Darrington <john@darrington.wattle.id.au>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 1/3] gdb: Added builtin types for 24 bit integers.
Date: Fri, 24 Aug 2018 20:37:00 -0000	[thread overview]
Message-ID: <33dfdfe9927a6b163deb502b97910081@polymtl.ca> (raw)
In-Reply-To: <20180824152934.bvs2y2t6py4vbynn@jocasta.intra>

On 2018-08-24 11:29, John Darrington wrote:
> On Fri, Aug 24, 2018 at 11:09:40AM -0400, Simon Marchi wrote:
> 
>      I'm not sure I understand.  I was only talking about the 
> definition of
>      the int24_t and uint24_t types, not the handling of 
> DW_EH_PE_udata3.
>      From what I read, the C99 standard mandates that the 8, 16, 32 and 
> 64
>      variants of the intX_t/uintX_t types exist.  Other types (with 
> other
>      values of X) would be extensions.  That's why I thought it would 
> make
>      sense to define that in the s12z-specific gdbarches only.  In the 
> end I
>      don't really mind, but it just looks like the "clean" way to do it 
> and
>      doesn't seem really more difficult.  Can you see if the attached 
> diff
>      (applied on top of your series) work for you?
> 
> 
> Yes, I see no reason why that shouldn't work.  Like you say, C99 et. 
> al.
> doesn't require uint24_t but doesn't prohibit it either.  I just
> thought, that it makes sense to keep all these type definitions in the
> same place so as to avoid the next 24 bit arch having to copy this
> definition.   But I don't have a strong opinion either way.

I see, then that's fine with mean to have it in gdbarch.

Simon

      reply	other threads:[~2018-08-24 20:37 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
2018-08-24 15:09         ` Simon Marchi
2018-08-24 15:29           ` John Darrington
2018-08-24 20:37             ` Simon Marchi [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=33dfdfe9927a6b163deb502b97910081@polymtl.ca \
    --to=simon.marchi@polymtl.ca \
    --cc=gdb-patches@sourceware.org \
    --cc=john@darrington.wattle.id.au \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).