all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: Dmitry Antipov <antipov@mvista.com>, emacs-devel@gnu.org
Subject: Re: immediate strings #2
Date: Mon, 28 Nov 2011 16:54:36 -0500	[thread overview]
Message-ID: <jwvliqzap9x.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <m21ussypn3.fsf@igel.home> (Andreas Schwab's message of "Mon, 28 Nov 2011 21:10:24 +0100")

>> I don't know any C compiler able to allocate unions at the bit level,
> It can't since it's not a bitfield (which isn't possible anyway).

Not that it's relevant to Emacs, but I don't know which part of the
C standard would force a C compiler to layout all unions at an
"addressable" offset.  I mean, wouldn't it be valid for a compiler to
analyze the whole program and decide "oh, the code uses the union in
such a way that I can bit-align it to save some padding space and noone
will notice"?


        Stefan



  reply	other threads:[~2011-11-28 21:54 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-28  9:11 immediate strings #2 Dmitry Antipov
2011-11-28 17:33 ` Stefan Monnier
2011-11-28 19:48   ` Ken Raeburn
2011-11-28 20:10   ` Andreas Schwab
2011-11-28 21:54     ` Stefan Monnier [this message]
2011-11-28 22:25       ` Andreas Schwab
2011-11-29  0:57         ` Ken Raeburn
2011-11-29  8:44           ` Andreas Schwab
2011-11-29 15:48             ` Ken Raeburn
2011-11-29 16:08               ` Andreas Schwab
2011-11-30 16:43                 ` Ken Raeburn
2011-11-28 22:18   ` Paul Eggert
2011-11-29  2:07     ` Stefan Monnier
2011-11-29  3:37       ` Dmitry Antipov
2011-11-29  8:50       ` Paul Eggert
2011-11-30  5:37         ` Dmitry Antipov
2011-11-30  9:35           ` Paul Eggert
2011-11-30 16:43             ` Ken Raeburn
2011-11-30 21:44               ` Paul Eggert
2011-11-29  3:17     ` Dmitry Antipov
2011-11-29  5:29   ` Dmitry Antipov

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=jwvliqzap9x.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=antipov@mvista.com \
    --cc=emacs-devel@gnu.org \
    --cc=schwab@linux-m68k.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.