egcs-ss-970814 on m68k-next-nextstep3

egcs-ss-970814 on m68k-next-nextstep3

[Toon Moene]

Results for `make bootstrap CFLAGS="-g -O3 -fno-regmove" LANGUAGES=c'.

A regression with respect to the not-so-public egcs-ss-970813:

- I had to compile config/nextstep.c by hand.

- Furthermore, convert.c is compiled twice.

Both are shortcomings I noted with a recent gcc snapshot too.

The hang at enquire:

Apparently, it happens in routine F_check, because the last routine  
in enquire.s is:

.globl _fSelf
_fSelf:

When stopped with Control-C, I get:

Reading in symbols for real.c...done.
etoasc (x=0x6, string=0x3fff4f6 "", ndigs=20) at real.c:1887
1887          bits <<= 1;
(gdb) bt
Reading in symbols for config/m68k/m68k.c...done.
Reading in symbols for final.c...done.
Reading in symbols for toplev.c...done.
Reading in symbols for c-decl.c...done.
Reading in symbols for c-parse.c...done.
#0  etoasc (x=0x6, string=0x3fff4f6 "", ndigs=20) at real.c:1887
#1  0x74c2a in ereal_to_decimal (x=void, s=0x3fff4f6 "") at real.c:1210
#2  0xec338 in print_operand (file=0x3fff4f6, op=0x443214,  
letter=67106038) at config/m68k/m68k.c:2734
#3  0xcee26 in output_operand (x=0x443214, code=102) at final.c:2713
#4  0xceb00 in output_asm_insn (template=0x3fff452 "",  
operands=0x1356e0) at final.c:2637
#5  0xce3d4 in final_scan_insn (insn=0x443244, file=0x1,  
optimize=0, prescan=110, nopeepholes=0) at final.c:2168
#6  0xcd5d8 in final (first=0x1356e0, file=0x1, optimize=110,  
prescan=0) at final.c:1322
#7  0x226cc in rest_of_compilation (decl=void) at toplev.c:3592
#8  0xfc46 in finish_function (nested=0) at c-decl.c:7012
#9  0x2d44 in yyparse () at c-parse.y:352
#10 0x1f2c4 in compile_file (name=0x3fffcde "enquire.i") at toplev.c:2470
#11 0x233c2 in main (argc=12, argv=0x124d2c, envp=0x3fffc88) at  
toplev.c:4309

but

(gdb) whatis x
type = unsigned short *

the value 0x6 seems a bit odd for a pointer.

HTH,
Toon.

Re: alias analysis to use induction var information?

[Jeffrey A Law]

  In message <199708171644.MAA08103@kikashi.lcs.mit.edu>you write:
  > Any plans to modify the alias analysis code to use induction variable
  > information computed in the loop optimization pass to aid dependence
  > testing?
Not that I'm aware of.  However, I do have in the back of my mind some
work in loop that could take advantage of the new alias code.  Things
like caching of memory values in registers around a loop -- which 
would benefit from the alias code.

jeff

Re: GCC Projects?

[Jeffrey A Law]

  In message <k2hgcovl4a.fsf@zero.aec.at>you write:
  > Hi,
  > 
  > I see that there are two main unfinished projects in the egcs
  > source tree: pre-compiled include files and bytecode generation.
  > Is anyone working on one of these?
Nobody is working on these as far as I know.  Lots of other stuff
is probably more important -- cpplib, lots of optimization work,
fold in ada & pascal front ends, packaging & release issues, docs,
etc etc.

jeff

Re: alias analysis to use induction var information?

[John Carr]

> Any plans to modify the alias analysis code to use induction variable
> information computed in the loop optimization pass to aid dependence
> testing?

I don't plan to.  I don't understand the loop code very well.  My code
does improve dependency checking between iterations of some unrolled
loops: the new code sometimes uses a single pseudo-register where the
old code would use several.

alias analysis to use induction var information?

[Cotton Seed]

Any plans to modify the alias analysis code to use induction variable
information computed in the loop optimization pass to aid dependence
testing?

        - Cotton