Hi Stefan!

> The problems are in the gcc implementation
> 
> - the lra implementation is buggy
> - the compare elimination can't handle parallel's containing a compare
> - df-core considers parallel's containing a compare also as a USE
> - some optimizations/mechanisms do only work if HAVE_CC0 is defined
> - way more ...

Are you talking about GCC in general or about the m68k backend?

In any case, I would appreciate it if you could file bug reports where you
are seeing issues and put me in the CC of these bug reports.

> And the current implementation is IMHO unusable for lra since it did not
> introduce a CC register to track clobbering. So it's a dead end.

I assume you are talking about Bernd's m68k cc0 transition?

We are planning to have another Bountysource campaign for the m68k
backend to fund the LRA transition and - if necessary - fix other bugs
in the backend, so constructive feedback is necessary and absolutely
welcome.

On every bug that is documented in GCC Bugzilla, we can put a bounty if
necessary.

> I can live with the fact that my patch was refuted since I simply use
> my *working* fork, where I fixed the issues mentioned above.

I would prefer getting all bugs in GCC reported to the GCC Bugzilla so that
they can be resolved in GCC itself. We don't gain anything if important bug
fixes are found in forks only.

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-    GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Reply via email to