public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: "Billinghurst, David \(CRTS\)" <David.Billinghurst@riotinto.com> To: billingd@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: fortran/3393: ICE in extract_insn, at recog.c:2173 Date: Tue, 22 Jan 2002 15:46:00 -0000 [thread overview] Message-ID: <20020122234603.18572.qmail@sources.redhat.com> (raw) The following reply was made to PR fortran/3393; it has been noted by GNATS. From: "Billinghurst, David (CRTS)" <David.Billinghurst@riotinto.com> To: <gcc-gnats@gcc.gnu.org> Cc: Subject: Re: fortran/3393: ICE in extract_insn, at recog.c:2173 Date: Wed, 23 Jan 2002 07:39:12 +0800 For the record ... -----Original Message----- From: Reichelt [mailto:reichelt@igpm.rwth-aachen.de] Sent: Wednesday, 23 January 2002 12:17=20 To: toon@moene.indiv.nluug.nl; gcc@gcc.gnu.org Subject: Re: Plan for bug-fixing g77-3.1. Hello again, PR 3393 can be boiled down to the following lines of code: PROGRAM LABUG2 INTEGER I, J, M REAL A(5,2) M =3D 1 DO J =3D 1, 2 DO I =3D 1, M CALL F1( A(I,J) ) END DO END DO CALL F2(M) END I get the following error message when compiling with "g77 -O2 = -mabi=3D64" on mips-sgi-irix6.5: labug2.f:11: unrecognizable insn: (insn 203 84 144 (set (reg:DI 114) (plus:DI (reg:DI 114) (sign_extend:DI (const_int 20 [0x14])))) -1 (nil) (nil)) labug2.f:11: Internal compiler error in extract_insn, at recog.c:2129 Again, there's a two-dimensional array involded, so that PR 3393 is probably related to PR 3392. Greetings, Volker Reichelt http://gcc.gnu.org/ml/gcc/2002-01/msg01379.html http://gcc.gnu.org/ml/gcc/2002-01/msg01389.html
next reply other threads:[~2002-01-22 23:46 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-01-22 15:46 Billinghurst, David (CRTS) [this message] -- strict thread matches above, loose matches on Subject: below -- 2001-06-24 20:56 David.Billinghurst
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=20020122234603.18572.qmail@sources.redhat.com \ --to=david.billinghurst@riotinto.com \ --cc=billingd@gcc.gnu.org \ --cc=gcc-prs@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: linkBe 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).