public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: kisch@mindless.com
To: gcc-gnats@gcc.gnu.org
Cc: kisch@sesamstrasse.dyndns.tv
Subject: target/8528: Internal compiler error in extract_insn, at recog.c:2148
Date: Mon, 11 Nov 2002 09:16:00 -0000	[thread overview]
Message-ID: <20021111170622.3112.qmail@sources.redhat.com> (raw)


>Number:         8528
>Category:       target
>Synopsis:       Internal compiler error in extract_insn, at recog.c:2148
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          ice-on-legal-code
>Submitter-Id:   net
>Arrival-Date:   Mon Nov 11 09:16:03 PST 2002
>Closed-Date:
>Last-Modified:
>Originator:     Bernd Kischnick
>Release:        gcc-3.2 20020903
>Organization:
>Environment:
powerpc-yellowdog-linux, glibc 2.3.1, ppc 603e cpu.
>Description:
gcc emits "internal compiler error" on the attached code fragment, when -O is -O2 or higher.
No error and correct code with -O and -Os or without -O.
No error with the same code with i386 target.

The code is already stripped down to the minimum I've found necessary to trigger the bug (from 17000 lines preprocessed output to start with).

screen-E.c: In function `meta_screen_calc_workspace_layout':
screen-E.c:25: unrecognizable insn:
(insn 106 55 107 (parallel[
            (set (reg/v:SI 3 r3 [119])
                (plus:SI (gt:SI (reg:SI 0 r0 [140])
                        (const_int 0 [0x0]))
                    (reg:SI 9 r9 [133])))
            (clobber (reg:SI 11 r11))
        ] ) -1 (nil)
    (nil))
>How-To-Repeat:
gcc -O2 -c screen-E.c or gcc -O2 -S screen-E.c
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: application/octet-stream; name="screen-E.c"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="screen-E.c"

c3RydWN0IF9NZXRhU2NyZWVuCnsKICBpbnQgcm93c19vZl93b3Jrc3BhY2VzOwogIGludCBjb2x1
bW5zX29mX3dvcmtzcGFjZXM7Cn07Cgp2b2lkCm1ldGFfc2NyZWVuX2NhbGNfd29ya3NwYWNlX2xh
eW91dCAoc3RydWN0IF9NZXRhU2NyZWVuICpzY3JlZW4sCiAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgaW50IG51bV93b3Jrc3BhY2VzLAogICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgIGludCAqcikKewogIGludCBjb2xzLCByb3dzOwogIHJvd3MgPSBzY3JlZW4tPnJv
d3Nfb2Zfd29ya3NwYWNlczsKICBjb2xzID0gc2NyZWVuLT5jb2x1bW5zX29mX3dvcmtzcGFjZXM7
CiAgaWYgKHJvd3MgPD0gMCAmJiBjb2xzIDw9IDApCiAgICBjb2xzID0gbnVtX3dvcmtzcGFjZXM7
CgogIGlmIChyb3dzIDw9IDApCiAgICByb3dzID0gbnVtX3dvcmtzcGFjZXMgLyBjb2xzICsgKChu
dW1fd29ya3NwYWNlcyAlIGNvbHMpID4gMCA/IDEgOiAwKTsKCiAgaWYgKHJvd3MgPCAxKQogICAg
cm93cyA9IDE7CgogICpyID0gcm93czsKfQo=


                 reply	other threads:[~2002-11-11 17:16 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20021111170622.3112.qmail@sources.redhat.com \
    --to=kisch@mindless.com \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=kisch@sesamstrasse.dyndns.tv \
    /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).