Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jiang Jilin <freephp@gmail.com>
To: Hui Zhu <teawater@gmail.com>
Cc: gdb-patches ml <gdb-patches@sourceware.org>,
	Michael Snyder <msnyder@vmware.com>
Subject: Re: [PATCH] Fix cygwin build error with i386-linux-tdep.c
Date: Mon, 31 Aug 2009 00:32:00 -0000	[thread overview]
Message-ID: <7d77a27d0908301652t570159a6ncf4adf479a47ddc5@mail.gmail.com> (raw)
In-Reply-To: <daef60380908301643k1463ee38vc300700543a1e2a0@mail.gmail.com>

On Mon, Aug 31, 2009 at 7:43 AM, Hui Zhu<teawater@gmail.com> wrote:
> On Mon, Aug 31, 2009 at 07:39, Jiang Jilin<freephp@gmail.com> wrote:
>> On Sun, Aug 30, 2009 at 11:22 PM, Hui Zhu<teawater@gmail.com> wrote:
>>> On Sun, Aug 30, 2009 at 23:13, Jiang Jilin<freephp@gmail.com> wrote:
>>>> On Sun, Aug 30, 2009 at 9:15 PM, Hui Zhu<teawater@gmail.com> wrote:
>>>>> Hi guys,
>>>>>
>>>>>   if (tmpu32 > 499)
>>>>>     {
>>>>>       printf_unfiltered (_("Process record and replay target doesn't "
>>>>> -                           "support syscall number %u\n"), tmpu32);
>>>>> +                           "support syscall number %u\n"), (unsigned) tmpu32);
>>>>>       return -1;
>>>>>     }
>>>>>
>>>>
>>>> Sorry, it's not clear to me.
>>>>
>>>> when looking into the code, I found the type of tmpu32 is uint32_t,
>>>> why did the gcc complain "warning: unsigned int format, uint32_t arg
>>>> (arg 2)"?
>>>>
>>>> %u doesn't mean unsigned int?
>>>>
>>>
>>> Really?  what does it mean?
>>
>> I mean without your patch, the type of tmpu32 _is_ uint32_t, why did
>> gcc complain? and when you cast it to unsigned, the warning
>> disappeared?
>>
>
> I am not sure the unit32_t in cygwin.  But it looks like uint32_t is
> not unsigned int in cygwin.
> And "unsigned" is seems "unsigned int".

If it's true, that is, uint32_t is not unsigned int in cygwin,  I
think there is a  bug in cygwin, we should redefine the uint32_t to
real unsigned int, shouldn't we?



-- 
Thanks

Jiang


  reply	other threads:[~2009-08-30 23:53 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-30 13:56 Hui Zhu
2009-08-30 14:09 ` Mark Kettenis
2009-08-30 14:20   ` Hui Zhu
2009-08-30 15:00     ` Hui Zhu
2009-08-31  8:46       ` Hui Zhu
2009-08-31  8:49         ` Jiang Jilin
2009-08-31 12:05           ` Hui Zhu
2009-08-31 16:33             ` Mark Kettenis
2009-09-01  2:15               ` Hui Zhu
2009-09-05 20:34         ` Michael Snyder
2009-09-05 21:15           ` Joel Brobecker
2009-09-06  4:15             ` Hui Zhu
2009-09-09  2:22               ` Hui Zhu
2009-09-09  3:31                 ` Michael Snyder
2009-09-09  5:59                   ` Hui Zhu
2009-08-30 14:37   ` Andreas Schwab
2009-08-30 15:14     ` Hui Zhu
2009-08-30 15:22 ` Jiang Jilin
2009-08-30 18:00   ` Hui Zhu
2009-08-30 23:43     ` Jiang Jilin
2009-08-30 23:53       ` Hui Zhu
2009-08-31  0:32         ` Jiang Jilin [this message]
2009-08-31  2:52           ` Jiang Jilin

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=7d77a27d0908301652t570159a6ncf4adf479a47ddc5@mail.gmail.com \
    --to=freephp@gmail.com \
    --cc=gdb-patches@sourceware.org \
    --cc=msnyder@vmware.com \
    --cc=teawater@gmail.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