Hi there,
>
>We have a function that can be used to initialize a pdf_i64_t with a
>pdf_i32_t:
>
>void
>pdf_i64_assign_quick (pdf_i64_t *bignum,
> const pdf_i32_t value,
> pdf_status_t *p_status);
>
>But, what if I am in a
Hi Aleks.
We have a function that can be used to initialize a pdf_i64_t with a
pdf_i32_t:
void
pdf_i64_assign_quick (pdf_i64_t *bignum,
const pdf_i32_t value,
pdf_status_t *p_status);
But, what if I am in a OS with built-in 64-
Solved, the issue as described here:
http://gcc.gnu.org/onlinedocs/gcc/Long-Long.html#Long-Long
is that in C89 we have to use 'long long' literals (LL) for 64-bit constants,
since it's a GCC extension (C99 supports it but C89 not).
Here I attach a patch to suppress those warning
Solved, the issue as described here:
http://gcc.gnu.org/onlinedocs/gcc/Long-Long.html#Long-Long
is that in C89 we have to use 'long long' literals (LL) for 64-bit constants,
since it's a GCC extension (C99 supports it but C89 not).
Here I attach a patch to suppress those warnings,
##
# Bazaar
> base/types/pdf-i64-new.c: In function 'pdf_i64_new_001':
> base/types/pdf-i64-new.c:53: warning: integer constant is too large for
'long' type
> base/types/pdf-i64-assign.c: In function 'pdf_i64_assign_001':
> base/types/pdf-i64-assign.c:57: warning: integer constant is too large fo
> base/types/pdf-i64-new.c: In function 'pdf_i64_new_001':
> base/types/pdf-i64-new.c:53: warning: integer constant is too large for
'long' type
>
Hi jemarch, I have a similar list of warnings that I have been getting in the
last 2 months or so, I reported it and IIRC no one r
> Date: Tue, 25 Nov 2008 10:45:32 +0100
> From: Aleksander Morgado <[EMAIL PROTECTED]>
>
> > > After applying your patch I am getting lots of compilation warnings
> > > like:
> > >
> > > base/types/pdf-i64-new.c: In function 'pdf_i64_new_001':
> > > base/types/pdf-i64-new.c:53: warni
> > After applying your patch I am getting lots of compilation warnings
> > like:
> >
> > base/types/pdf-i64-new.c: In function 'pdf_i64_new_001':
> > base/types/pdf-i64-new.c:53: warning: integer constant is too large for
> 'long' type
> >
>
> Hi jemarch, I have a similar list of warnin
> Date: Mon, 24 Nov 2008 20:07:41 +0100
> From: [EMAIL PROTECTED]
>
> After applying your patch I am getting lots of compilation warnings
> like:
>
> base/types/pdf-i64-new.c: In function 'pdf_i64_new_001':
> base/types/pdf-i64-new.c:53: warning: integer constant is too large for
> 'lo
Hi Aleks.
>>#if defined(HAVE_INT_64) || defined(int64_t)
>> Use the system type.
>>#endif
>
> Yep, I'll send you updated patch.
After applying your patch I am getting lots of compilation warnings
like:
base/types/pdf-i64-new.c: In function 'pdf_i64_new_001':
base/ty
gnulib will only include the stdint.h if not available in the
system, orif not correctly implemented in a given system. In my
Ubuntu/Debian themodule is not needed, as that file is already in
the system, so nostdint.h will be created after runnning configure.
The problem here
gnulib will only include the stdint.h if not available in the system, or
if not correctly implemented in a given system. In my Ubuntu/Debian the
module is not needed, as that file is already in the system, so no
stdint.h will be created after runnning configure.
The problem he
Hi Aleks.
gnulib will only include the stdint.h if not available in the system, or
if not correctly implemented in a given system. In my Ubuntu/Debian the
module is not needed, as that file is already in the system, so no
stdint.h will be created after runnning configure.
The p
>I found that the "#if defined(int64_t)" is not working (the previous
>"#ifdef int64_t" didn't work either... my fault) in pdf-types.h. This
>means we have always been compiling our own 64-bit support.
>
>Attached is a patch to check for int64_t at configure time
>I found that the "#if defined(int64_t)" is not working (the previous
>"#ifdef int64_t" didn't work either... my fault) in pdf-types.h. This
>means we have always been compiling our own 64-bit support.
>
>Attached is a patch to check for int64_t at configure time,
>I found that the "#if defined(int64_t)" is not working (the previous
>"#ifdef int64_t" didn't work either... my fault) in pdf-types.h. This
>means we have always been compiling our own 64-bit support.
>
>Attached is a patch to check for int64_t at configure time, which seems
>
Hello Aleks.
I found that the "#if defined(int64_t)" is not working (the previous
"#ifdef int64_t" didn't work either... my fault) in pdf-types.h. This
means we have always been compiling our own 64-bit support.
Attached is a patch to check for int64_t at configure time, which see
And BTW, didn't we talk about adding an option to configure in order to
force the use of our built-in 64-bit support?
I just commited a patch in the trunk adding a new configure option for
that purpose: --enable-bignum-forcing
Hi
I found that the "#if defined(int64_t)" is not working
But, I don't think it's clear from the API document point of view, as it
seems that only 32-bit integers are allowed. How can we explain this in
the document? Just with a note saying... "hey, you can also use a 64-bit
value in this function instead of a pdf_i32_t"... or what?
I w
Hi Aleks.
We have a function that can be used to initialize a pdf_i64_t with a
pdf_i32_t:
void
pdf_i64_assign_quick (pdf_i64_t *bignum,
const pdf_i32_t value,
pdf_status_t *p_status);
But, what if I am in a OS with built-in 64-
Hi,
We have a function that can be used to initialize a pdf_i64_t with a
pdf_i32_t:
void
pdf_i64_assign_quick (pdf_i64_t *bignum,
const pdf_i32_t value,
pdf_status_t *p_status);
But, what if I am in a OS with built-in 64-bit support (like I guess we
21 matches
Mail list logo
