public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: george@mpimf-heidelberg.mpg.de
To: gcc-gnats@gcc.gnu.org
Subject: optimization/6698: gcc crashes in reload_cse_simplify_operands (M68HC12)
Date: Fri, 17 May 2002 09:16:00 -0000	[thread overview]
Message-ID: <20020517161312.16543.qmail@sources.redhat.com> (raw)


>Number:         6698
>Category:       optimization
>Synopsis:       gcc crashes in reload_cse_simplify_operands (M68HC12)
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          ice-on-legal-code
>Submitter-Id:   net
>Arrival-Date:   Fri May 17 09:16:01 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     george@mpimf-heidelberg.mpg.de
>Release:        gcc version 3.1
>Organization:
>Environment:

>Description:
m68hc12-elf-gcc -g -Os -mshort -fomit-frame-pointer -mauto-incdec -msoft-reg-count=0 -Wl,-defsym,ports=0x0,-u,-mm68hc12elfb -o scanner.elf scanner.c
scanner.c: In function `main':
scanner.c:42: insn does not satisfy its constraints:
(insn 67 65 68 (set (mem/v:QI (const_int 174 [0xae]) [0 S1 A8])
        (ior:QI (mem/v:QI (const_int 174 [0xae]) [0 S1 A8])
            (const_int 2 [0x2]))) 83 {*iorqi3_const} (insn_list 60 (nil))
    (nil))
scanner.c:42: Internal compiler error in reload_cse_simplify_operands, at reload1.c:8368
>How-To-Repeat:
See description.

Compilation works if the delay() is placed directly into the while(1) loop.
>Fix:

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

LyogIHNjYW5uZXIuYyAqLwovKiAgSi4gVHJpdHRoYXJkdCwgTVBJTUYvQk1PICovCi8qICBWZXJz
aW9uIDEuMCAtIDI4LjAyLjIwMDIgKi8KCi8qICBUZXN0cHJvZ3JhbW0gZnVlciBkaWUgTEVEcyBk
ZXIgU2Nhbm5lci1Cb3ggKi8KCiNkZWZpbmUgQ09QQ1RMICoodm9sYXRpbGUgdW5zaWduZWQgY2hh
ciAqKSgweDE2KQoKI2RlZmluZSBJT19CQVNFIDAKI2RlZmluZSBQT1JUVCAqKCh2b2xhdGlsZSB1
bnNpZ25lZCBjaGFyICopKElPX0JBU0UgKyAweEFFKSkKI2RlZmluZSBERFJUICooKHZvbGF0aWxl
IHVuc2lnbmVkIGNoYXIgKikoSU9fQkFTRSArIDB4QUYpKQoKI2RlZmluZSBsZWRfcmVkIDB4MDIK
I2RlZmluZSBsZWRfcmVkX3BvcnQgUE9SVFQKI2RlZmluZSBsZWRfcmVkX2RkciBERFJUCiNkZWZp
bmUgbGVkX2dyZWVuIDB4MDgKI2RlZmluZSBsZWRfZ3JlZW5fcG9ydCBQT1JUVAojZGVmaW5lIGxl
ZF9ncmVlbl9kZHIgRERSVAoKdm9pZCBkZWxheSgpOwoKaW50IG1haW4oKSAKeyAKICBsZWRfcmVk
X3BvcnQgPSBsZWRfcmVkX3BvcnQgfCBsZWRfcmVkOwogIGxlZF9yZWRfZGRyID0gbGVkX3JlZF9k
ZHIgfCBsZWRfcmVkOwogIGxlZF9ncmVlbl9wb3J0ID0gbGVkX2dyZWVuX3BvcnQgfCBsZWRfZ3Jl
ZW47CiAgbGVkX2dyZWVuX2RkciA9IGxlZF9ncmVlbl9kZHIgfCBsZWRfZ3JlZW47CgogIHdoaWxl
ICgxKSB7CiAgICBsZWRfcmVkX3BvcnQgPSBsZWRfcmVkX3BvcnQgfCBsZWRfcmVkOwogICAgbGVk
X2dyZWVuX3BvcnQgPSBsZWRfZ3JlZW5fcG9ydCAmIH5sZWRfZ3JlZW47CgogICAgZGVsYXkoKTsK
CiAgICBsZWRfZ3JlZW5fcG9ydCA9IGxlZF9ncmVlbl9wb3J0IHwgbGVkX2dyZWVuOwogICAgbGVk
X3JlZF9wb3J0ID0gbGVkX3JlZF9wb3J0ICYgfmxlZF9yZWQ7CgogICAgZGVsYXkoKTsKICB9Cgog
IHJldHVybiAwOwp9IAogCnZvaWQgX19wcmVtYWluKCkgCnsKICAgIF9fYXNtX18gX192b2xhdGls
ZV9fICgiY2xyIDB4MTYiKTsKfSAKCnZvaWQgZGVsYXkoKQp7CiAgX19hc21fXyBfX3ZvbGF0aWxl
X18gKCJQU0hEXG5cdExERAkweEZGRkZcblx0REJORQlELC0zXG5cdFBVTERcblx0UlRTIik7Cn0K


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

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-17  9:16 george [this message]
2002-06-14 16:06 ciceron
2002-07-22 13:20 ciceron

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=20020517161312.16543.qmail@sources.redhat.com \
    --to=george@mpimf-heidelberg.mpg.de \
    --cc=gcc-gnats@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).