From: Mike Frysinger <vapier@gentoo.org>
To: Garrett Cooper <yanegomi@gmail.com>
Cc: "ltp-list@lists.sourceforge.net" <ltp-list@lists.sourceforge.net>
Subject: Re: [LTP] LTP Intermediate Release for JULY 2009 Build Failures
Date: Wed, 22 Jul 2009 03:04:32 -0400 [thread overview]
Message-ID: <200907220304.33267.vapier@gentoo.org> (raw)
In-Reply-To: <124D1FD0-1C6A-40D0-9754-DD87A3CF27DC@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1444 bytes --]
On Wednesday 22 July 2009 02:52:25 Garrett Cooper wrote:
> On Jul 21, 2009, at 10:22 PM, Mike Frysinger wrote:
> > On Wednesday 22 July 2009 01:01:34 Garrett Cooper wrote:
> >> On Tue, Jul 21, 2009 at 9:38 PM, Garrett Cooper wrote:
> >>> On Tue, Jul 21, 2009 at 2:28 PM, Mike Frysinger wrote:
> >>>> On Tuesday 21 July 2009 10:21:44 Garrett Cooper wrote:
> >>>>> I was tempted to fix the format string error, but I don't know
> >>>>> what
> >>>>> the potential implications are of switching the data type from
> >>>>> u_int64_t to unsigned long long...
> >>>>
> >>>> dont do that. just use the proper format string from inttypes.h.
> >>>> uint64_t f;
> >>>> printf("f = %"PRIu64"\n", f);
> >>
> >> - fprintf(stdout, "[%u] wait completed on %d: count=%llu\n",
> >> + fprintf(stdout, "[%u] wait completed on %d: count=%lu64\n",
> >> getpid(), fd, cntr);
> >
> > umm, you sure that's right ? seems to me it'll output the number
> > followed by
> > the string "64". i think you need to look at my example again (and
> > take
> > notice of the quote marks).
>
> Your suggestion didn't compile and unfortunately the testcase appears
> to be broken. I'll retest when I get home.
did you include inttypes.h ? i'm pretty sure your proposed change would (1)
fix warnings for one arch size, (2) add warnings for the other arch size, and
(3) add a spurious "64" string to the output.
-mike
[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 79 bytes --]
------------------------------------------------------------------------------
[-- Attachment #3: Type: text/plain, Size: 155 bytes --]
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
prev parent reply other threads:[~2009-07-22 7:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-21 10:25 [LTP] LTP Intermediate Release for JULY 2009 Build Failures CAI Qian
2009-07-21 14:21 ` Garrett Cooper
2009-07-21 21:28 ` Mike Frysinger
2009-07-22 4:38 ` Garrett Cooper
2009-07-22 5:01 ` Garrett Cooper
2009-07-22 5:22 ` Mike Frysinger
2009-07-22 6:52 ` Garrett Cooper
2009-07-22 7:04 ` Mike Frysinger [this message]
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=200907220304.33267.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=ltp-list@lists.sourceforge.net \
--cc=yanegomi@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