public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "amylaar at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/20211] autoincrement generation is poor
Date: Wed, 27 Apr 2005 13:38:00 -0000	[thread overview]
Message-ID: <20050427133750.13264.qmail@sourceware.org> (raw)
In-Reply-To: <20050225161912.20211.amylaar@gcc.gnu.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


  parent reply	other threads:[~2005-04-27 13:38 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-25 22:08 [Bug rtl-optimization/20211] New: " amylaar at gcc dot gnu dot org
2005-02-26  1:13 ` [Bug rtl-optimization/20211] " pinskia at gcc dot gnu dot org
2005-02-26  1:24 ` giovannibajo at libero dot it
2005-02-27  4:49 ` hp at gcc dot gnu dot org
2005-02-28 20:49 ` joern dot rennecke at st dot com
2005-03-15  2:12 ` giovannibajo at libero dot it
2005-03-15 18:08 ` amylaar at gcc dot gnu dot org
2005-03-17 16:38 ` amylaar at gcc dot gnu dot org
2005-04-12 18:06 ` amylaar at gcc dot gnu dot org
2005-04-27 13:38 ` amylaar at gcc dot gnu dot org [this message]
2005-04-27 13:42 ` pinskia at gcc dot gnu dot org
2005-04-28 13:37 ` amylaar at gcc dot gnu dot org
2005-04-28 13:43 ` pinskia at gcc dot gnu dot org
2005-04-28 19:21 ` amylaar at gcc dot gnu dot org
2005-05-12 19:00 ` pinskia at gcc dot gnu dot org
2005-05-12 19:31 ` joern dot rennecke at st dot com
2005-05-17 19:20 ` amylaar at gcc dot gnu dot org
2005-09-19 16:52 ` cvs-commit at gcc dot gnu dot org
2005-09-19 16:54 ` cvs-commit at gcc dot gnu dot org
2005-09-19 17:30 ` amylaar at gcc dot gnu dot org
     [not found] <bug-20211-5394@http.gcc.gnu.org/bugzilla/>
2005-11-02 21:50 ` amylaar at gcc dot gnu dot org
2006-11-15 20:11 ` amylaar at gcc dot gnu dot org
2006-11-30 20:05 ` amylaar at gcc dot gnu dot org
2006-12-17 14:47 ` steven at gcc dot gnu dot org
2007-06-18  2:03 ` pinskia at gcc dot gnu dot org
2007-09-17 20:06 ` rguenth at gcc dot gnu dot org
2008-05-23 23:14 ` hp at gcc dot gnu dot org
2010-02-22  6:05 ` amylaar at gcc dot gnu dot org
     [not found] <bug-20211-4@http.gcc.gnu.org/bugzilla/>
2013-12-24 22:55 ` steven at gcc dot gnu.org
2015-09-21  8:15 ` olegendo at gcc dot gnu.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20050427133750.13264.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).