On 19/02/15 11:21, Arvind Padmanabhan wrote:
> Thanks to both Eric and David for their inputs. Indeed, although "-Os
> -g" worked for me, it was difficult to set breakpoints at the right
> places. At times I had to resort single-stepping in assembly to get
> what I wanted.
>
> It is nice David poi
From: David Brown
To: mspgcc-users@lists.sourceforge.net
Sent: Thursday, 19 February 2015, 13:43
Subject: Re: [Mspgcc-users] Code does not fit in ROM with mspgcc but fits with
CCS compiler
On 19/02/15 06:10, Arvind Padmanabhan wrote:
> Hi Folks,
>
> My friend has Code Composer Studio (CCS
Hi Arvind,
I completely agree with the comment from David, I would also recommend do
use use "-g -Os" by default and "-g -O1" if you struggle while debugging.
Regarding the binary size, I have recently played around with the TI/RedHat
GCC release and the results are IMO really really bad (standar
On 19/02/15 06:10, Arvind Padmanabhan wrote:
> Hi Folks,
>
> My friend has Code Composer Studio (CCS) license. He compiled without
> debugging and no optimization. Code size (ROM) is only 35 KB. This is
> good for MSP430G2955 that has 56 KB of Flash.
There is no standard for how much optimisation
have you tried, -g -Os
or -ggdb -Os
that is what I use to debug size optimized code.
works fine.
figuring out what the code is doing can be a bit tricky but it can be done.
On Wed, Feb 18, 2015 at 9:10 PM, Arvind Padmanabhan <
arvindpadmanab...@yahoo.com.sg> wrote:
> Hi Folks,
>
> My friend
