public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Zidlicky <Richard.Zidlicky@stud.informatik.uni-erlangen.de>
To: Peter Barada <pbarada@mail.wm.sps.mot.com>
Cc: gcc@gcc.gnu.org
Subject: Re: ICE building glibc-2.2.5 using m68k-linux gcc-3.1
Date: Thu, 25 Jul 2002 13:32:00 -0000	[thread overview]
Message-ID: <20020725172702.B1938@linux-m68k.org> (raw)
In-Reply-To: <200207222009.g6MK9xI27711@hyper.wm.sps.mot.com>; from pbarada@mail.wm.sps.mot.com on Mon, Jul 22, 2002 at 04:09:59PM -0400

On Mon, Jul 22, 2002 at 04:09:59PM -0400, Peter Barada wrote:
> 
':
> ../wcsmbs/wchar.h:520: Internal compiler error in simplify_unary_operation, at simplify-rtx.c:532
> Please submit a full bug report,
> with preprocessed source if appropriate.
> See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.

not much help I am afraid, but I have had a few similar problems 
with native m68k-linux on 3.1. I managed to reduce one testcase 
to something really small, perhaps you can see something from it.

Btw it does no longer cause an ICE for 3.1.1 but the program from
which it is taken still doesn't work correctly.

Richard

#### compile with -O0 to trigger ICE ####

extern void (**table)(void);

typedef unsigned short uw16;
typedef unsigned int gshort;

register uw16 *pc asm("%a4");
register gshort code asm("%d6");


void QMExecuteLoop(uw16 *oldPC)
{
            table[code=(*(uw16*)(pc++))]();
}




  reply	other threads:[~2002-07-25 18:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-22 17:22 Peter Barada
2002-07-25 13:32 ` Richard Zidlicky [this message]
2002-07-25 15:45   ` Peter Barada
2002-07-26  8:50     ` Richard Henderson
2002-07-26 15:52       ` Richard Zidlicky
2002-07-27 15:18       ` 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=20020725172702.B1938@linux-m68k.org \
    --to=richard.zidlicky@stud.informatik.uni-erlangen.de \
    --cc=gcc@gcc.gnu.org \
    --cc=pbarada@mail.wm.sps.mot.com \
    /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).