all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Thien-Thi Nguyen <ttn@gnuvola.org>
To: Dmitry Antipov <dmantipov@yandex.ru>
Cc: emacs-devel@gnu.org
Subject: Re: Note on 109327
Date: Tue, 31 Jul 2012 23:47:13 +0200	[thread overview]
Message-ID: <87obmv1u3i.fsf@zigzag.favinet> (raw)
In-Reply-To: <5017E2B3.1060608@yandex.ru> (Dmitry Antipov's message of "Tue, 31 Jul 2012 17:50:43 +0400")

[-- Attachment #1: Type: text/plain, Size: 1345 bytes --]

() Dmitry Antipov <dmantipov@yandex.ru>
() Tue, 31 Jul 2012 17:50:43 +0400

   > I think to do this well you will need separate macros for getting
   > and setting.

   Sure, but it's almost impossible to do this at once.

Why?

   At the very beginning, it's possible to "overestimate" barrier
   assuming that each XVAR (obj, field) changes FIELD in OBJ; in the
   future, reads and writes may be separated, thus giving a precise
   write barrier.

I think you're saying that you prefer to do:

a1. substitute object access (whether LHS or RHS) w/ XVAR (obj, field)
a2. distinguish LHS (which could benefit from optimization) from RHS
a3. substitue LHS ‘XVAR (...) = value’ w/ SETVAR (obj, field, value)

instead of:

b1. distinguish LHS (which could benefit from optimization) from RHS
b2. substitute LHS object access w/ SETVAR (obj, field, value)
b3. substitute RHS object access w/ XVAR (obj, field)

Is my understanding correct?

-- 
Thien-Thi Nguyen ..................................... GPG key: 4C807502
.                  NB: ttn at glug dot org is not me                   .
.                 (and has not been since 2007 or so)                  .
.                        ACCEPT NO SUBSTITUTES                         .
........... please send technical questions to mailing lists ...........

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2012-07-31 21:47 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-31 12:38 Note on 109327 Dmitry Antipov
2012-07-31 13:13 ` Dan Nicolaescu
2012-07-31 13:25   ` Dmitry Antipov
2012-07-31 13:33     ` Tom Tromey
2012-07-31 13:50       ` Dmitry Antipov
2012-07-31 21:47         ` Thien-Thi Nguyen [this message]
2012-08-01  4:34           ` Dmitry Antipov
2012-07-31 13:54 ` Juanma Barranquero
2012-07-31 17:04   ` Eli Zaretskii
2012-07-31 17:17     ` Juanma Barranquero
2012-07-31 17:35     ` joakim
2012-07-31 17:56       ` Dmitry Antipov
2012-07-31 17:42     ` Dmitry Antipov
2012-07-31 18:06       ` Refactoring in Emacs (was: Note on 109327) Eli Zaretskii
2012-08-01  4:14         ` Refactoring in Emacs Dmitry Antipov
2012-08-01 11:41           ` Refactoring in Emacs : CEDET Eric M. Ludlam
2012-08-01 14:50             ` Eli Zaretskii
2012-08-01 23:42               ` Eric Ludlam
2012-08-01 22:41           ` Refactoring in Emacs Richard Stallman
2012-08-01 14:05         ` Jason Rumney
2012-07-31 15:16 ` Note on 109327 Jan Djärv

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=87obmv1u3i.fsf@zigzag.favinet \
    --to=ttn@gnuvola.org \
    --cc=dmantipov@yandex.ru \
    --cc=emacs-devel@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.