All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <tom_rini@mentor.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] sane-toolchain-*: add -g to FULL_OPTIMIZATION to make -dbg packages more usefull
Date: Tue, 1 Mar 2011 12:33:40 -0700	[thread overview]
Message-ID: <4D6D4A14.5010107@mentor.com> (raw)
In-Reply-To: <AANLkTim2CcNy4f_mXGmyeJ9yTfSsXnMFgZTMM6g8sOQ=@mail.gmail.com>

On 03/01/2011 12:14 PM, Khem Raj wrote:
> On Tue, Mar 1, 2011 at 10:29 AM, Tom Rini<tom_rini@mentor.com>  wrote:
>> On 03/01/2011 11:10 AM, Phil Blundell wrote:
>>>
>>> On Tue, 2011-03-01 at 10:54 -0700, Tom Rini wrote:
>>>>
>>>> That's why I'm asking for the -g part to be put into a variable so that
>>>> it can be overriden easily, in all cases, without needing to know the
>>>> special cases (ie glibc).
>>>
>>> Why is glibc special anyway (or, why is the optimization in a
>>> libc-specific conf file)?  It seems a bit bogus that the choice of your
>>> C library would be having such a global impact on the compiler flags for
>>> everything else.
>>
>> There is some odd papering over that's going on to switch out a flag or two
>> (and force -O2) for glibc (but not eglibc).  But my point is that today we
>> have a few special case FULL_OPTIMIZATION_pn-'s and it'd be great to just
>> not have to worry about that when setting the debug level we build with.
>>
>
> May be debugability can be expressed via another variable say
> DEBUG_FLAGS or somesuch which can then we appended to global CFLAGS

With the caveat that I want to control native vs target at different 
levels, yes.

-- 
Tom Rini
Mentor Graphics Corporation



  reply	other threads:[~2011-03-01 19:35 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-01  9:10 [PATCH] sane-toolchain-*: add -g to FULL_OPTIMIZATION to make -dbg packages more usefull Martin Jansa
2011-03-01 11:15 ` Otavio Salvador
2011-03-01 16:07 ` Tom Rini
2011-03-01 17:03   ` Otavio Salvador
2011-03-01 17:39     ` Tom Rini
2011-03-01 17:50       ` Otavio Salvador
2011-03-01 17:54         ` Tom Rini
2011-03-01 18:10           ` Phil Blundell
2011-03-01 18:29             ` Tom Rini
2011-03-01 19:14               ` Khem Raj
2011-03-01 19:33                 ` Tom Rini [this message]
2011-03-01 19:37                   ` Khem Raj
2011-03-01 20:17               ` Phil Blundell
2011-03-02 19:55 ` [PATCHv2] sane-toolchain-*: define DEBUG_FLAGS and add it " Martin Jansa
2011-03-02 22:29   ` Tom Rini
2011-03-02 23:22   ` Khem Raj

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=4D6D4A14.5010107@mentor.com \
    --to=tom_rini@mentor.com \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=raj.khem@gmail.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.
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.