public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rearnsha at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/82150] Produces a branch prefetch which causes a hang
Date: Thu, 28 Jan 2021 18:44:30 +0000	[thread overview]
Message-ID: <bug-82150-4-fejOrtLFdJ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-82150-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82150

Richard Earnshaw <rearnsha at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |INVALID
             Status|UNCONFIRMED                 |RESOLVED

--- Comment #14 from Richard Earnshaw <rearnsha at gcc dot gnu.org> ---
The code generated is architecturally correct.  If your core is prefetching
from addresses that are not valid then this is indicative that the MMU is
incorrectly configured for your system.  Prefetches will NOT be attempted from
unmapped pages, or pages that are mapped as device memory.

So you need to find out why your memory system has not been correctly set up.

There's no bug in GCC here.

  parent reply	other threads:[~2021-01-28 18:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-82150-4@http.gcc.gnu.org/bugzilla/>
2021-01-26 14:58 ` david.welch at netronome dot com
2021-01-26 15:02 ` david.welch at netronome dot com
2021-01-26 21:06 ` david.welch at netronome dot com
2021-01-28 18:44 ` rearnsha at gcc dot gnu.org [this message]
2021-01-28 20:12 ` david.welch at netronome dot com
2021-01-29 11:47 ` rearnsha at gcc dot gnu.org
2021-01-29 12:24 ` rearnsha at gcc dot gnu.org

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=bug-82150-4-fejOrtLFdJ@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).