public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: cato@df.lth.se
To: gcc-gnats@gcc.gnu.org
Subject: bootstrap/7770: m68k ICE during bootstrap
Date: Thu, 29 Aug 2002 20:46:00 -0000	[thread overview]
Message-ID: <20020830030835.22882.qmail@sources.redhat.com> (raw)


>Number:         7770
>Category:       bootstrap
>Synopsis:       m68k ICE during bootstrap
>Confidential:   no
>Severity:       critical
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          ice-on-legal-code
>Submitter-Id:   net
>Arrival-Date:   Thu Aug 29 20:16:00 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     Krister Walfridsson
>Release:        gcc version 3.3 20020828 (experimental)
>Organization:
>Environment:
m68k-unknown-netbsdelf1.5ZC
>Description:
The compiler reports an ICE during bootstrap, when compiling unwind-dw2-fde.c:
../../gcc/gcc/unwind-dw2-fde.c: In function `init_object':
../../gcc/gcc/unwind-dw2-fde.c:924: internal compiler error: Internal compiler error in reg_overlap_mentioned_p, at rtlanal.c:1543

I have attached a .i file that reproduces the problem.
>How-To-Repeat:
./xgcc -B./ -O2 -c bug.i
>Fix:

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

IyAxICJidWcuYyIKIyAxICI8YnVpbHQtaW4+IgojIDEgIjxjb21tYW5kIGxpbmU+IgojIDEgImJ1
Zy5jIgpzdHJ1Y3Qgb2JqZWN0CnsKICAgIHN0cnVjdCB7CiAgICAgIHVuc2lnbmVkIGxvbmcgc29y
dGVkIDogMTsKICAgICAgdW5zaWduZWQgbG9uZyBmcm9tX2FycmF5IDogMTsKICAgICAgdW5zaWdu
ZWQgbG9uZyBtaXhlZF9lbmNvZGluZyA6IDE7CiAgICAgIHVuc2lnbmVkIGxvbmcgZW5jb2Rpbmcg
OiA4OwogICAgICB1bnNpZ25lZCBsb25nIGNvdW50IDogMjE7CiAgICB9IGI7Cn07CgppbnQKc3Rh
cnRfZmRlX3NvcnQgKHZvaWQpOwoKaW50CmNsYXNzaWZ5X29iamVjdF9vdmVyX2ZkZXMgKHZvaWQg
Km9iKTsKCnZvaWQKYWRkX2ZkZXMgKHN0cnVjdCBvYmplY3QgKm9iKTsKCmlubGluZSB2b2lkCmlu
aXRfb2JqZWN0IChzdHJ1Y3Qgb2JqZWN0KiBvYikKewogIGludCBjb3VudDsKCiAgY291bnQgPSBv
Yi0+Yi5jb3VudDsKICBpZiAoY291bnQgPT0gMCkKICAgIHsKICAgICAgaWYgKG9iLT5iLmZyb21f
YXJyYXkpCiAgICAgICAgICAgIGNvdW50ICs9IGNsYXNzaWZ5X29iamVjdF9vdmVyX2ZkZXMgKG9i
KTsKCiAgICAgIG9iLT5iLmNvdW50ID0gY291bnQ7CiAgICAgIGlmIChvYi0+Yi5jb3VudCAhPSBj
b3VudCkKICAgICAgICBvYi0+Yi5jb3VudCA9IDA7CiAgICB9CgogIGlmICghc3RhcnRfZmRlX3Nv
cnQgKCkpCiAgICByZXR1cm47CgogIGlmIChvYi0+Yi5mcm9tX2FycmF5KQogICAgYWRkX2ZkZXMg
KG9iKTsKfQo=


             reply	other threads:[~2002-08-30  3:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-29 20:46 cato [this message]
2002-08-29 21:36 Jason R Thorpe
2002-09-22 10:09 kristerw

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=20020830030835.22882.qmail@sources.redhat.com \
    --to=cato@df.lth.se \
    --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).