Hi,
I've been using the 'old' compiler last maintained by P.Bigot(many
thanks to him).
Now I need to make some changes and have installed the new msp430-gcc
6.2.1.16 under OpenSuse 42.1
My small project under the 'old' compiler produced a .text size of 1392
bytes, the 'new' compiler makes a .te
On 03/03/2017 05:20 AM, Bob von Knobloch wrote:
> As far as I can see, the 'bloat' is in library funcs (newlib?).
> Why the 50% increase and can I mitigate this somehow?
> Regards,
> Bob von Knobloch.
>
Hard to say without seeing the code. Have you looked at the resulting
file using objdump? If n
Op 03/03/2017 om 02:29 PM schreef David W. Schultz:
> On 03/03/2017 05:20 AM, Bob von Knobloch wrote:
>> As far as I can see, the 'bloat' is in library funcs (newlib?).
>> Why the 50% increase and can I mitigate this somehow?
>> Regards,
>> Bob von Knobloch.
>>
> Hard to say without seeing the cod
Hi Bob,
> As far as I can see, the 'bloat' is in library funcs (newlib?).
If the bloat is indeed in the library funcs why not just compile with
gcc and then link in the old, mspcc C library instead of newlib ?
Cheers
Nick
On 03/03/17 14:29, David W. Schultz wrote:
> On 03/03/2017 05:20 AM, Bob von Knobloch wrote:
>> As far as I can see, the 'bloat' is in library funcs (newlib?).
>> Why the 50% increase and can I mitigate this somehow?
>> Regards,
>> Bob von Knobloch.
>>
>
> Hard to say without seeing the code. Have
I "thought" something like that was happening to me, but didn't follow
through. For operating system compatibility reasons I decided a while back
to just keep using the legacy one, it works well for the simple things that
I do, also some tool I downloaded from TI was a terrible bloat itself in
the
This has come up before, and here's what's going on... the new
msp430-elf-gcc includes all the code required by the standard, partly
because... well, standards... and partly so that the testsuite can test
everything. The old msp-gcc made lots of assumptions about how the
compiler would actually b
I think it's pretty unlikely msp430-libc would work with upstream gcc,
though I admit I haven't tried it.
http://pabigot.github.io/bsp430/msp430elf.html has some outdated
suggestions for building customized newlib and trimming out functionality
that isn't needed.
Glad to know people are still get
long story short, one of my first mspgcc worked because of a bug, when
later either the bug was fixed in mspgcc or fedora (don't recall which one
exactly), things broke all over, code unusable, docs I had share were
wrong.
But by then I was already married to the MSP430 chips, so I stayed for the
r