From: Pedro Alves <palves@redhat.com>
To: Simon Marchi <simon.marchi@polymtl.ca>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 4/5] Make sect_offset and cu_offset strong typedefs instead of structs
Date: Wed, 05 Apr 2017 15:13:00 -0000 [thread overview]
Message-ID: <30bf01d6-31dc-c884-055a-f7c675e17d62@redhat.com> (raw)
In-Reply-To: <ff9cee4d3eee2fbb0eb7273397ead7e1@polymtl.ca>
On 03/29/2017 04:46 PM, Simon Marchi wrote:
> A while ago (in the pre C++ era), I asked you if we could make some
> integer types that couldn't be assigned to each other, to represent
> 8-bit bytes and target bytes. That would help avoid mixing incompatible
> lengths or offsets for targets that have 16 or 32 bit bytes, forcing us
> to do the appropriate conversion. There was no way to do it in C. Do
> you think offset-type could be used for that now?
Indeed, that might work.
Thanks,
Pedro Alves
prev parent reply other threads:[~2017-04-05 15:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-29 2:25 [PATCH 0/5] dwarf2read.c: Some C++fycation Pedro Alves
2017-03-29 2:25 ` [PATCH 5/5] dwarf2read.c: C++fy lnp_state_machine Pedro Alves
2017-03-29 2:25 ` [PATCH 3/5] dwarf2read.c: Make dir_index and file_name_index strong typedefs Pedro Alves
2017-03-29 15:36 ` Simon Marchi
2017-04-04 18:54 ` Pedro Alves
2017-04-04 19:06 ` Pedro Alves
2017-03-29 2:25 ` [PATCH 2/5] gdb::optional: Add observers Pedro Alves
2017-03-29 2:25 ` [PATCH 1/5] dwarf2read.c: Some C++fycation, use std::vector, std::unique_ptr Pedro Alves
[not found] ` <ef286ec115c7c1986e41dd08ecf14fcf@polymtl.ca>
2017-04-04 18:57 ` Pedro Alves
2017-03-29 2:32 ` [PATCH 4/5] Make sect_offset and cu_offset strong typedefs instead of structs Pedro Alves
2017-03-29 15:46 ` Simon Marchi
2017-04-05 15:13 ` Pedro Alves [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=30bf01d6-31dc-c884-055a-f7c675e17d62@redhat.com \
--to=palves@redhat.com \
--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