From: Yao Qi <yao@codesourcery.com>
To: David Taylor <dtaylor@usendtaylorx2l.lss.emc.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: RFA 0/2 fix for bug with large structure offsets
Date: Fri, 12 Dec 2014 03:57:00 -0000 [thread overview]
Message-ID: <87zjaty0ze.fsf@codesourcery.com> (raw)
In-Reply-To: <23959.1418329569@usendtaylorx2l> (David Taylor's message of "Thu, 11 Dec 2014 15:26:09 -0500")
David Taylor <dtaylor@usendtaylorx2l.lss.emc.com> writes:
> In the slightly over three weeks since I posted this and the two related
> parts, I have seen only two replies off list, nothing on list.
>
> This bug is affecting us and I'd like some version of a fix for it to go
> in. Any chance?
It is worried that we can't verify the type width change like this.
Personally, I don't see the point GDB-switch-to-C++ block the changes,
either from your patch or from Fedora GDB's patches, although I agree
that it is easier to do sanity check in C++.
If it is practical to turn on -Wconversion and people here agree to do
so, we can do it first to pave the way for your patch, and convince
people your patch is safe enough. Last time I tried turning
-Wconversion on, it causes a huge number of warnings. :-/
--
Yao (齐尧)
next prev parent reply other threads:[~2014-12-12 3:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-18 16:53 David Taylor
2014-11-23 19:40 ` Jan Kratochvil
2014-12-11 20:26 ` David Taylor
2014-12-12 3:57 ` Yao Qi [this message]
2014-12-12 11:15 ` Pedro Alves
2014-12-19 2:00 ` David Taylor
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=87zjaty0ze.fsf@codesourcery.com \
--to=yao@codesourcery.com \
--cc=dtaylor@usendtaylorx2l.lss.emc.com \
--cc=gdb-patches@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).