public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: ritzert@t-online.de
To: gcc-gnats@gcc.gnu.org
Subject: target/5379: internal error: Segmentation fault (prefetch related?)
Date: Mon, 14 Jan 2002 11:06:00 -0000	[thread overview]
Message-ID: <20020114185952.23676.qmail@sources.redhat.com> (raw)


>Number:         5379
>Category:       target
>Synopsis:       internal error: Segmentation fault (prefetch related?)
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          ice-on-legal-code
>Submitter-Id:   net
>Arrival-Date:   Mon Jan 14 11:06:30 PST 2002
>Closed-Date:
>Last-Modified:
>Originator:     ritzert@t-online.de
>Release:        gcc version 3.1 20020114 (experimental)
>Organization:
>Environment:
Linux 2.4.16, Athlon
>Description:
# gcc -c x.c -fprefetch-loop-arrays -march=athlon -O2
x.c: In function `_KDE_IceGetPoValidAuthIndices':
x.c:33: internal error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.
>How-To-Repeat:
Compile the attached file with
gcc -c x.c -fprefetch-loop-arrays -march=athlon -O2
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: text/x-csrc; name="x.c"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="x.c"

ZXh0ZXJuIGludCBhY2Nlc3MoIGNoYXIqICk7CmV4dGVybiBpbnQgYSgpOwpjaGFyKiBmb29jcCgp
OwoKdm9pZApfS0RFX0ljZUdldFBvVmFsaWRBdXRoSW5kaWNlcyAocHJvdG9jb2xfbmFtZSwgbnVt
X2luZGljZXNfcmV0LCBpbmRpY2VzX3JldCkKY29uc3QgY2hhciAqcHJvdG9jb2xfbmFtZTsKaW50
ICpudW1faW5kaWNlc19yZXQ7CmludCAqaW5kaWNlc19yZXQ7CnsKICAgIGludCBhdXRoX2ZpbGU7
CiAgICBjaGFyICpmaWxlbmFtZTsKICAgIGludCBpbmRleF9yZXQsIGk7CgogICAgaWYgKCEoZmls
ZW5hbWUgPSBmb29jcCAoKSkpCiAgICAgICAgcmV0dXJuOwoKICAgIGlmIChhY2Nlc3MgKGZpbGVu
YW1lKSkKICAgICAgICByZXR1cm47CgogICAgaWYgKGF1dGhfZmlsZSA9IGFjY2VzcyAoZmlsZW5h
bWUpKQogICAgICAgIHJldHVybjsKCiAgICBmb3IgKDs7KQogICAgewogICAgICAgIGlmIChzdHJj
bXAgKHByb3RvY29sX25hbWUsIHByb3RvY29sX25hbWUpID09IDAgKQogICAgICAgIHsKICAgICAg
ICAgICAgZm9yIChpID0gMDsgaSA8ICpudW1faW5kaWNlc19yZXQ7IGkrKykKICAgICAgICAgICAg
ICAgIGlmIChpbmRleF9yZXQgPT0gaW5kaWNlc19yZXRbaV0pCiAgICAgICAgICAgICAgICAgICAg
YnJlYWs7CiAgICAgICAgfQogICAgfQp9Cgo=


             reply	other threads:[~2002-01-14 19:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-14 11:06 ritzert [this message]
2002-01-17 16:26 Janis Johnson
2002-01-22 13:46 Janis Johnson

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=20020114185952.23676.qmail@sources.redhat.com \
    --to=ritzert@t-online.de \
    --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).