From: Andreas Schwab <schwab@linux-m68k.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Phil Muldoon <pmuldoon@redhat.com>,
teawater@gmail.com, gdb-patches@sourceware.org,
tromey@redhat.com
Subject: Re: [python][patch] And range method to type
Date: Wed, 09 Dec 2009 11:41:00 -0000 [thread overview]
Message-ID: <m2tyw0cr32.fsf@igel.home> (raw)
In-Reply-To: <E1NIKhl-0003Bi-Un@fencepost.gnu.org> (Eli Zaretskii's message of "Wed, 09 Dec 2009 06:27:37 -0500")
Eli Zaretskii <eliz@gnu.org> writes:
>> > I make the cvs-head get:
>>
>> > cc1: warnings being treated as errors
>> > ../../src/gdb/python/py-type.c: In function 'typy_range':
>> > ../../src/gdb/python/py-type.c:285: warning: 'high' may be used
>> > uninitialized in this function
>> > ../../src/gdb/python/py-type.c:285: warning: 'low' may be used
>> > uninitialized in this function
>>
>> I do not see this on my build at all.
>
> Are you compiling without optimizations, per chance? AFAIK, this
> warning is only produced in optimized compilations.
Recent gcc versions are also much better at tracking values.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2009-12-09 11:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-04 15:25 Phil Muldoon
2009-12-04 15:32 ` Eli Zaretskii
2009-12-04 17:10 ` Phil Muldoon
2009-12-04 19:30 ` Eli Zaretskii
2009-12-04 17:19 ` Joel Brobecker
2009-12-04 18:13 ` Tom Tromey
2009-12-05 9:19 ` Phil Muldoon
2009-12-05 9:22 ` Eli Zaretskii
2009-12-07 19:54 ` Tom Tromey
2009-12-08 14:14 ` Phil Muldoon
2009-12-09 3:00 ` Hui Zhu
2009-12-09 7:47 ` Phil Muldoon
2009-12-09 11:27 ` Eli Zaretskii
2009-12-09 11:41 ` Andreas Schwab [this message]
2009-12-09 7:52 ` Phil Muldoon
2009-12-09 7:56 ` Hui Zhu
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=m2tyw0cr32.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=pmuldoon@redhat.com \
--cc=teawater@gmail.com \
--cc=tromey@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