From: Philipp Stephani <p.stephani2@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Alan Third <alan@idiocy.org>, Paul Eggert <eggert@cs.ucla.edu>,
raman <raman@google.com>, Emacs developers <emacs-devel@gnu.org>
Subject: Re: san_ignore_object not found at link time
Date: Sat, 1 Aug 2020 20:33:08 +0200 [thread overview]
Message-ID: <CAArVCkRocrOJyyvn9nixSNzRKGmVKdXWxb3zR4XzX5ZJqVEk=A@mail.gmail.com> (raw)
In-Reply-To: <83ime2ckhb.fsf@gnu.org>
Am Sa., 1. Aug. 2020 um 20:03 Uhr schrieb Eli Zaretskii <eliz@gnu.org>:
>
> > Date: Sat, 01 Aug 2020 20:51:42 +0300
> > From: Eli Zaretskii <eliz@gnu.org>
> > Cc: alan@idiocy.org, emacs-devel@gnu.org, p.stephani2@gmail.com,
> > raman@google.com
> >
> > 4641 | void *po = (char *) ((intptr_t) (char *) XLP (obj)
> > | ^
> >
> > This is a 32-bit build --with-wide-int, in case it matters, where
> > EMACS_INT is a 64-bit data type.
>
> Btw, I'm probably missing something, because I don't understand how
> XLP in its current definition can work in a --with-wide-int build,
> where the size of a Lisp_Object is wider than both intptr_t and a
> 'void *'.
This is somewhat subtle, but I think in this case it works because the
function bails out for the int types, and all other types are tagged
pointers.
next prev parent reply other threads:[~2020-08-01 18:33 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-01 14:10 san_ignore_object not found at link time T.V Raman
2020-08-01 14:37 ` Eli Zaretskii
2020-08-01 14:45 ` T.V Raman
2020-08-01 14:45 ` Eli Zaretskii
2020-08-01 15:02 ` Philipp Stephani
2020-08-01 15:38 ` Alan Third
2020-08-01 17:32 ` Philipp Stephani
2020-08-01 17:51 ` Eli Zaretskii
2020-08-01 18:02 ` Eli Zaretskii
2020-08-01 18:33 ` Philipp Stephani [this message]
2020-08-01 18:52 ` Andreas Schwab
2020-08-01 18:29 ` Philipp Stephani
2020-08-01 18:32 ` Eli Zaretskii
2020-08-01 18:35 ` Philipp Stephani
2020-08-01 19:17 ` Philipp Stephani
2020-08-01 19:21 ` Philipp Stephani
2020-08-01 19:21 ` Eli Zaretskii
2020-08-01 19:26 ` Eli Zaretskii
2020-08-01 19:40 ` Philipp Stephani
2020-08-02 16:08 ` Eli Zaretskii
2020-08-01 18:09 ` T.V Raman
2020-08-01 18:13 ` Alan Third
2020-08-01 16:43 ` T.V Raman
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='CAArVCkRocrOJyyvn9nixSNzRKGmVKdXWxb3zR4XzX5ZJqVEk=A@mail.gmail.com' \
--to=p.stephani2@gmail.com \
--cc=alan@idiocy.org \
--cc=eggert@cs.ucla.edu \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=raman@google.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.
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).