PLEASE REPLY TO [EMAIL PROTECTED] ONLY, *NOT* [EMAIL PROTECTED]
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12717
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
Processing commands for [EMAIL PROTECTED]:
> retitle 217541 ffi.h's ffi_type_[us]long bogus on x86
Bug#217541: fficonfig.h bogus on x86
Changed Bug title.
> tags 217541 + patch
Bug#217541: ffi.h's ffi_type_[us]long bogus on x86
There were no tags set.
Tags added: patch
> thanks
Stopping processi
Andreas Rottmann <[EMAIL PROTECTED]> writes:
> As you can easily see, the two pointers refer to the same object, which
> means fficonfig.h #defines ffi_type_ulong to ffi_type_uint64, which is
> plain wrong on a 32bit platform.
>
s/fficonfig.h/ffi.h/
The way ffi.h #defines the ffi_type_XX equival
Package: libffi2-dev
Version: 1:3.3.2-1
Severity: important
Running this little test program on my Athlon (no, not an Athlon64 ;-)):
#include
#include
int main ()
{
printf ("&ffi_type_ulong: %p &ffi_type_uint64: %p\n",
&ffi_type_ulong, &ffi_type_uint64);
}
results in:
&ffi_type_
PLEASE REPLY TO [EMAIL PROTECTED] ONLY, *NOT* [EMAIL PROTECTED]
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12765
ebotcazou at gcc dot gnu dot org changed:
What|Removed |Added
Processing commands for [EMAIL PROTECTED]:
> severity 194345 important
Bug#194345: g++ 3.3 needs to much memory / gets killed by OOM-killer
Bug#194513: Internal error: unbalanced parenthesis in operand 1
Severity set to `important'.
> thanks
Stopping processing here.
Please contact me if you nee
severity 194345 important
thanks
this case is not related to original report. reverting the severity of
the report to the old severity.
The new bug has been forwarded to http://gcc.gnu.org/PR12765
the severity of this report is not RC, as there is a workaround using
g++-3.2.
Eduard Bloch writes:
7 matches
Mail list logo