ChatGPT解决这个技术问题 Extra ChatGPT

How do you format an unsigned long long int using printf?

#include <stdio.h>
int main() {
    unsigned long long int num = 285212672; //FYI: fits in 29 bits
    int normalInt = 5;
    printf("My number is %d bytes wide and its value is %ul. A normal number is %d.\n", sizeof(num), num, normalInt);
    return 0;
}

Output:

My number is 8 bytes wide and its value is 285212672l. A normal number is 0.

I assume this unexpected result is from printing the unsigned long long int. How do you printf() an unsigned long long int?

I just compiled your code ( with %llu ) with gcc and the output was the correct one. Are you passing any options to the compiler?
Note that samsung bada's newlib seems not to support "%lld" : developer.bada.com/forum/…
I would suggest using using stdint.h and being explicit about the number of bits in your variable. We're still in a period of transition between 32 and 64 bit architectures, and "unsigned long long int" doesn't mean the same thing on both.

r
rogerdpack

Use the ll (el-el) long-long modifier with the u (unsigned) conversion. (Works in windows, GNU).

printf("%llu", 285212672);

Or to be precise it's for GNU libc, and doesn't work with Microsoft's C runtime.
This isn't a Linux/UNIX thing, the "ll" length modifier was added to Standard C in C99, if it doesn't work in "Microsoft C" then it is because they are not standards compliant.
Works for me in VS2008. Moreover, as far as I remember the MS C Compiler (when set up to compile straight C) is supposed to be C90 compliant by design; C99 introduced some things that not everyone liked.
One thing to keep in mind here is that if you are passing multiple long long arguments to printf and use the wrong format for one of them, say %d instead of %lld, then even the arguments printed after the incorrect one may be completely off (or can even cause printf to crash). Essentially, variable arguments are passed to printf without any type information, so if the format string is incorrect, the result is unpredictable.
Heard Herb Sutter say in an interview that Microsoft's customers don't ask for C99 so their pure C compiler has been frozen at C90. That applies if you are compiling as C. If you compile as C++, as others have noted above, you should be fine.
S
SSpoke

%d--> for int

%u--> for unsigned int

%ld--> for long int or long

%lu--> for unsigned long int or long unsigned int or unsigned long

%lld--> for long long int or long long

%llu--> for unsigned long long int or unsigned long long


N
Nathan Fellman

You may want to try using the inttypes.h library that gives you types such as int32_t, int64_t, uint64_t etc. You can then use its macros such as:

uint64_t x;
uint32_t y;

printf("x: %"PRId64", y: %"PRId32"\n", x, y);

This is "guaranteed" to not give you the same trouble as long, unsigned long long etc, since you don't have to guess how many bits are in each data type.


where these PRId64, PRId32 macros defined?
@happy_marmoset: they are defined in inttypes.h
I think you need PRIu64 and PRIu32 for unsigned integers.
Is inttypes.h standard? Wouldn't it be stdint.h?
Note that these exact-width types are optional, as there are architectures out there that do not have integer types of those exact widths. Only the leastX and fastX types (which may actually be wider than indicated) are mandatory.
佚名

For long long (or __int64) using MSVS, you should use %I64d:

__int64 a;
time_t b;
...
fprintf(outFile,"%I64d,%I64d\n",a,b);    //I is capital i

t
tofutim

That is because %llu doesn't work properly under Windows and %d can't handle 64 bit integers. I suggest using PRIu64 instead and you'll find it's portable to Linux as well.

Try this instead:

#include <stdio.h>
#include <inttypes.h>

int main() {
    unsigned long long int num = 285212672; //FYI: fits in 29 bits
    int normalInt = 5;
    /* NOTE: PRIu64 is a preprocessor macro and thus should go outside the quoted string. */
    printf("My number is %d bytes wide and its value is %" PRIu64 ". A normal number is %d.\n", sizeof(num), num, normalInt);
    return 0;
}

Output

My number is 8 bytes wide and its value is 285212672. A normal number is 5.

+1 for the reference to PRIu64, which I had never seen, but this doesn't seem portable to 64 bit Linux (at least) because PRIu64 expands to "lu" instead of "llu".
And why would that be bad? A long is a 64 bit value on 64 bit Linux, as on every other OS except for Windows.
@BDatRivenhill Linux/Unix uses LP64 in which long is 64 bits
however, to make it more portable, use int64_t instead because there may well be some implementations with long long larger than long
"%" PRIu64 matches uint64_t and "%llu" matches unsigned long long. This answer has "%" PRIu64 with unsigned long long. This approach plants seeds for UB when unsigned long long is more than 64-bit. Best to avoid.
S
ST3

In Linux it is %llu and in Windows it is %I64u

Although I have found it doesn't work in Windows 2000, there seems to be a bug there!


