all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: Glenn Morris <rgm@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: master updated (eb787d7 -> dc18a09)
Date: Tue, 14 Aug 2018 04:40:29 -0700	[thread overview]
Message-ID: <6958cf3f-ea95-c7e8-e448-7762ba4bf6a2@cs.ucla.edu> (raw)
In-Reply-To: <ozva8dmpws.fsf@fencepost.gnu.org>

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

Glenn Morris wrote:
> This fails to build with --enable-check-lisp-object-type.

Thanks for mentioning that. --enable-check-lisp-object-type worked for me, 
perhaps because I'm using a different compiler version. I installed the 
attached; please give it a try.

[-- Attachment #2: 0001-Port-recent-changes-to-older-GCC.patch --]
[-- Type: text/x-patch, Size: 775 bytes --]

From 396a33a3656a0e2bbe2f24a81df64914491c44e5 Mon Sep 17 00:00:00 2001
From: Paul Eggert <eggert@cs.ucla.edu>
Date: Tue, 14 Aug 2018 04:38:44 -0700
Subject: [PATCH] Port recent changes to older GCC

Problem reported by Glenn Morris in:
https://lists.gnu.org/r/emacs-devel/2018-08/msg00446.html
* src/lisp.h (make_pointer_integer_unsafe):
Port to older GCC.
---
 src/lisp.h | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/src/lisp.h b/src/lisp.h
index 18d53537cc..da93efdd93 100644
--- a/src/lisp.h
+++ b/src/lisp.h
@@ -1191,7 +1191,8 @@ XFIXNUMPTR (Lisp_Object a)
 INLINE Lisp_Object
 make_pointer_integer_unsafe (void *p)
 {
-  return TAG_PTR (Lisp_Int0, p);
+  Lisp_Object a = TAG_PTR (Lisp_Int0, p);
+  return a;
 }
 
 INLINE Lisp_Object
-- 
2.17.1


      reply	other threads:[~2018-08-14 11:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20180813225557.8746.83112@vcs0.savannah.gnu.org>
2018-08-14  6:18 ` master updated (eb787d7 -> dc18a09) Glenn Morris
2018-08-14 11:40   ` Paul Eggert [this message]

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=6958cf3f-ea95-c7e8-e448-7762ba4bf6a2@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --cc=emacs-devel@gnu.org \
    --cc=rgm@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.