Hi All;
From the discussion the reason for CONFIG_DEBUG_NOOPT to fail is
already known. Is this true?
Confused and ignorant
Bill Rees
On 9/18/2023 8:55 AM, Tiago Medicci Serrano wrote:
Hi Mike,
NuttX + Espressif's SoCs are intended to be built with optimization
enabled. Otherwise, few
On Mon, Sep 18, 2023 at 12:07 PM Mike Moretti
wrote:
> This is the kind of thing that really should be documented somewhere.
> In bold, "DO NOT TURN OFF OPTIMIZATION because...". Either that or
> disallow it being changed, or make FULLOPT the default for every platform?
Sometimes you really do
Hi Mike,
Yes, I just noticed this option in the Kconfig:
choice
prompt "Optimization Level"
default DEBUG_NOOPT if DEBUG_SYMBOLS
default DEBUG_FULLOPT if !DEBUG_SYMBOLS
Probably this is from the days when GCC for ARM and other chips didn't
work well with debug enable and
Hi Mike;
I haven't seen any screen dump of the error message(s). Are there any logs?
Bill
On 9/18/2023 9:04 AM, Mike Moretti wrote:
This is the kind of thing that really should be documented somewhere.
In bold, "DO NOT TURN OFF OPTIMIZATION because...". Either that or
disallow it being chang
This is the kind of thing that really should be documented somewhere.
In bold, "DO NOT TURN OFF OPTIMIZATION because...". Either that or
disallow it being changed, or make FULLOPT the default for every platform?
I only stumbled upon this because I missed copying one single config
line (the FU
Hi Mike,
NuttX + Espressif's SoCs are intended to be built with optimization
enabled. Otherwise, few practical applications would be possible and you'd
need to reconsider stack sizes, for instance. So, please don't disable
optimization while building practical applications.
Usually, it isn't need
Hi Mike,
I remember facing similar issue with ESP32 in the past.
Because I started using NuttX with ARM chip and in the past the GCC
toolchain has some issue with you are trying to compile debug symbols
(-g) and optimization enabled (-O2) I always disabled optimization
while enabling debugging. (
