From: Tom Tromey <tromey@redhat.com>
To: Mark Wielaard <mjw@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Handle volatile array types in dwarf2read.c.
Date: Tue, 01 Jul 2014 18:25:00 -0000 [thread overview]
Message-ID: <87ionhq6mg.fsf@fleche.redhat.com> (raw)
In-Reply-To: <1404238306.3766.17.camel@bordewijk.wildebeest.org> (Mark Wielaard's message of "Tue, 01 Jul 2014 20:11:45 +0200")
Mark> But we have to look anyway. This is just the existing code, moved into
Mark> its own function. What do you suggest should be changed?
It's fine to leave it.
Tom> make_cv_type preserves the already existing qualifiers so you don't need
Tom> to track "cnst" and "voltl". You can just pass in the ones you want to
Tom> add.
Mark> The original code already did it this way. And I don't think it is true
Mark> that make_cv_type preserves existing const or volatile qualifiers.
Wow, I wonder how long I've had the incorrect view of make_cv_type.
Hopefully not too long. Thanks for pointing that out.
Tom> I wonder about typedefs to array type.
Tom> Calling check_typedef here is probably not so great but I assume we can
Tom> just ignore incomplete types.
Mark> I am not sure I understand precisely what you are wondering about. Do
Mark> you have an example? Then I can add a testcase for it. This is just
Mark> precisely as is done for the const case. So the issue you are thinking
Mark> about is probably the same for both cases and might already be existing.
Well, I was thinking this:
typedef int atype[23];
const atype a;
However, gcc omits the typedef from the DWARF, so I suppose some
hand-crafted DWARF would have to be written.
This patch is ok. If there's a further bug and you want to fix it, it's
fine to do that separately.
Tom
next prev parent reply other threads:[~2014-07-01 18:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-30 21:35 Mark Wielaard
2014-07-01 16:05 ` Tom Tromey
2014-07-01 18:11 ` Mark Wielaard
2014-07-01 18:25 ` Tom Tromey [this message]
2014-07-01 20:15 ` Mark Wielaard
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=87ionhq6mg.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=mjw@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