all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Helmut Eller <eller.helmut@gmail.com>
To: "Gerd Möllmann" <gerd@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: scratch/igc fe90d556834: Make glyphs ambiguous roots
Date: Mon, 29 Jul 2024 08:21:29 +0200	[thread overview]
Message-ID: <87h6c8lnva.fsf@gmail.com> (raw)
In-Reply-To: <20240728174212.BDB66C41F13@vcs2.savannah.gnu.org> (Gerd Moellmann's message of "Sun, 28 Jul 2024 13:42:12 -0400 (EDT)")

On Sun, Jul 28 2024, Gerd Moellmann wrote:

>     We cannot trace glyphs in fix_window because we don't have exclusive
>     access to glyph_rows and glyphs. (An optimal solution would allocate
>     glyphs from MPS, and change data structures in a way that everything
>     needed (row->used, row->enabled_p) is available for the scanner.)

I don't understand this.  Glyph_rows aren't allocated in MPS-managed
memory so there are no memory barriers to worry about.  While fix_frame
runs, all other threads are suspended.  So why don't we have exclusive
access?  And why is it not a problem for FRAME_FONT, FRAME_DISPLAY_INFO,
etc?



       reply	other threads:[~2024-07-29  6:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <172218853212.17772.9043342656088870281@vcs2.savannah.gnu.org>
     [not found] ` <20240728174212.BDB66C41F13@vcs2.savannah.gnu.org>
2024-07-29  6:21   ` Helmut Eller [this message]
2024-07-29  7:21     ` scratch/igc fe90d556834: Make glyphs ambiguous roots Gerd Möllmann
2024-07-29  9:21       ` Helmut Eller
2024-07-29 10:19         ` Gerd Möllmann
2024-07-29 13:12           ` Gerd Möllmann
2024-07-29 14:01             ` Helmut Eller
2024-07-29 14:12               ` Gerd Möllmann

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=87h6c8lnva.fsf@gmail.com \
    --to=eller.helmut@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=gerd@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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.