From: Euan Harris <euan.harris@citrix.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: Ian.Jackson@eu.citrix.com, xen-devel@lists.xen.org
Subject: Re: [PATCH] libxl/Makefile: Don't optimize debug builds; add macro debugging information
Date: Mon, 1 Dec 2014 11:55:21 +0000 [thread overview]
Message-ID: <20141201115521.GB3731@citrix.com> (raw)
In-Reply-To: <1417434193.29138.14.camel@citrix.com>
On Mon, Dec 01, 2014 at 11:43:13AM +0000, Ian Campbell wrote:
> On Mon, 2014-12-01 at 10:39 +0000, Euan Harris wrote:
> > libxl debug builds are built with optimization level -O1, inherited from
> > the CFLAGS definition in StdGNU.mk. Optimizations confuse the debugger,
> > and the comment justifying -O1 in StdGNU.mk should not apply for a
> > userspace library. Disable optimization by appending -O0 to CFLAGS,
> > which overrides the -O1 flag specified earlier.
>
> I think if this argument applies (I see no reason to disagree) then it
> should apply to the whole of tools/* or at least to tools/lib* and not
> just to libxl. IOW this probably belongs at a higher level somewhere.
Ok, I'll submit a new patch putting it in tools/Rules.mk
> > Also specify -g3, to add macro debugging information which allows
> > gdb to expand macro invocations. This is useful as libxl uses many
> > non-trivial macros.
>
> Useful, I'd never heard of this. Do you know which version of gcc
> introduced it? (AKA do we need to make it part of configure.ac to check
> availability or not).
It's documented in GCC 2.95.3 [1], which is as far back as the online
manuals go.
[1] https://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_2.html#SEC9
> Not sure if you were proposing this change for 4.5 or not.
It would be nice to have, but I was assuming that 4.5 was more or less
closed by now.
Thanks,
Euan
next prev parent reply other threads:[~2014-12-01 11:55 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-01 10:39 [PATCH] libxl/Makefile: Don't optimize debug builds; add macro debugging information Euan Harris
2014-12-01 11:43 ` Ian Campbell
2014-12-01 11:55 ` Euan Harris [this message]
2014-12-01 12:12 ` Ian Campbell
2014-12-01 14:21 ` [PATCH v2] tools/Rules.mk: " Euan Harris
2015-01-08 17:16 ` Ian Campbell
2015-01-12 16:42 ` Ian Campbell
2015-01-13 5:52 ` Wen Congyang
2015-01-13 10:11 ` Ian Campbell
2015-01-13 10:38 ` Wen Congyang
2015-01-13 11:17 ` Wen Congyang
2015-01-13 11:30 ` Ian Campbell
2015-01-15 3:38 ` Wen Congyang
2015-01-15 3:39 ` [PATCH] Fix building error Wen Congyang
2015-01-15 7:57 ` Olaf Hering
2015-01-15 9:04 ` Wen Congyang
2015-01-15 9:21 ` Olaf Hering
2015-01-15 9:28 ` Wen Congyang
2015-01-15 9:33 ` [PATCH v2] " Wen Congyang
2015-01-15 11:26 ` Ian Jackson
2015-01-19 15:23 ` Ian Campbell
2015-01-20 2:21 ` Wen Congyang
2015-01-20 10:18 ` Ian Campbell
2015-01-20 10:39 ` Wen Congyang
2015-01-20 12:47 ` Olaf Hering
2015-01-23 11:34 ` Julien Grall
2015-02-04 15:37 ` Jan Beulich
2015-02-04 15:43 ` Ian Jackson
2015-02-04 16:02 ` Jan Beulich
2015-02-04 16:10 ` Ian Jackson
2015-02-04 16:42 ` Olaf Hering
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=20141201115521.GB3731@citrix.com \
--to=euan.harris@citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=xen-devel@lists.xen.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.
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.