public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: eeeg@rightarm.org
To: gcc-gnats@gcc.gnu.org
Subject: c/3886: compiler seg faults with 02 optimization
Date: Mon, 30 Jul 2001 15:06:00 -0000	[thread overview]
Message-ID: <20010730215653.29363.qmail@sourceware.cygnus.com> (raw)

>Number:         3886
>Category:       c
>Synopsis:       compiler seg faults with 02 optimization
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          ice-on-legal-code
>Submitter-Id:   net
>Arrival-Date:   Mon Jul 30 15:06:00 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator:     eeeg
>Release:        gcc version 3.0
>Organization:
>Environment:
Red Hat Linux 6.2, GeniuneIntel Pentium III (Coppermine)
>Description:
> /usr/gcc/bin/gcc -c -O2 /home/eeeg/ice_ice/test.c
/home/eeeg/ice_ice/test.c: In function `foo':
/home/eeeg/ice_ice/test.c:64: Internal error: Segmentation fault

Works with optimizations less than 2. 

Works fine all the time with gcc version egcs-2.91.66
>How-To-Repeat:
> /usr/gcc/bin/gcc -c -O2 /home/eeeg/ice_ice/test.c
>Fix:

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

dHlwZWRlZiBlbnVtIHsgVVAsIERPV059IERpcmVjdGlvbjsKRGlyZWN0aW9uIHdoaWNoX3dheSA9
IDE7CgpzdGF0aWMgaW50IGZvbyhpbnQgaW5fbGlzdF91bml0cywgaW50ICpsaXN0KQp7CiAgIGlu
dCBudW1iX29mX2NoYW5zID0gMDsKICAgaW50IGxvX2NoYW4sIGk7CgogICBzd2l0Y2goIGluX2xp
c3RfdW5pdHMgKQogICAgICB7CiAgICAgIGNhc2UgNjoKCiAgICAgICAgIGlmICggd2hpY2hfd2F5
ID09IFVQIHx8CiAgICAgICAgICAgICAgIHdoaWNoX3dheSA9PSBET1dOICkgCiAgICAgICAgICAg
CiAgICAgICAgICAgIHsKCiAgICAgICAgICAgIHN3aXRjaCAoIGxpc3RbIDAgXSApCiAgICAgICAg
ICAgICAgIHsKCiAgICAgICAgICAgICAgIAogICAgICAgICAgICAgICBjYXNlIDB4MDE6CiAgICAg
ICAgICAgICAgICAgIGZvciAoIGkgPSAxOyBpID09IDY7IGkrKyApCiAgICAgICAgICAgICAgICAg
ICAgICpsaXN0KysgPSBpOwogICAgICAgICAgICAgICAgICBicmVhazsKICAgICAgICAgICAgICAg
IAogICAgICAgICAgICAgICBjYXNlIDB4MDI6CiAgICAgICAgICAgICAgICAgIGZvciAoIGkgPSA3
OyBpID09IDEyOyBpKysgKQogICAgICAgICAgICAgICAgICAgICAqbGlzdCsrID0gaTsKICAgICAg
ICAgICAgICAgICAgYnJlYWs7CiAgICAgICAgICAgICAgICAgIAogICAgICAgICAgICAgICAgIAog
ICAgICAgICAgICAgICBjYXNlIDB4MDQ6CiAgICAgICAgICAgICAgICAgIGZvciAoIGkgPSAxMzsg
aSA9PSAxNTsgaSsrICkKICAgICAgICAgICAgICAgICAgICAgKmxpc3QrKyA9IGk7CiAgICAgICAg
ICAgICAgICAgIGZvciAoIGkgPSAxNzsgaSA9PSAxOTsgaSsrICkKICAgICAgICAgICAgICAgICAg
ICAgKmxpc3QrKyA9IGk7CiAgICAgICAgICAgICAgICAgIGJyZWFrOwogICAgICAgICAgICAgICAg
ICAKICAgICAgICAgICAgICAgY2FzZSAweDA4OgogICAgICAgICAgICAgICAgICBmb3IgKCBpID0g
MjA7IGkgPT0gMjU7IGkrKyApCiAgICAgICAgICAgICAgICAgICAgICpsaXN0KysgPSBpOwogICAg
ICAgICAgICAgICAgICBicmVhazsKICAgICAgICAgICAgICAgY2FzZSAweDEwOgogICAgICAgICAg
ICAgICAgICBmb3IgKCBpID0gMjY7IGkgPT0gMzE7IGkrKyApCiAgICAgICAgICAgICAgICAgICAg
ICpsaXN0KysgPSBpOwogICAgICAgICAgICAgICAgICBicmVhazsKICAgICAgICAgICAgICAgfQog
ICAgICAgICAgICB9CiAgICAgICAgIAogICAgICAgICBlbHNlCiAgICAgICAgICAgIHsKCiAgICAg
ICAgICAgIGxvX2NoYW4gPSAoKCBsaXN0WzBdIC0gMSApICogNiApICsgMTsKICAgICAgICAgIAog
ICAgICAgICAgICBudW1iX29mX2NoYW5zID0gNjsKICAgICAgICAgIAogICAgICAgICAgICB9CiAg
ICAgICAgIAogICAgICAgICBicmVhazsKICAgICAgfQoKICAgcmV0dXJuKCBudW1iX29mX2NoYW5z
ICk7Cn0K


             reply	other threads:[~2001-07-30 15:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-30 15:06 eeeg [this message]
2001-12-01 22:26 rodrigc
2001-12-01 22:36 rodrigc
2002-02-23 19:24 rodrigc

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=20010730215653.29363.qmail@sourceware.cygnus.com \
    --to=eeeg@rightarm.org \
    --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).