On Dec 11, 2007 7:48 PM, Nuno Lucas <[EMAIL PROTECTED]> wrote:
>
>
> http://gcc.gnu.org/onlinedocs/gcc/Variable-Attributes.html#Variable-Attributes
>
> Don't know how I forgot to include that option, sorry. Probably too
> focused on portable code.
>
>
> Regards,
> ~Nuno Lucas
>
Hi,
I presumed it'
Hi,
In an earlier message, we arrived at the conclusion that IcmpSendEcho
and some of its friends are in a static library which we don't have; or
in the iphlpapi DLL which we do.
I've since tried to get the ping application that's on our website to
compile with my poor man's version of MFC. It do
On Dec 11, 2007 6:38 PM, Ivan Vucica <[EMAIL PROTECTED]> wrote:
> On Dec 11, 2007 4:28 PM, Nuno Lucas <[EMAIL PROTECTED]> wrote:
> >
> >
> > Allocated memory should always come aligned. That's not the problem.
> > I would guess the problem is the array base address in the stack (on
> > IA32 the sta
On Dec 11, 2007 4:28 PM, Nuno Lucas <[EMAIL PROTECTED]> wrote:
>
>
> Allocated memory should always come aligned. That's not the problem.
> I would guess the problem is the array base address in the stack (on
> IA32 the stack is always aligned by 32 bits, but that can not be true
> on other platfor
Forgot to reply to the list, my to original Carnsten response below:
On Dec 10, 2007 5:32 PM, Carsten Sørensen <[EMAIL PROTECTED]> wrote:
> On Dec 10, 2007 2:28 PM, Ivan Vucica <[EMAIL PROTECTED]> wrote:
> > Casting a char* into uint32_t*, unsigned int* or int* and then using it
> > with operator
On Tue, 2007-12-11 at 00:29 +, Pedro Alves wrote:
> * gcc : fix alignment of 64-bit objects to be inline with MSFT's ABI.
> This means 0.51 generated code is NOT binary compatible
> with code generated with 0.50.
Oops. Added it to the notes for this release on our download pa