with windows, (or at least, with the microsoft C compiler for windows) there's also %I64d, %I32u, and %I32d
What does it have to do with Windows 2000? The C library is the one that handles printf.
Just what I observed. I wrote an app which used this construct and it worked perfectly on WinXP but spat garbage on Win2k. Maybe it's something to do with a system call that the C library is making to the kernel, maybe it's something to do with Unicode, who knows. I remember having to work around it using _i64tot() or something like that.
The Win2k/Win9x issue is likely due to unsigned long long datatype being relatively new (at the time, with the C99 standard) but C compilers (including MinGW/GCC) utilizing the old Microsoft C runtime which only supported the C89 spec. I only have access to really old and reasonably recent Windows API docs. So it's difficult to say exactly when I64u support was dropped in. But it sounds like the XP-era.
S
Sandy

Compile it as x64 with VS2005:

%llu works well.


C
Community

Apparently no one has come up with a multi-platform* solution for over a decade since [the] year 2008, so I shall append mine 😛. Plz upvote. (Joking. I don’t care.)

Solution: lltoa()

How to use:

#include <stdlib.h> /* lltoa() */
// ...
char dummy[255];
printf("Over 4 bytes: %s\n", lltoa(5555555555, dummy, 10));
printf("Another one: %s\n", lltoa(15555555555, dummy, 10));

OP’s example:

#include <stdio.h>
#include <stdlib.h> /* lltoa() */

int main() {
    unsigned long long int num = 285212672; // fits in 29 bits
    char dummy[255];
    int normalInt = 5;
    printf("My number is %d bytes wide and its value is %s. "
        "A normal number is %d.\n", 
        sizeof(num), lltoa(num, dummy, 10), normalInt);
    return 0;
}

Unlike the %lld print format string, this one works for me under 32-bit GCC on Windows.

*) Well, almost multi-platform. In MSVC, you apparently need _ui64toa() instead of lltoa().


I don't have lltoa.
lltoa() is not a standard C library function. It does not work under 32-bit GCC on Windows when compiled unless non-standard extensions are allowed.
sizeof(num) returns a size_t. "%d" is not specifed to work with that. Better with "%zu".
c
chux - Reinstate Monica

How do you format an unsigned long long int using printf?

Since C99 use an "ll" (ell-ell) before the conversion specifiers o,u,x,X.

In addition to base 10 options in many answers, there are base 16 and base 8 options:

Choices include

unsigned long long num = 285212672;
printf("Base 10: %llu\n", num);
num += 0xFFF; // For more interesting hex/octal output.
printf("Base 16: %llX\n", num); // Use uppercase A-F
printf("Base 16: %llx\n", num); // Use lowercase a-f
printf("Base  8: %llo\n", num);
puts("or 0x,0X prefix");
printf("Base 16: %#llX %#llX\n", num, 0ull); // When non-zero, print leading 0X
printf("Base 16: %#llx %#llx\n", num, 0ull); // When non-zero, print leading 0x
printf("Base 16: 0x%llX\n", num); // My hex fave: lower case prefix, with A-F

Output

Base 10: 285212672
Base 16: 11000FFF
Base 16: 11000fff
Base  8: 2100007777
or 0x,0X prefix
Base 16: 0X11000FFF 0
Base 16: 0x11000fff 0
Base 16: 0x11000FFF

+l: "%llu" surprised me. I used "%ull" and got warning said I provided int.
@Rainning "%ull" prints an unsigned and then "ll".
B
Bernd Elkemann

In addition to what people wrote years ago:

you might get this error on gcc/mingw:

main.c:30:3: warning: unknown conversion type character 'l' in format [-Wformat=]

printf("%llu\n", k);

Then your version of mingw does not default to c99. Add this compiler flag: -std=c99.


s
sparkes

Non-standard things are always strange :)

for the long long portion under GNU it's L, ll or q

and under windows I believe it's ll only


v
vzczc

Well, one way is to compile it as x64 with VS2008

This runs as you would expect:

int normalInt = 5; 
unsigned long long int num=285212672;
printf(
    "My number is %d bytes wide and its value is %ul. 
    A normal number is %d \n", 
    sizeof(num), 
    num, 
    normalInt);

For 32 bit code, we need to use the correct __int64 format specifier %I64u. So it becomes.

int normalInt = 5; 
unsigned __int64 num=285212672;
printf(
    "My number is %d bytes wide and its value is %I64u. 
    A normal number is %d", 
    sizeof(num),
    num, normalInt);

This code works for both 32 and 64 bit VS compiler.


Try an actual 64-bit number instead of '285212672' and I do not believe the first example runs correctly, compiled to any target.
k
kungfooman

Hex:

printf("64bit: %llp", 0xffffffffffffffff);

Output:

64bit: FFFFFFFFFFFFFFFF

Very nice! i was wondering how i could get it in hex representation
But, almost all the C++ and C compilers give the warning: warning: use of 'll' length modifier with 'p' type character [-Wformat=]
this utterly broken answer has doubly-undefined behaviour and does not even begin to answer the question.
@AnttiHaapala You say this answer is utterly broken with doubly-undefined behaviour, can you elaborate or shall I just delete it? Or keep it as a good bad example?
UB1: all pointers are same size, sizeof(char *) == sizeof(long long *), so size modifier on %p is pointless. UB2: 0xff.fff is type int and format %p expects a pointer