From: Paul Eggert <eggert@cs.ucla.edu>
To: Ravi Desai <ravi@ravidesai.com>, emacs-devel@gnu.org
Subject: Re: Revisit patch for Bug#11935?
Date: Sun, 4 Dec 2016 18:21:31 -0800 [thread overview]
Message-ID: <661e36f7-2a24-d7f3-f7d2-f1ef98216f5b@cs.ucla.edu> (raw)
In-Reply-To: <c8258cb4-13ed-3cfc-fb71-6b4665d020ef@ravidesai.com>
[-- Attachment #1: Type: text/plain, Size: 371 bytes --]
On 12/04/2016 04:07 PM, Ravi Desai wrote:
> Is this now a good time to revisit the original patch submitted for
> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=11935 ?
I would guess not. As I recall, Eli is still using GCC 3, and I suspect
some other developers are still using pre-4.8 GCC. Let's kick this can
down the road a while more. I installed the attached.
[-- Attachment #2: 0001-src-lisp.h-Update-comment-to-kick-Og-down-the-road.patch --]
[-- Type: text/x-patch, Size: 909 bytes --]
From 02055b6de9df82a68d24ee38e7d19e93191938c2 Mon Sep 17 00:00:00 2001
From: Paul Eggert <eggert@cs.ucla.edu>
Date: Sun, 4 Dec 2016 18:19:01 -0800
Subject: [PATCH] * src/lisp.h: Update comment to kick -Og down the road.
---
src/lisp.h | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/src/lisp.h b/src/lisp.h
index 94f1152..7dd9145 100644
--- a/src/lisp.h
+++ b/src/lisp.h
@@ -292,9 +292,8 @@ error !;
used elsewhere.
FIXME: Remove the lisp_h_OP macros, and define just the inline OP
- functions, once most developers have access to GCC 4.8 or later and
- can use "gcc -Og" to debug. Maybe in the year 2016. See
- Bug#11935.
+ functions, once "gcc -Og" (new to GCC 4.8) works well enough for
+ Emacs developers. Maybe in the year 2020. See Bug#11935.
Commentary for these macros can be found near their corresponding
functions, below. */
--
2.7.4
next prev parent reply other threads:[~2016-12-05 2:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-05 0:07 Revisit patch for Bug#11935? Ravi Desai
2016-12-05 2:21 ` Paul Eggert [this message]
2016-12-05 8:12 ` Colin Baxter
2016-12-05 13:57 ` Ravi Desai
2016-12-05 15:47 ` Eli Zaretskii
2016-12-05 16:26 ` martin rudalics
2016-12-05 17:08 ` Paul Eggert
2016-12-05 17:44 ` Stefan Monnier
2016-12-05 18:46 ` Eli Zaretskii
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=661e36f7-2a24-d7f3-f7d2-f1ef98216f5b@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=ravi@ravidesai.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 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.