public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Jim Wilson <wilson@tuliptree.org>
To: wilson@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c/7871: ICE on legal code, global register variables problems
Date: Thu, 01 May 2003 06:06:00 -0000	[thread overview]
Message-ID: <20030501060601.31751.qmail@sources.redhat.com> (raw)

The following reply was made to PR c/7871; it has been noted by GNATS.

From: Jim Wilson <wilson@tuliptree.org>
To: Richard Zidlicky <rz@linux-m68k.org>
Cc: Richard Henderson <rth@redhat.com>, gcc-gnats@gcc.gnu.org
Subject: Re: c/7871: ICE on legal code, global register variables problems
Date: 30 Apr 2003 22:57:05 -0400

 I am able to work on this again.
 
 On Tue, 2003-03-04 at 07:50, Richard Zidlicky wrote:
 > If you need a heavy duty testcase, I maintain a program that uses global 
 > registers extensively and works on many architectures
 >  http://linux-q40.sourceforge.net/uqlx/uqlx.tar.bz2  (332K)
 
 I tried looking at this.  It won't build cross without a bit of work,
 and the only native I can build at the moment is x86-linux which can't
 use global register variables.  So it is of no immediate help.
 
 I tried building it native on x86-linux anyways just to make sure I
 could build and run it.  I thought it wasn't working at first.  I had to
 add a 0 to the loops in bench1/bench2 before I was sure it was doing
 something.  Otherwise it took a fraction of a second to run.
 
 If you could send me a .i file and a pointer to where it was miscompiled
 that would be very helpful.  I can build a m68k-linux cross compiler and
 look at it.
 
 Otherwise, I could try compiling files with and without your gcc patch
 to see what difference it makes, but there might be too much noise for
 me to figure out what is going on.
 
 Jim
 
 


             reply	other threads:[~2003-05-01  6:06 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-01  6:06 Jim Wilson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-02 14:16 Richard Zidlicky
2003-05-02 12:26 Richard Zidlicky
2003-04-06 19:46 Jim Wilson
2003-04-02 20:56 Richard Zidlicky
2003-03-10  5:16 Jim Wilson
2003-02-28 16:46 Jim Wilson
2003-02-28  5:56 Richard Henderson
2003-02-28  3:26 Jim Wilson
2003-02-28  3:02 wilson
2002-12-14 12:56 Richard Zidlicky
2002-09-09 14:36 Richard Zidlicky

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=20030501060601.31751.qmail@sources.redhat.com \
    --to=wilson@tuliptree.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=wilson@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).