public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: falk@efalk.org
To: gcc-gnats@gcc.gnu.org
Subject: c/7324: Internal compiler error in fixup_var_refs_1, at function.c:1874
Date: Mon, 15 Jul 2002 22:36:00 -0000	[thread overview]
Message-ID: <20020716053104.7893.qmail@sources.redhat.com> (raw)


>Number:         7324
>Category:       c
>Synopsis:       Internal compiler error in fixup_var_refs_1, at function.c:1874
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          ice-on-legal-code
>Submitter-Id:   net
>Arrival-Date:   Mon Jul 15 22:36:00 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     falk@efalk.org
>Release:        2.96
>Organization:
>Environment:
Redhat 7.2
>Description:
See attached source code.  Compile with cc -O and get
the message

foo.c:41: Internal compiler error in fixup_var_refs_1, at function.c:1874
>How-To-Repeat:
Compile enclosed code with 2.96 compiler and -O flag.
>Fix:

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

LyogTm90ZXM6CiAqCiAqICBnY2MgdjIuOTYsICBidWd6aWxsYSBidWcgNjQ0NDUKICoKICogIGNv
bXBpbGUgd2l0aCBjYyAtTyAtYyBmb28uYwogKgogKiAgQ29tcGlsZXIgcmVwb3J0czoKICoKICog
IGZvby5jOiBJbiBmdW5jdGlvbiBgZm9vJzoKICogIGZvby5jOjQxOiBJbnRlcm5hbCBjb21waWxl
ciBlcnJvciBpbiBmaXh1cF92YXJfcmVmc18xLCBhdCBmdW5jdGlvbi5jOjE4NzQKICogIFBsZWFz
ZSBzdWJtaXQgYSBmdWxsIGJ1ZyByZXBvcnQuCiAqICBTZWUgPFVSTDpodHRwOi8vYnVnemlsbGEu
cmVkaGF0LmNvbS9idWd6aWxsYS8+IGZvciBpbnN0cnVjdGlvbnMuCiAqCiAqCiAqICBpbnQgb3Ig
ZmxvYXQsIHRoZSByZXN1bHRzIGFyZSB0aGUgc2FtZS4KICoKICogIFNldCBwb2ludCB4LHkgdHlw
ZXMgdG8gZG91YmxlLCBhbmQgdGhlIHByb2JsZW0gZ29lcyBhd2F5LgogKgogKiAgdHJ5IHRvIHNp
bXBsaWZ5ICJkaXN0ID0iIGxpbmUsIGFuZCBwcm9ibGVtIGdvZXMgYXdheS4KICoKICogIGNoYW5n
ZSAoJnYpLT55IHRvIHYueSBhbmQgcHJvYmxlbSBnb2VzIGF3YXkKICoKICogICgidiA9ICpwIiBs
aW5lIGlzIG5vdCBuZWVkZWQgdG8gc2hvdyB0aGUgYnVnLCBidXQgSQogKiAgbGVmdCBpdCB0aGVy
ZSB0byBrZWVwIGZ1bmN0aW9uIGxlZ2l0aW1hdGUuKQogKi8KCnR5cGVkZWYgc3RydWN0IHBvaW50
IHsKCSAgaW50IHgseSA7Cgl9IFBvaW50IDsKCnZvaWQKZm9vKFBvaW50ICpwKQp7CglQb2ludCB2
IDsKCWludCBkaXN0IDsKCWludCBzIDsKCgl2ID0gKnAgOwoKCWRpc3QgPSB2LnkgPT0gMCA/ICh2
LnggPCAwID8gLXYueCA6IHYueCkgOiB2Lngqdi54IDsKCglzID0gcC0+eCAqICgmdiktPnkgOwp9
Cg==


                 reply	other threads:[~2002-07-16  5: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=20020716053104.7893.qmail@sources.redhat.com \
    --to=falk@efalk.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).