From: Andreas Schwab <schwab@linux-m68k.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: p.stephani2@gmail.com, Paul Eggert <eggert@cs.ucla.edu>,
emacs-devel@gnu.org, alan@idiocy.org, raman@google.com
Subject: Re: san_ignore_object not found at link time
Date: Sat, 01 Aug 2020 20:52:13 +0200 [thread overview]
Message-ID: <87bljup5b6.fsf@igel.home> (raw)
In-Reply-To: <83ime2ckhb.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 01 Aug 2020 21:02:56 +0300")
On Aug 01 2020, Eli Zaretskii wrote:
>> 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 has nothing to do with XLP. If you add a wide integer to a pointer
you still have a pointer, whereas if you add a wide integer to a pointer
converted to intptr_t, the result is of the widened type.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
next prev parent reply other threads:[~2020-08-01 18:52 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
2020-08-01 18:52 ` Andreas Schwab [this message]
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=87bljup5b6.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=alan@idiocy.org \
--cc=eggert@cs.ucla.edu \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=p.stephani2@gmail.com \
--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).