From: Stefan Weil <weil@mail.berlios.de>
To: Brad <brad@comstyle.com>
Cc: Gerd Hoffmann <kraxel@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Only build with -g CFLAGS/LDFLAGS if using --enable-debug and add --optflags.
Date: Wed, 07 Sep 2011 23:31:38 +0200 [thread overview]
Message-ID: <4E67E2BA.6070402@mail.berlios.de> (raw)
In-Reply-To: <1315326651.9576.8.camel@Nokia-N900>
Am 06.09.2011 18:30, schrieb Brad:
> ----- Original message -----
>> On 09/06/11 10:02, Brad wrote:
>>> Only build with -g CFLAGS/LDFLAGS if using --enable-debug.
>>> Add --optflags to allow overriding the default optimization
>>> level added to CFLAGS.
>>>
>>> This is a first draft of coming up with a patch I could potentially
>>> push upstream based on much cruder local patches to do something
>>> similar. I'm trying to eliminate having to patch the configure
>>> script.
>>
>> You don't have to. You can just run 'make CFLAGS="$optflags"' to
>> override the defaults. Nevertheless having optflags would be nice as
>> you don't have to type this for each make run then.
>
> I do when its unconditionally on the commandline either way. If the
> configure scipt didnt put it their if CFLAGS wasnt empty it wouldnt be
> an issue.
>
>> I don't think we should mess with the -g flag. It should stay enabled
>> by default, so you can easily get a useful stacktrace out of a core
>> without having to rebuild with debug info first.
>
> I dont care what the default is as long as I can disable it without
> patching.
I'm sorry but I still don't understand why you want this patch.
It's already possible to run the compiler with or without -g
and with any optimization you want: make CFLAGS="-O1",
make CFLAGS=-g (my favourite), make CFLAGS="-O0", ...
There must be a really good reason for new options like
--optflags. Is this flag some kind of standard which is widely
used (like CFLAGS)? If it isn't, users won't know it, so they
won't use it, so it is useless.
Regards,
Stefan Weil
next prev parent reply other threads:[~2011-09-07 21:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-06 8:02 [Qemu-devel] [PATCH] Only build with -g CFLAGS/LDFLAGS if using --enable-debug and add --optflags Brad
2011-09-06 9:26 ` Peter Maydell
2011-09-06 10:19 ` Gerd Hoffmann
2011-09-06 16:30 ` Brad
2011-09-07 10:54 ` Juan Quintela
2011-09-07 19:42 ` Blue Swirl
2011-09-07 21:31 ` Stefan Weil [this message]
2011-09-06 10:35 ` Peter Maydell
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=4E67E2BA.6070402@mail.berlios.de \
--to=weil@mail.berlios.de \
--cc=brad@comstyle.com \
--cc=kraxel@redhat.com \
--cc=qemu-devel@nongnu.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).