public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Geoff Keating <geoffk@geoffk.org>
To: drow@mvista.com
Cc: camm@enhanced.com, binutils@sources.redhat.com, gcl-devel@gnu.org
Subject: Re: [Gcl-devel] Re: BFD relocations
Date: Wed, 05 Jun 2002 20:09:00 -0000	[thread overview]
Message-ID: <200206060309.g5639kE11865@desire.geoffk.org> (raw)
In-Reply-To: <20020605230537.GA4336@nevyn.them.org> (message from Daniel Jacobowitz on Wed, 5 Jun 2002 19:05:37 -0400)

> Date: Wed, 5 Jun 2002 19:05:37 -0400
> From: Daniel Jacobowitz <drow@mvista.com>

> > 1) Is it possible to know for sure that a smaller range could be
> >    flushed safely?
> 
> I believe glibc has an "aux" mechanism to convey this.  I don't know
> how it works, though.  Geoff?

The kernel does, in some versions, pass the size of a cache line (8,
16, whatever), but I don't think glibc passes it to userland yet.
There's no way to know which lines don't need flushing.

-- 
- Geoffrey Keating <geoffk@geoffk.org> <geoffk@redhat.com>

      parent reply	other threads:[~2002-06-06  3:09 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-02 20:42 Camm Maguire
2002-06-02 22:06 ` Daniel Jacobowitz
2002-06-03 15:08   ` Camm Maguire
2002-06-03 15:29     ` Daniel Jacobowitz
2002-06-04 14:34       ` [Gcl-devel] " Camm Maguire
2002-06-04 14:42         ` Geoff Keating
2002-06-04 14:44         ` Daniel Jacobowitz
2002-06-04 15:06           ` Camm Maguire
2002-06-04 15:33             ` Daniel Jacobowitz
2002-06-05 16:03               ` Camm Maguire
2002-06-05 16:09                 ` Daniel Jacobowitz
2002-06-05 17:21                   ` Camm Maguire
2002-06-05 18:13                     ` Daniel Jacobowitz
2002-06-06 20:14                       ` Camm Maguire
2002-06-06 21:00                         ` Daniel Jacobowitz
2002-06-06 22:03                           ` Jason R Thorpe
2002-06-07  6:55                         ` Paul Koning
2002-06-10 15:35                           ` Camm Maguire
2002-06-10 16:10                             ` Daniel Jacobowitz
2002-06-14  8:51                               ` Flushing the d-cache (was Re: BFD relocations) Camm Maguire
2002-06-14  9:16                                 ` Philip Blundell
2002-06-14 12:22                                   ` [Gcl-devel] " Camm Maguire
2002-06-14 12:34                                     ` Philip Blundell
2002-06-14 13:10                                 ` Andreas Schwab
2002-06-17 15:37                                 ` Richard Zidlicky
2002-06-17 20:09                                   ` [Gcl-devel] " Camm Maguire
2002-06-19 11:25                               ` MIPS bfd_get_relocated_section_contents broken Camm Maguire
2002-07-27  0:06                               ` [Gcl-devel] Re: BFD relocations Camm Maguire
2002-07-27  9:08                                 ` Alan Modra
2002-07-27 12:23                                   ` Camm Maguire
2002-07-30  0:46                                     ` Alan Modra
2002-08-11  9:26                                       ` BFD relocations -- alpha Camm Maguire
2002-06-05 20:09                   ` Geoff Keating [this message]

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=200206060309.g5639kE11865@desire.geoffk.org \
    --to=geoffk@geoffk.org \
    --cc=binutils@sources.redhat.com \
    --cc=camm@enhanced.com \
    --cc=drow@mvista.com \
    --cc=gcl-devel@gnu.org \
    --cc=geoffk@redhat.com \
    /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).