From: Martin Hunt <hunt@redhat.com>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: Hien Nguyen <hien@us.ibm.com>, SystemTAP <systemtap@sources.redhat.com>
Subject: Re: nightly test result of systemtap in ppc64
Date: Mon, 10 Apr 2006 21:05:00 -0000 [thread overview]
Message-ID: <1144703141.2527.4.camel@dragon> (raw)
In-Reply-To: <y0mk69xkvs5.fsf@ton.toronto.redhat.com>
On Mon, 2006-04-10 at 16:42 -0400, Frank Ch. Eigler wrote:
> Hien Nguyen <hien@us.ibm.com> writes:
>
> > powerpc does not like [%lld vs int64_t]
> > but likes this [%lld vs (long long)]
> > or this [%ld vs int64_t]
> > could it be a compiler bug?
>
> More likely a "pilot error" in the new code.
If you mean I checked in a new vsnprintf() but not a new snprintf(), you
are right. I'll get that checked in.
When writing vsnprintf(), I changed %lld to expect int64_t instead of
"long long". And then I forgot to also check in a new snprintf(). That's
the reason for the errors.
Martin
next prev parent reply other threads:[~2006-04-10 21:05 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-10 18:30 Hien Nguyen
2006-04-10 20:19 ` Hien Nguyen
2006-04-10 20:28 ` Roland McGrath
2006-04-10 20:42 ` Frank Ch. Eigler
2006-04-10 20:53 ` Roland McGrath
2006-04-10 21:05 ` Martin Hunt [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-05-15 20:44 Hien Nguyen
2006-05-09 18:46 Stone, Joshua I
2006-05-10 16:19 ` Hien Nguyen
2006-05-09 18:19 Stone, Joshua I
2006-05-09 18:29 ` Hien Nguyen
2006-05-09 17:59 Stone, Joshua I
2006-05-09 18:02 ` Hien Nguyen
2006-05-09 17:28 Hien Nguyen
2006-04-24 18:16 Nightly " Hien Nguyen
2006-04-24 18:55 ` Frank Ch. Eigler
2006-04-24 22:18 ` Hien Nguyen
2006-05-01 21:53 ` Hien Nguyen
[not found] ` <20060503021650.GC11017@redhat.com>
[not found] ` <4458FFA2.3090802@us.ibm.com>
2006-05-07 22:52 ` Frank Ch. Eigler
2006-03-27 19:35 Hien Nguyen
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=1144703141.2527.4.camel@dragon \
--to=hunt@redhat.com \
--cc=fche@redhat.com \
--cc=hien@us.ibm.com \
--cc=systemtap@sources.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).