This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug rtl-optimization/20211] autoincrement generation is poor
- From: "amylaar at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 27 Apr 2005 13:37:50 -0000
- Subject: [Bug rtl-optimization/20211] autoincrement generation is poor
- References: <20050225161912.20211.amylaar@gcc.gnu.org>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Additional Comments From amylaar at gcc dot gnu dot org 2005-04-27 13:37 -------
(In reply to comment #4)
> There are both primary and secondary platforms among the AUTO_INC_DEC targets.
> So it is probably good to gain some wider test coverage about the compile-
> time/run-time impact of this. E.g. testing CSIBE on ARM, or SPEC on RS6000.
I have been trying to install Linux/GNU on an POwer Macintosh G3, but it
appears that this is not going to work. Inserting a Yellowdog 3.0.1
install 1 CD-rom into the drive freezes the machine solid. BootX versions
later than BootX_1.1.3 won't unpack. BootX 1.1.3 freezes the machine about
60% of the time rather than starting a kernel. rocklinux gets a CRC error
on the ramdisk and then can't find init. ubuntu manages to continue after
ramdisk unpacking errors, and even goes as far as partitioning if you
restrict the partitions to 13 GB or less, but then it say it can't find the
CD_ROM it just has read lots of files from.
So, since there is no native platform I can test, would you like me to
benchmark cross-compiling a suitable package? IIRC powerpc-eabisim is
a possible cross target. Would CSIBE cross-compile time measurements
fit your requirements?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20211