Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Hui Zhu <teawater@gmail.com>
To: Phil Muldoon <pmuldoon@redhat.com>
Cc: gdb-patches ml <gdb-patches@sourceware.org>,
	Tom Tromey <tromey@redhat.com>,  	Eli Zaretskii <eliz@gnu.org>
Subject: Re: [python][patch] And range method to type
Date: Wed, 09 Dec 2009 03:00:00 -0000	[thread overview]
Message-ID: <daef60380912081900w689031d8mdbaab7ed40e14e0@mail.gmail.com> (raw)
In-Reply-To: <4B1E5F1C.4030202@redhat.com>

Hi,

I make the cvs-head get:
gcc -g -O2   -I. -I../../src/gdb -I../../src/gdb/common
-I../../src/gdb/config -DLOCALEDIR="\"/usr/local/share/locale\""
-DHAVE_CONFIG_H -I../../src/gdb/../include/opcode
-I../../src/gdb/../readline/.. -I../bfd -I../../src/gdb/../bfd
-I../../src/gdb/../include -I../libdecnumber
-I../../src/gdb/../libdecnumber  -I../../src/gdb/gnulib -Ignulib
-DMI_OUT=1 -DTUI=1  -DGDBTK  -Wall -Wdeclaration-after-statement
-Wpointer-arith -Wformat-nonliteral -Wno-pointer-sign -Wno-unused
-Wunused-value -Wno-switch -Wno-char-subscripts -Werror -c -o
py-type.o -MT py-type.o -MMD -MP -MF .deps/py-type.Tpo
-fno-strict-aliasing -DNDEBUG -fwrapv ../../src/gdb/python/py-type.c
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
make[2]: *** [py-type.o] Error 1
make[2]: Leaving directory `/home/teawater/gdb/cvs/bgdb/gdb'
make[1]: *** [all-gdb] Error 2
make[1]: Leaving directory `/home/teawater/gdb/cvs/bgdb'
make: *** [all] Error 2

Thanks,
Hui

On Tue, Dec 8, 2009 at 22:13, Phil Muldoon <pmuldoon@redhat.com> wrote:
>
>> Phil> I've regenerated the patch. Thanks for the review! What do you think?
>
>>>>>>> On 12/07/2009 07:54 PM, Tom Tromey wrote:
>
>> Ok.
>
>>>>>>> On 12/04/2009 03:32 PM, Eli Zaretskii wrote:
>
>> The gdb.texinfo part is OK with me.
>
> Committed, thanks.
>
> Cheers,
>
> Phil
>


  reply	other threads:[~2009-12-09  3:00 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 [this message]
2009-12-09  7:47           ` Phil Muldoon
2009-12-09 11:27             ` Eli Zaretskii
2009-12-09 11:41               ` Andreas Schwab
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=daef60380912081900w689031d8mdbaab7ed40e14e0@mail.gmail.com \
    --to=teawater@gmail.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=pmuldoon@redhat.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