public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: kris.demuynck@esat.kuleuven.ac.be
To: gcc-gnats@gcc.gnu.org
Subject: c/8555: Internal compiler error in gen_split_1231
Date: Tue, 19 Nov 2002 18:15:00 -0000	[thread overview]
Message-ID: <20021112203556.21009.qmail@sources.redhat.com> (raw)


>Number:         8555
>Category:       c
>Synopsis:       Internal compiler error in gen_split_1231
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    unassigned
>State:          open
>Class:          ice-on-legal-code
>Submitter-Id:   net
>Arrival-Date:   Tue Nov 12 12:36:03 PST 2002
>Closed-Date:
>Last-Modified:
>Originator:     Kris Demuynck
>Release:        gcc version 3.2
>Organization:
>Environment:
Linux, RedHat 7.1, 2.4.9-31smp kernel
Dell WS410, dual P3 450Mhz, 512MB SDRAM
>Description:
zz.c: In function `find_max':
zz.c:19: Internal compiler error in gen_split_1231, at insn-emit.c:16727
>How-To-Repeat:
gcc -march=pentium3 -O2 -fomit-frame-pointer -ffast-math -funroll-loops -c zz.c
>Fix:
1. Turning off any of the following optimization flags:
    -march=pentium3 -O2 -fomit-frame-pointer -ffast-math -funroll-loops
2. Some simple recoding; See the problem file 'zz.c' for an example
>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: application/octet-stream; name="zz.c"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="zz.c"

LyotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0qLwpmbG9hdCAqZmluZF9tYXgoZmxvYXQgKmRzdCxmbG9hdCAq
c3JjLGludCBzaXplLGludCBOKQp7aW50IG5keDsKIGlmKE4gPT0gMSkJCQkJLyogc2VhcmNoIG1h
eGltdW0gb2YgYW4gYXJyYXkgKi8KICB7ZmxvYXQgbXggPSBzcmNbbmR4PXNpemUtMV07CiNpZiAx
CQkJCQkvKiB0aGlzIG5vdCBzbyBlZmZpY2llbnQgaW1wbGVtZW50YXRpb24gZ2l2ZXMgcHJvYmxl
bXMgKi8KICAgZm9yKG5keD1zaXplOy0tbmR4Pj0wOyApCiNlbHNlCiAgIHdoaWxlKC0tbmR4ID49
IDApCQkJLyogdGhpcyBtb3JlIG9wdGltYWwgaW1wbGVtZW50YXRpb24gc29sdmVzIHRoZSBwcm9i
bGVtICovCiNlbmRpZgogICAge2Zsb2F0IHRtcDsKICAgICBpZigodG1wPXNyY1tuZHhdKSA+IG14
KQogICAgICAgbXggPSB0bXA7CiAgICB9CiAgIGRzdFswXSA9IG14OwogIH0KLyogZWxzZSA6IGNv
ZGUgZm9yIGZpbmRpbmcgdGhlIDxOPiBsYXJnZXN0IHZhbHVlcyBpbiBhbiBhcnJheSAqLwogcmV0
dXJuKGRzdCk7Cn0K


                 reply	other threads:[~2002-11-12 20:36 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=20021112203556.21009.qmail@sources.redhat.com \
    --to=kris.demuynck@esat.kuleuven.ac.be \
    --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).