unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Eli Zaretskii" <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: USE_LSB_TAG and MS-DOS
Date: Tue, 18 May 2004 17:08:21 +0200	[thread overview]
Message-ID: <9003-Tue18May2004170821+0300-eliz@gnu.org> (raw)
In-Reply-To: <m1n048lzci.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on 16 May 2004 19:40:23 -0400)

> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Date: 16 May 2004 19:40:23 -0400
> 
> > Btw, the way DECL_ALIGN and USE_LSB_TAG are defined on lisp.h doesn't
> > leave any elegant way for specific platforms to turn that off without
> > cluttering lisp.h with ugly OS-specific #ifdef's.  Perhaps we should
> > devise a cleaner way.
> 
> It was devised in the hope that it will only be turned on where it's safe.
> Obviously, that's not the way it works, but at least it *should* work that
> way, so I think we're just hitting a bug.
> After all, all we need is to make sure pointers are multiples of 8.
> GNU malloc guarantees that AFAIK for malloced objects and DECL_ALIGN allows
> to get the same guarantee for static objects, so if we have both the only
> reasonf ro USE_LSB_TAG to fail is a bug, right?

I still think we should have an easy way to force or disable use of
LSB tags.  lisp.h already checks MAC_OSX for that, which is not nice
IMHO.

How about if USE_LSB_TAG's value will tell this, viz

  - if USE_LSB_TAG is defined to a non-zero value, always use LSB tags
  - if it is zero, don't use them
  - if it's undefined, lisp.h will use the current method to define
    it to either zero or 1

With this setup, Mac OSX could #define USE_LSB_TAG 1 in its config
file, and be done with that.

  parent reply	other threads:[~2004-05-18 15:08 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-15 13:07 USE_LSB_TAG and MS-DOS Eli Zaretskii
2004-05-15 15:10 ` Jason Rumney
2004-05-15 18:24   ` Eli Zaretskii
2004-05-17  8:13     ` Jason Rumney
2004-05-17  8:45       ` YAMAMOTO Mitsuharu
2004-05-18 20:34         ` Jason Rumney
2004-05-17 10:13       ` Eli Zaretskii
2004-05-17 10:30         ` Jason Rumney
2004-05-16 23:40 ` Stefan Monnier
2004-05-17  6:10   ` Eli Zaretskii
2004-05-17 16:22     ` Stefan Monnier
2004-05-17 22:31       ` Miles Bader
2004-05-18 13:36         ` Stefan Monnier
2004-05-18 15:00       ` Eli Zaretskii
2004-05-18 14:59         ` Andreas Schwab
2004-05-18 15:13         ` Stefan Monnier
2004-05-18 18:45           ` Eli Zaretskii
2004-05-18 19:12             ` Stefan Monnier
2004-05-19  6:25               ` Eli Zaretskii
2004-05-20 16:34               ` Eli Zaretskii
2004-05-18 15:08   ` Eli Zaretskii [this message]
2004-05-18 15:18     ` Stefan Monnier
2004-05-18 15:09   ` Eli Zaretskii
  -- strict thread matches above, loose matches on Subject: below --
2004-05-18 19:08 Michael Mauger
2004-05-18 22:10 ` Stefan Monnier
2004-05-18 23:32 ` Jason Rumney
2004-05-19 14:58   ` Michael Mauger

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=9003-Tue18May2004170821+0300-eliz@gnu.org \
    --to=eliz@gnu.org \
    --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 public inbox

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

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).