public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: tanmoy@lanl.gov
To: gcc-gnats@gcc.gnu.org
Subject: optimization/3906: Internal compiler error in change_address, at emit-rtl.c:1635
Date: Tue, 31 Jul 2001 17:16:00 -0000	[thread overview]
Message-ID: <20010801000608.6924.qmail@sourceware.cygnus.com> (raw)

>Number:         3906
>Category:       optimization
>Synopsis:       Internal compiler error in change_address, at emit-rtl.c:1635
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          ice-on-legal-code
>Submitter-Id:   net
>Arrival-Date:   Tue Jul 31 17:16:00 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator:     Tanmoy Bhattacharya
>Release:        gcc version 3.0 (thread model: posix)
>Organization:
>Environment:
SunOS 5.8 Generic_108528-06 sun4u sparc SUNW,Sun-Blade-100
configured by .../configure --prefix=... (i.e. all defaults)
>Description:
gcc -O -c example.c produces i.c.e as reported in synopsis.

I supply a trimmed down example.  Any further trimming
makes the problem either go away, or leaves a code that
uses variables without properly initializing them. 
>How-To-Repeat:
gcc -O -c example.i
>Fix:
Turn off optimization!!!!
>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: application/octet-stream; name="example.i"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="example.i"

IyAxICJleGFtcGxlLmMiCmRvdWJsZSBsb2cxMCgpOwpzdHJ1Y3QgeHkgewogICAgaW50IHhsYmYs
IHh1YmY7CiAgICBpbnQgeHFmOwogICAgZG91YmxlICgqeGYpICgpOwogICAgZG91YmxlIHhsYiwg
eHViOwp9OwoKc3RydWN0IHogewogICAgZG91YmxlIGxiLCB1YiwgbXVsdCwgcXVhbnQ7Cn07Cgpz
ZXRsaW0ocCkKICAgIHJlZ2lzdGVyIHN0cnVjdCB4eSAqcDsKewogICAgZG91YmxlIHQsIGRlbHRh
LCBzaWduOwogICAgc3RydWN0IHogeiA9IHswfTsKICAgIGludCBsbWFya1s1MTJdLCBtYXJrWzUx
Ml07CiAgICBkb3VibGUgbGIsIHViOwogICAgaW50IGxiZiwgdWJmOwoKICAgIGxiID0gcC0+eGxi
OwogICAgdWIgPSBwLT54dWI7CiAgICBkZWx0YSA9IHViIC0gbGI7CiAgICBzaWduID0gMTsKICAg
IGxiZiA9IHAtPnhsYmY7CiAgICB1YmYgPSBwLT54dWJmOwogICAgaWYgKGRlbHRhIDwgMCkgewog
ICAgICAgIHNpZ24gPSAtMTsKICAgIH0KICAgIGlmIChwLT54ZiA9PSBsb2cxMCAmJiBsYiA+IDAg
JiYgdWIgPiBsYikgewogICAgICAgIHNldGxvZ2xpbShsYmYsIHViZiwgbGIsIHViLCAmeik7CiAg
ICB9CiAgICBpZiAoc2lnbiA+IDApIHsKICAgICAgICBwLT54dWIgPSB6LnViOwogICAgfQp9Cg==


             reply	other threads:[~2001-07-31 17:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-31 17:16 tanmoy [this message]
2001-08-13 15:24 rodrigc
2001-11-07  3:29 Tanmoy Bhattacharya
2001-11-07  6:17 Craig Rodrigues
2001-11-25  4:26 rodrigc
2001-11-25  5:14 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=20010801000608.6924.qmail@sourceware.cygnus.com \
    --to=tanmoy@lanl.gov \
    --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).