Re: [Mspgcc-users] New MSP430 GCC version release available!

Hello Youssef, Monday, October 19, 2015, 10:11:09 PM, you wrote: > The MSP Debug Stack is an open source. Please refer to this link: > http://www.ti.com/tool/mspds Please see README-BUILD.txt for build > instructions. Yep, I was able to build it on FreeBSD with some small additions to

Re: [Mspgcc-users] New MSP430 GCC version release available!

: Ghannouchi, Youssef; mspgcc-users@lists.sourceforge.net; Miller, Greg Subject: Re: [Mspgcc-users] New MSP430 GCC version release available! > Agenda VR3 (did you remember this very first Linuix-based PDA with > MIPS-based CPU?) Yup, I was involved with the project way back then. >

Re: [Mspgcc-users] New MSP430 GCC version release available!

Hello DJ, Sunday, October 18, 2015, 10:44:10 PM, you wrote: >> To be honest, your (RedHat + TI) way is worst possible one :-( > Worst for your purposes, perhaps. We just have a different goal - a > turnkey custom collection that "just works" for our customers. That > means we normally

Re: [Mspgcc-users] New MSP430 GCC version release available!

> Agenda VR3 (did you remember this very first Linuix-based PDA with > MIPS-based CPU?) Yup, I was involved with the project way back then. > Could you please clear situation with debugging (in separate thread in > mailing list)? Sorry, that's a TI question, they provide the DLLs and SOs for

Re: [Mspgcc-users] New MSP430 GCC version release available!

> To be honest, your (RedHat + TI) way is worst possible one :-( Worst for your purposes, perhaps. We just have a different goal - a turnkey custom collection that "just works" for our customers. That means we normally include things that wouldn't be included in a system package. What you

Re: [Mspgcc-users] New MSP430 GCC version release available!

Hello DJ, Sunday, October 18, 2015, 9:08:34 PM, you wrote: >> Yep, it works, modulo DESTDIR problems, which could be easily patched. > We've always used a separate --prefix for each release (typically > /opt/redhat/msp430-YYMMDD/) so we wouldn't notice. When it is build for system package

Re: [Mspgcc-users] New MSP430 GCC version release available!

> Yep, it works, modulo DESTDIR problems, which could be easily patched. We've always used a separate --prefix for each release (typically /opt/redhat/msp430-YYMMDD/) so we wouldn't notice. > I'm not sure, that toolchain need all these separate tcl and tk > stuff (system already has them!),

Re: [Mspgcc-users] New MSP430 GCC version release available!

Hello DJ, Friday, October 16, 2015, 9:12:20 PM, you wrote: BTW, "gnu89" helps, thank you. > That should be built as part of building gcc/ > so you probably have a problem earlier on that you didn't see in your logs... Nope. It was build here ("root" is sources/tools from tarball):

Re: [Mspgcc-users] New MSP430 GCC version release available!

Hello Lev, Saturday, October 17, 2015, 10:33:35 PM, you wrote: > Makefile in "msp430-elf/libgcc" contains: > > libgcc_topdir = ../.././libgcc/.. > host_subdir = . > gcc_objdir = $(MULTIBUILDTOP)../../$(host_subdir)/gcc > > "host_subdir" is clearly invalid :) Really, This problem

Re: [Mspgcc-users] New MSP430 GCC version release available!

Two questions: 1. Are you cross-building a compiler? I.e. is the host you're building *on* different than the host (not target, which is msp430) you're building *for*? (This is called a "canadian cross" and is much more complicated than a regular cross compiler). (one typically

Re: [Mspgcc-users] New MSP430 GCC version release available!

Hello DJ, Saturday, October 17, 2015, 10:55:52 PM, you wrote: > 1. Are you cross-building a compiler? I.e. is the host you're >building *on* different than the host (not target, which is msp430) >you're building *for*? (This is called a "canadian cross" and is >much more

Re: [Mspgcc-users] New MSP430 GCC version release available!

On 10/17/2015 03:35 PM, Lev Serebryakov wrote: > Hello DJ, > > Saturday, October 17, 2015, 10:55:52 PM, you wrote: > > >> 1. Are you cross-building a compiler? I.e. is the host you're >>building *on* different than the host (not target, which is msp430) >>you're building *for*? (This

Re: [Mspgcc-users] New MSP430 GCC version release available!

Hello DJ, Friday, October 16, 2015, 9:12:20 PM, you wrote: > That should be built as part of building gcc/ > so you probably have a problem earlier on that you didn't see in your logs... Other problem: tcl doesn't respect DESTDIR setting, so whole package could not be properly "staged" for

Re: [Mspgcc-users] New MSP430 GCC version release available!

> It is clang 3.4.1, and I don't want to install gcc, if it is possible to > avoid with some "simple" patch :) IIRC there's an option in clang to use the old semantics (-std=gnu89). --

Re: [Mspgcc-users] New MSP430 GCC version release available!

That should be built as part of building gcc/ so you probably have a problem earlier on that you didn't see in your logs... -- ___ Mspgcc-users mailing list

Re: [Mspgcc-users] New MSP430 GCC version release available!

Hello DJ, Friday, October 16, 2015, 1:03:06 AM, you wrote: > You're probably running into a common problem with "static inline" vs > "extern inline" - the semantics of those changed with the recent C > standards, so not all compilers do the same thing. I assume you're > not using GCC? It is

Re: [Mspgcc-users] New MSP430 GCC version release available!

Hello DJ, Friday, October 16, 2015, 1:03:06 AM, you wrote: > You're probably running into a common problem with "static inline" vs > "extern inline" - the semantics of those changed with the recent C > standards, so not all compilers do the same thing. I assume you're > not using GCC? Ok,

Re: [Mspgcc-users] New MSP430 GCC version release available!

On 20.09.2015 19:17, Ghannouchi, Youssef wrote: I could not build this version on FreeBSD. It could not link "sim" (multiple symbol definitions): cc -DHAVE_CONFIG_H -DPROFILE=1 -DWITH_PROFILE=-1 -DWITH_DEFAULT_ALIGNMENT=STRICT_ALIGNMENT -DWITH_TARGET_BYTE_ORDER=LITTLE_ENDIAN

Re: [Mspgcc-users] New MSP430 GCC version release available!

You're probably running into a common problem with "static inline" vs "extern inline" - the semantics of those changed with the recent C standards, so not all compilers do the same thing. I assume you're not using GCC?

Re: [Mspgcc-users] New MSP430 GCC version release available!

On 09/20/2015 11:17 AM, Ghannouchi, Youssef wrote: > Hello GCC-enthusiasts, We are pleased to announce a new stand-alone & > open source release (v3.5.0.0) of MSP430 GCC I don't see any mention of a fix to the compiler saving more registers than required when entering an interrupt routine. Its

Re: [Mspgcc-users] New MSP430 GCC version release available!

Thanks for the update. Please note the mspgcc-users mailing list has historically had a maximum message length of 40 kB, and does not allow attachments. A couple of your messages have exceeded this limit and I've passed them through, but that's why you may see delays on your postings. Also may

Re: [Mspgcc-users] New MSP430 GCC version release available!

Hello GCC-enthusiasts, I have seen some questions and feedbacks related to the email below and I would like to clarify some points. 1. Versioning a. The MSP430 GCC standalone package is container which has its own version. The latest version is v3.5.0.0. Please refer to versioning

Re: [Mspgcc-users] New MSP430 GCC version release available!

On 21/09/15 06:31, Mark Rages wrote: > On Sun, Sep 20, 2015 at 10:17 AM, Ghannouchi, Youssef > wrote: >> Hello GCC-enthusiasts, We are pleased to announce a new stand-alone >> & open source release (v3.5.0.0) of MSP430 GCC available for >> download >>

[Mspgcc-users] New MSP430 GCC version release available!

Hello GCC-enthusiasts, We are pleased to announce a new stand-alone & open source release (v3.5.0.0) of MSP430 GCC available for download here! The stand-alone package includes all binaries, the

Re: [Mspgcc-users] New MSP430 GCC version release available!

On Sun, Sep 20, 2015 at 10:17 AM, Ghannouchi, Youssef wrote: > Hello GCC-enthusiasts, > We are pleased to announce a new stand-alone & open source release (v3.5.0.0) > of MSP430 GCC available for download >