Re: [E-devel] Re: libast from Eterm CVS fails to build with gcc4 on x86_64

2005-06-02 Thread John Ellson
Michael Jennings wrote: Why not just define STRICT_ISO_C99? I created it specifically for that purpose. Sure, but then there should be a configure test for the cases that need it. john --- This SF.Net email is sponsored by Yahoo. Intr

Re: [E-devel] Re: libast from Eterm CVS fails to build with gcc4 on x86_64

2005-06-02 Thread Michael Jennings
On Thursday, 02 June 2005, at 13:56:28 (-0400), John Ellson wrote: > Sure, but then there should be a configure test for the cases that need it. Patches welcome. :) Michael -- Michael Jennings (a.k.a. KainX) http://www.kainx.org/ <[EMAIL PROTECTED]> n + 1, Inc., http://www.nplus1.net/

Re: [E-devel] Re: libast from Eterm CVS fails to build with gcc4 on x86_64

2005-06-02 Thread John Ellson
Michael Jennings wrote: On Thursday, 02 June 2005, at 13:56:28 (-0400), John Ellson wrote: Sure, but then there should be a configure test for the cases that need it. Patches welcome. :) Michael RCS file: /cvsroot/enlightenment/eterm/libast/configure.in,v retrieving revision 1

Re: [E-devel] Re: libast from Eterm CVS fails to build with gcc4 on x86_64

2005-06-02 Thread Mike Frysinger
On Thursday 02 June 2005 01:01 pm, Michael Jennings wrote: > On Thursday, 02 June 2005, at 10:28:15 (-0400), > > John Ellson wrote: > > The problem is that the xor trick isn't working for swapping pointers. > > One possible work around is to use > > the more straightfoward SWAP code: > > > > RCS fi

Re: [E-devel] Re: libast from Eterm CVS fails to build with gcc4 on x86_64

2005-06-06 Thread Michael Jennings
On Thursday, 02 June 2005, at 15:56:40 (-0400), John Ellson wrote: > RCS file: /cvsroot/enlightenment/eterm/libast/configure.in,v > retrieving revision 1.24 Got it, thanks. On Thursday, 02 June 2005, at 16:02:00 (-0400), Mike Frysinger wrote: > would an ifdef like: > #if STRICT_ISO_C99 || __G

Re: [E-devel] Re: libast from Eterm CVS fails to build with gcc4 on x86_64

2005-06-06 Thread Tres Melton
On Mon, 2005-06-06 at 13:26 -0400, Michael Jennings wrote: > > #define BINSWAP(a, b) \ > >(((long) (a)) ^= ((long) (b)) ^= ((long) (a)) ^= ((long) (b))) > > > > int main( void ) > > { > > long a = 3; > > long b = 8; > > > > asm( "noop;noop;noop" ); > > BINSWAP(a,b); > > asm( "noop;

Re: [E-devel] Re: libast from Eterm CVS fails to build with gcc4 on x86_64

2005-06-06 Thread Mike Frysinger
On Monday 06 June 2005 07:09 pm, Tres Melton wrote: > The "nop" is just an easy way to place markers in the code so you > can find the interesting parts quickly. In reality it costs one clock > cycle for each "nop". i use asm label tricks: $ cat test.c int main(int argc, char *argv[]) { i

Re: [E-devel] Re: libast from Eterm CVS fails to build with gcc4 on x86_64

2005-06-06 Thread Tres Melton
On Mon, 2005-06-06 at 19:26 -0400, Mike Frysinger wrote: > i use asm label tricks: > $ cat test.c > int main(int argc, char *argv[]) > { > int a; > asm("startit:"); > a = 10; > asm("stopit:"); > return 0; > } > > $ gcc -c test.c && objdump -d test.o > test.o

Re: [E-devel] Re: libast from Eterm CVS fails to build with gcc4 on x86_64

2005-06-10 Thread Tres Melton
On Wed, 2005-06-08 at 19:20 -0700, Stephen Horner wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 18:00, Mon 06 Jun 05, Tres Melton wrote: > > Well, the pages I was reading used the nop trick but it looks like a > > better solution has been presented. I almost forgot that integers