From: Ian Jackson <Ian.Jackson@eu.citrix.com>
To: George Dunlap <george.dunlap@citrix.com>
Cc: Wei Liu <wei.liu2@citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
Doug Goldstein <cardoe@cardoe.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: [PATCH 2/2] tools: detect appropriate debug optimization level
Date: Wed, 6 Apr 2016 15:57:57 +0100 [thread overview]
Message-ID: <22277.9205.201038.354110@mariner.uk.xensource.com> (raw)
In-Reply-To: <CAFLBxZbnKbU68HsCfh-adCeGAVzvs=_DSvkxZgch1G-ON5vuMg@mail.gmail.com>
George Dunlap writes ("Re: [Xen-devel] [PATCH 2/2] tools: detect appropriate debug optimization level"):
> On Wed, Apr 6, 2016 at 3:07 PM, Ian Jackson <Ian.Jackson@eu.citrix.com> wrote:
> > Doug, would you like to, for now, propose a patch that uses -Og if it
> > is available, but otherwise falls back to -O0 ? NB that if
> > convenient, this can be done simply by always specifying -O0 and
> > putting -Og after it if it is supported.
>
> I agree that it would be good to include specific bugs that this
> fixes. Presuming that they are as described (compilation errors for
> reasonable setups), I continue to think that making things compile for
> everyone is more important than making them debuggable via gdb for
> people running compilers that don't support -Og.
I think making debug builds debuggable for people with non-broken
compilers is more important than making debug builds build for people
with broken compilers.
(Under some unstated but I think reasonable, and rebuttable,
assumptions about the sizes of the two sets of people.)
Non-debug builds are, after all, not affected by any of this.
Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-04-06 14:57 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-08 2:23 [PATCH 1/2] libxl: ensure var is inited in libxl__domain_firmware Doug Goldstein
2016-03-08 2:23 ` [PATCH 2/2] tools: detect appropriate debug optimization level Doug Goldstein
2016-03-08 15:38 ` Wei Liu
2016-03-08 16:34 ` Doug Goldstein
2016-03-08 16:50 ` Wei Liu
2016-03-16 19:14 ` Doug Goldstein
2016-03-28 15:01 ` Doug Goldstein
2016-03-29 11:44 ` George Dunlap
2016-03-29 17:21 ` Doug Goldstein
2016-03-30 9:52 ` George Dunlap
2016-03-30 16:00 ` Ian Jackson
2016-03-30 16:11 ` Ian Jackson
2016-03-30 16:20 ` Doug Goldstein
2016-03-31 8:24 ` George Dunlap
2016-04-06 14:07 ` Ian Jackson
2016-04-06 14:34 ` George Dunlap
2016-04-06 14:57 ` Ian Jackson [this message]
2016-03-08 15:38 ` [PATCH 1/2] libxl: ensure var is inited in libxl__domain_firmware Wei Liu
2016-03-10 15:13 ` Doug Goldstein
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=22277.9205.201038.354110@mariner.uk.xensource.com \
--to=ian.jackson@eu.citrix.com \
--cc=cardoe@cardoe.com \
--cc=george.dunlap@citrix.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=wei.liu2@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 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 NNTP newsgroup(s).