From: Eli Zaretskii <eliz@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: ravi@ravidesai.com, emacs-devel@gnu.org
Subject: Re: Revisit patch for Bug#11935?
Date: Mon, 05 Dec 2016 17:47:19 +0200 [thread overview]
Message-ID: <8337i2l6ns.fsf@gnu.org> (raw)
In-Reply-To: <661e36f7-2a24-d7f3-f7d2-f1ef98216f5b@cs.ucla.edu> (message from Paul Eggert on Sun, 4 Dec 2016 18:21:31 -0800)
> From: Paul Eggert <eggert@cs.ucla.edu>
> Date: Sun, 4 Dec 2016 18:21:31 -0800
>
> 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
No, those days are long gone. 5.3.0 is what I have here now.
> 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.
Thanks.
I think this is related not only to the GCC version, but also to
whether developers use -Og when building development versions of
Emacs. I'm still using -O0, and only switch to -Og when I build
pretests (and switch to -O2 when building the released tarballs).
That's because I've found that -Og still makes debugging more
difficult compared to -O0. For example, many values appear as
"optimized out" in the backtraces, which sometimes requires me to go
up the stack very far to find the value. (-Og is actually -O1 with a
couple of more aggressive optimizations disabled, so what I see is not
surprising.)
So the question is how many people who customary debug on the C level
build with -O0, regardless of their compiler version. Could people
who read this please tell what they use?
next prev parent reply other threads:[~2016-12-05 15:47 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
2016-12-05 8:12 ` Colin Baxter
2016-12-05 13:57 ` Ravi Desai
2016-12-05 15:47 ` Eli Zaretskii [this message]
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=8337i2l6ns.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=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.