Hi,
i am following the archlinux steps.
https://aur.archlinux.org/packages/msp430-elf-newlib/
So it would come from upstream as well.
Gero
Am 10.09.19 um 11:21 schrieb Juan Ignacio Carrano:
> Hi Gero,
>
> Thanks for tackling this!
>
> On 10/9/19 09:12, Gero Müller wrote:
>> I have no idea about
Hi Gero,
Thanks for tackling this!
On 10/9/19 09:12, Gero Müller wrote:
I have no idea about the performance / feature differences, but I use
the vanilla version and it works fine.
What about the C library/newlib? I know TI also provides newlib. Where
would newlib come from if we used vani
I agree with Marian here! Don't use anything provided by TI :)
On 10.09.19 09:48, Gero Müller wrote:
> Hi!
>
> That's what I meant with philosophy ;-)
>
> And +1 for vanilla from me as well.
>
> Thanks
> Gero
>
> Am 10.09.19 um 09:20 schrieb Marian Buschsieweke:
>> Hi,
>>
>> I'd personally go
Hi!
That's what I meant with philosophy ;-)
And +1 for vanilla from me as well.
Thanks
Gero
Am 10.09.19 um 09:20 schrieb Marian Buschsieweke:
> Hi,
>
> I'd personally go the vanilla version, but not for philosophical reasons. My
> reasons would be:
>
> - More consistent to other toolchains (no
Hi,
I'd personally go the vanilla version, but not for philosophical reasons. My
reasons would be:
- More consistent to other toolchains (no TI specific stuff)
- Does not rely on TI for future updates (in case TI looses interest in
maintaining their on version)
So +1 for vanilla GCC.
Kind reg
Hi!
I am about to update the Dockerfile for testing to include a new version
of msp430-gcc.
We have the choice between a binary version (gcc 8) provded by TI:
http://software-dl.ti.com/msp430/msp430_public_sw/mcu/msp430/MSPGCC/latest/index_FDS.html
and the vanilla upstream gcc 9.2 release.
I h
