public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Janis Johnson <janis187@us.ibm.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: target/5379: internal error: Segmentation fault (prefetch related?) Date: Thu, 17 Jan 2002 16:26:00 -0000 [thread overview] Message-ID: <20020118002602.13042.qmail@sources.redhat.com> (raw) The following reply was made to PR target/5379; it has been noted by GNATS. From: Janis Johnson <janis187@us.ibm.com> To: ritzert@t-online.de Cc: gcc-gnats@gcc.gnu.org Subject: Re: target/5379: internal error: Segmentation fault (prefetch related?) Date: Thu, 17 Jan 2002 16:20:51 -0800 On Mon, Jan 14, 2002 at 06:59:52PM -0000, ritzert@t-online.de wrote: > > >Number: 5379 > >Category: target > >Synopsis: internal error: Segmentation fault (prefetch related?) > >Class: ice-on-legal-code > >Arrival-Date: Mon Jan 14 11:06:30 PST 2002 > >Originator: ritzert@t-online.de > >Release: gcc version 3.1 20020114 (experimental) > >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 I'm currently testing a fix for this and hope to submit the patch within a day or two. The problem is related to prefetch and is specific to x86 targets. Janis
next reply other threads:[~2002-01-18 0:26 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-01-17 16:26 Janis Johnson [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-01-22 13:46 Janis Johnson 2002-01-14 11:06 ritzert
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=20020118002602.13042.qmail@sources.redhat.com \ --to=janis187@us.ibm.com \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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: linkBe 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).