Tail-call reference (was: CPUTYPE warning)

2001-08-07 Thread Joseph Koshy
tl == Terry Lambert wrote: tl FWIW: tail-call optimization is when I have a function tl that, as it's last thing (perhaps after reordering by tl the compiler, as well) calls another function, such tl that the return value of the other function is its tl return value. See also: Debunking

Re: CPUTYPE warning

2001-06-23 Thread Karsten W. Rohrbach
Terry Lambert([EMAIL PROTECTED])@2001.06.22 20:38:45 +: Karsten W. Rohrbach wrote: btw, regarding gcc's -O2 optimization breakage on -2.95.x and improved instrumentation of the new compiler kit, is there someone working on getting gcc-3.0 into -current? ...yes *sigh* i know,

Re: CPUTYPE warning

2001-06-23 Thread Terry Lambert
Karsten W. Rohrbach wrote: refer to http://www.gnu.org/software/gcc/gcc-3.0/features.html --- General Optimizer Improvements: - Basic block reordering pass. - New if-conversion pass with support for conditional (predicated) execution. - New tail call and sibling call

Re: CPUTYPE warning

2001-06-22 Thread Karsten W. Rohrbach
btw, regarding gcc's -O2 optimization breakage on -2.95.x and improved instrumentation of the new compiler kit, is there someone working on getting gcc-3.0 into -current? ...yes *sigh* i know, 3.0 is _not_ stable, neither is -current ;-) /k Dag-Erling Smorgrav([EMAIL PROTECTED])@2001.06.21

Re: CPUTYPE warning

2001-06-22 Thread David O'Brien
On Fri, Jun 22, 2001 at 07:22:32PM +0200, Karsten W. Rohrbach wrote: btw, regarding gcc's -O2 optimization breakage on -2.95.x and improved instrumentation of the new compiler kit, is there someone working on getting gcc-3.0 into -current? It will come with time. To Unsubscribe: send mail to

Re: CPUTYPE warning

2001-06-22 Thread Terry Lambert
Karsten W. Rohrbach wrote: btw, regarding gcc's -O2 optimization breakage on -2.95.x and improved instrumentation of the new compiler kit, is there someone working on getting gcc-3.0 into -current? ...yes *sigh* i know, 3.0 is _not_ stable, neither is -current ;-) Does it do tail-call

Re: CPUTYPE warning

2001-06-21 Thread Dag-Erling Smorgrav
Dag-Erling Smorgrav [EMAIL PROTECTED] writes: June 5th doesn't work (dumps core when it gets to crt1.c). Today's won't build anything at all. I think I've found the problem - what doesn't work is: - building crt1.c with -fno-builtin - building anything with gcc compiled with -fno-builtin

Re: -fno-builtin warning (was: CPUTYPE warning)

2001-06-21 Thread Dag-Erling Smorgrav
Dag-Erling Smorgrav [EMAIL PROTECTED] writes: I think I've found the problem - what doesn't work is: - building crt1.c with -fno-builtin - building anything with gcc compiled with -fno-builtin Ah, no, I understand now: crt1 is the first item to be built in the libraries stage of

CPUTYPE warning

2001-06-20 Thread Dag-Erling Smorgrav
In recent versions of -CURRENT, gcc built with CPUTYPE set to k6-2 will dump core when compiling specific source files (crt1.c at least), and in the very latest -CURRENT, when compiling anything at all. So far, gcc built with CPUTYPE set to i586 seem to work fine. DES -- Dag-Erling Smorgrav -

Re: CPUTYPE warning

2001-06-20 Thread David O'Brien
On Thu, Jun 21, 2001 at 12:37:00AM +0200, Dag-Erling Smorgrav wrote: In recent versions of -CURRENT, gcc built with CPUTYPE set to k6-2 will dump core when compiling specific source files (crt1.c at least), and in the very latest -CURRENT, when compiling anything at all. So far, gcc built

Re: CPUTYPE warning

2001-06-20 Thread Dag-Erling Smorgrav
David O'Brien [EMAIL PROTECTED] writes: On Thu, Jun 21, 2001 at 12:37:00AM +0200, Dag-Erling Smorgrav wrote: In recent versions of -CURRENT, gcc built with CPUTYPE set to k6-2 will dump core when compiling specific source files (crt1.c at least), and in the very latest -CURRENT, when