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

[Lev Serebryakov]

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
Makefiles (adding new $(PLATFORM) branch). Sources were compiled without any
problems!

> I will double check the gdb_agent_console license and let you know asap.
  Thank you! Looks like it is last component to build full-featured MSP430
 developemnt stack for yet another host platform :)

-- 
Best regards,
 Levmailto:l...@serebryakov.spb.ru


--
___
Mspgcc-users mailing list
Mspgcc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mspgcc-users

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

[Ghannouchi, Youssef]

Hello Lev,

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.

I will double check the gdb_agent_console license and let you know asap.

Best regards,
Youssef Ghannouchi


Texas Instruments Deutschland GmbH, Haggertystr. 1, D-85356 Freising. 
Amtsgericht M?nchen HRB 40960. Gesch?ftsf?hrer: Dr. Wolfram Tietscher. 
Vorsitzender des Aufsichtsrates: Andreas Schwaiger

-Original Message-
From: DJ Delorie [mailto:d...@redhat.com]
Sent: Monday, October 19, 2015 12:21 AM
To: Lev Serebryakov
Cc: 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.

>  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 that.


--
___
Mspgcc-users mailing list
Mspgcc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mspgcc-users

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

[DJ Delorie]

> 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 that.

--
___
Mspgcc-users mailing list
Mspgcc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mspgcc-users

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

[Lev Serebryakov]

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 include things that wouldn't be included in a system
> package.
  Yep, because my goal is to do system package for yet another system :)

> And BTW I know all about packaging rules, I do after all work for Red
> Hat, we have a distro or two ourselves :-)
 :-)

 Anyway, I'm pleased, that it could be built on BSD system with clang
compiler almost flawlessly. I've remember days, when such package for Agenda
VR3 (did you remember this very first Linuix-based PDA with MIPS-based CPU?)
was hopeless to built anywhere but one distributive of Linux!

 Could you please clear situation with debugging (in separate thread in
mailing list)?

-- 
Best regards,
 Levmailto:l...@serebryakov.spb.ru


--
___
Mspgcc-users mailing list
Mspgcc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mspgcc-users

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

[DJ Delorie]

>   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 want is an "upstream" collection, broken down by packages,
with the latest greatest of each package.  Over time, the upstream
releases with msp430 support will happen and allow that.  Often we do
releases for customers that can't go upstream right away (usually
because the chips are still NDA, which is obviously not the case for
MSP430 ;) so our workflow is geared towards self-sufficiency.

And BTW I know all about packaging rules, I do after all work for Red
Hat, we have a distro or two ourselves :-)

--
___
Mspgcc-users mailing list
Mspgcc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mspgcc-users

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

[Lev Serebryakov]

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 (like RPM, DEB or Gentoo Portage) it
should has proper (final) prefix (like /usr/local/ti-gcc-${version}) but
"make install" must place it in "stage" directory for packaging. It is
typically done with DESTDIR (so, destination becomes $(DESTDIR)$(PREFIX),
not just $(PREFIX), and it is supported by all autotools/libtools
projects.

  But, as I say, it is very minor problem, as it could be easily patched by
 me (package maintainer), it is only 3KiB of patches, which is negligible :)

>>  I'm not sure, that toolchain need all these separate tcl and tk
>>  stuff (system already has them!), but it is better than nothing
>>  (though, very Windows-like!).
> No surprise, we support windows :-)
  Yep, I know :)

> And not all Unix-y systems have those, either.  Even Linux is the user
> hasn't chosen to install them yet (which is commonly the case).
 Yes. But typical *IX way is to use package managers for each separate
component. Ideally, all this stuff, which is not MSP430-dependand (build for
host and could be used by many oither packages and programs in same system):

  libgmp
  libmpfr
  zlib
  tcl
  tk
  itlc

 should be mentioned in requirements and installed by means of system
 package manager (rmp, apt-get, Gentoo Portages, NetBSD pkg-src, FreeBSD
 ports, etc). For example, msp430 package contains old versions of gmp and mpfr.
 Are you sure, that packaged versions doesnt have bugs and, may be, even
 security ones?

 IMHO, ideal source-based releasing of toolcahin looks like this:

  (1) List of requirements, like "libgmp > 5.1.0, mprf > 3.1.0" and so on.
  NO SOURCES of all these libraries should be provided, as they are
  SEPARATE projects.

  (2) Links to some official binutils / gcc / gdb RELEASE tarballs (gcc 4.9.1,
  for example).

  (3) Minimal patches for (2), which is msp430-dependant.

  (4) System headers, linker scripts, stuff like this.

  (5) Some script to build toolchain from all parts above
 (unpack-patch-configure-build in proper order).

  It is ideal situation, which allows to package your work for differnet
 distributives in most natural way.

  Second-to-best way is like ARM does: script, which, really, allows to
 build toolchain with system libraries (but binutls/gcc/gdb are packaged as
 whole).

  To be honest, your (RedHat + TI) way is worst possible one :-(

-- 
Best regards,
 Levmailto:l...@serebryakov.spb.ru


--
___
Mspgcc-users mailing list
Mspgcc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mspgcc-users

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

[DJ Delorie]

>  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!), but it is better than nothing
>  (though, very Windows-like!).

No surprise, we support windows :-)

And not all Unix-y systems have those, either.  Even Linux is the user
hasn't chosen to install them yet (which is commonly the case).

--
___
Mspgcc-users mailing list
Mspgcc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mspgcc-users

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

[Lev Serebryakov]

Hello Lev,

Saturday, October 17, 2015, 11:35:14 PM, you wrote:

>> 2. Are you building in the source tree?  If so, that is not supported,
>>you must always build in a separate (empty) directory.
>   Oh, it looks like my error. I'm trying to build out-of-tree now.
 Yep, it works, modulo DESTDIR problems, which could be easily patched.
 I'm not sure, that toolchain need all these separate tcl and tk stuff (system
 already has them!), but it is better than nothing (though, very
 Windows-like!).

-- 
Best regards,
 Levmailto:l...@serebryakov.spb.ru


--
___
Mspgcc-users mailing list
Mspgcc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mspgcc-users

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

[Lev Serebryakov]

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 package building, "tcl" try to
install itself directly to $(PREFIX).

 Same problem exists in ictl/* and tk.

 Also, "libgloss" doesn't respect DESTDIR.

 It could be patched, though.

-- 
Best regards,
 Levmailto:l...@serebryakov.spb.ru


--
___
Mspgcc-users mailing list
Mspgcc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mspgcc-users

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

[David W. Schultz]

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 is called a "canadian cross" and is
>>much more complicated than a regular cross compiler).
>   Nope. *host* and *build* are both the same.
> 
>>(one typically cross-builds by accident by specifying --build or
>>--host but not both, or by specifying both but not having them the
>>same.)
> 
>> 2. Are you building in the source tree?  If so, that is not supported,
>>you must always build in a separate (empty) directory.
>   Oh, it looks like my error. I'm trying to build out-of-tree now.
> 

I built the TI version from source a while back. I don't recall exactly
what I did but fortunately, it remembers.

I created the directory ti/gcc/sources/tools/msp430-build

The config.log reveals that I ran from that directory:

 ../configure --target=msp430-elf --program-prefix=msp430-elf --with-newlib

gcc has a lot of build options and by default it is going to build a lot
of stuff you have no interest in. Taking a long time to do it. I also
played with building a version for the 68000 with:

../configure --target=m68k-elf --with-arch=m68k --program-prefix=m68k-
--enable-languages=c --disable-libmudflap --disable-libssp
--disable-libgomp --disable-libstdcxx-pch --disable-threads

And since that was in its own build directory, it didn't conflict at all
with the msp430 build. It is almost certain that there is an optimal set
of options for the task but I don't know what they are.


-- 
David W. Schultz
http://home.earthlink.net/~david.schultz
Returned for Regrooving



--
___
Mspgcc-users mailing list
Mspgcc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mspgcc-users

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

[Lev Serebryakov]

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 complicated than a regular cross compiler).
  Nope. *host* and *build* are both the same.

>(one typically cross-builds by accident by specifying --build or
>--host but not both, or by specifying both but not having them the
>same.)

> 2. Are you building in the source tree?  If so, that is not supported,
>you must always build in a separate (empty) directory.
  Oh, it looks like my error. I'm trying to build out-of-tree now.

-- 
Best regards,
 Levmailto:l...@serebryakov.spb.ru


--
___
Mspgcc-users mailing list
Mspgcc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mspgcc-users

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

[DJ Delorie]

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 cross-builds by accident by specifying --build or
   --host but not both, or by specifying both but not having them the
   same.)

2. Are you building in the source tree?  If so, that is not supported,
   you must always build in a separate (empty) directory.

--
___
Mspgcc-users mailing list
Mspgcc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mspgcc-users

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

[Lev Serebryakov]

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 exists in each "msp430/**/libgcc/Makefile".

-- 
Best regards,
 Levmailto:l...@serebryakov.spb.ru


--
___
Mspgcc-users mailing list
Mspgcc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mspgcc-users

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

[Lev Serebryakov]

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):

"host-amd64-portbld-freebsd10.2/gcc/libgcc.mvars"

 But later build try to find it here:

gmake[3]: Entering directory 
'/usr/home/lev/FreeBSD/ports/devel/gcc-msp430-ti-toolchain/work/sources/tools/msp430-elf/libgcc'
Makefile:165: ../.././gcc/libgcc.mvars: No such file or directory

 Which is (again, path is trimmed):

"msp430-elf/libgcc/../.././gcc" -> "gcc", which is not
"host-amd64-portbld-freebsd10.2/gcc/libgcc.mvars" :)

 So, it looks like everyhting but msp430-elf/libgcc is built out-of-tree and
this library is build in-tree and here are some problems with that.

 Makefile in "msp430-elf/libgcc" contains:


libgcc_topdir = ../.././libgcc/..
host_subdir = .

gcc_objdir = $(MULTIBUILDTOP)../../$(host_subdir)/gcc


  "host_subdir" is clearly invalid :)

-- 
Best regards,
 Levmailto:l...@serebryakov.spb.ru


--
___
Mspgcc-users mailing list
Mspgcc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mspgcc-users

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

[DJ Delorie]

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
Mspgcc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mspgcc-users

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

[Lev Serebryakov]

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, tinkering with "extern" and "inline" helps, but now I have more serious
problem:

 gmake[3]: Leaving directory 
'/usr/home/lev/FreeBSD/ports/devel/gcc-msp430-ti-toolchain/work/sources/tools/host-amd64-portbld-freebsd10.2/gdb'
Checking multilib configuration for libgcc...
mkdir msp430-elf
mkdir msp430-elf/libgcc
Configuring in msp430-elf/libgcc
[SKIPPED]
configure: updating cache ./config.cache
configure: creating ./config.status
config.status: creating Makefile
config.status: creating auto-target.h
config.status: linking ../../.././libgcc/enable-execute-stack-empty.c to 
enable-execute-stack.c
config.status: linking ../../.././libgcc/unwind-generic.h to unwind.h
config.status: linking ../../.././libgcc/config/no-unwind.h to 
md-unwind-support.h
config.status: linking ../../.././libgcc/config/no-sfp-machine.h to 
sfp-machine.h
config.status: linking ../../.././libgcc/gthr-single.h to gthr-default.h
config.status: executing default commands
Adding multilib support to Makefile in ../../.././libgcc
with_multisubdir=large
gmake[3]: Entering directory 
'/usr/home/lev/FreeBSD/ports/devel/gcc-msp430-ti-toolchain/work/sources/tools/msp430-elf/libgcc'
Makefile:165: ../.././gcc/libgcc.mvars: No such file or directory
gmake[3]: *** No rule to make target '../.././gcc/libgcc.mvars'.  Stop.
gmake[3]: Leaving directory 
'/usr/home/lev/FreeBSD/ports/devel/gcc-msp430-ti-toolchain/work/sources/tools/msp430-elf/libgcc'
Makefile:17333: recipe for target 'all-target-libgcc' failed
gmake[2]: *** [all-target-libgcc] Error 2
gmake[2]: Leaving directory 
'/usr/home/lev/FreeBSD/ports/devel/gcc-msp430-ti-toolchain/work/sources/tools'
Makefile:860: recipe for target 'all' failed



-- 
Best regards,
 Levmailto:l...@serebryakov.spb.ru


--
___
Mspgcc-users mailing list
Mspgcc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mspgcc-users

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

[DJ Delorie]

>  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).

--
___
Mspgcc-users mailing list
Mspgcc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mspgcc-users

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

[Lev Serebryakov]

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 clang 3.4.1, and I don't want to install gcc, if it is possible to
avoid with some "simple" patch :)

-- 
Best regards,
 Levmailto:l...@serebryakov.spb.ru


--
___
Mspgcc-users mailing list
Mspgcc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mspgcc-users

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

[DJ Delorie]

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?

--
___
Mspgcc-users mailing list
Mspgcc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mspgcc-users

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

[Lev Serebryakov]

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 -DDEFAULT_INLINE=0
   -I. -I../../.././sim/msp430 -I../common
-I../../.././sim/msp430/../common -I../../include
-I../../.././sim/msp430/../../include -I../../bfd
-I../../.././sim/msp430/../../bfd -I../../opcodes
-I../../.././sim/msp430/../../opcodes  -O2 -pipe  -DLIBICONV_PLUG
-fstack-protector -fno-strict-aliasing -fstack-protector -o run \
  nrun.o libsim.a ../../bfd/libbfd.a ../../opcodes/libopcodes.a
../../libiberty/libiberty.a -lz
libsim.a(sim-info.o): In function `sim_addr_range_hit_p':
../../.././sim/msp430/../common/sim-info.c:(.text+0x0): multiple
definition of `sim_addr_range_hit_p'
nrun.o:../../.././sim/msp430/../common/nrun.c:(.text+0x0): first defined
here
libsim.a(sim-module.o): In function `sim_addr_range_hit_p':
../../.././sim/msp430/../common/sim-module.c:(.text+0x0): multiple
definition of `sim_addr_range_hit_p'
nrun.o:../../.././sim/msp430/../common/nrun.c:(.text+0x0): first defined
here
libsim.a(sim-options.o): In function `sim_addr_range_hit_p':
../../.././sim/msp430/../common/sim-options.c:(.text+0x0): multiple
definition of `sim_addr_range_hit_p'
nrun.o:../../.././sim/msp430/../common/nrun.c:(.text+0x0): first defined
here
libsim.a(sim-profile.o): In function `sim_addr_range_hit_p':
../../.././sim/msp430/../common/sim-profile.c:(.text+0x0): multiple
definition of `sim_addr_range_hit_p'
nrun.o:../../.././sim/msp430/../common/nrun.c:(.text+0x0): first defined
here
libsim.a(sim-signal.o): In function `sim_addr_range_hit_p':
../../.././sim/msp430/../common/sim-signal.c:(.text+0x0): multiple
definition of `sim_addr_range_hit_p'
nrun.o:../../.././sim/msp430/../common/nrun.c:(.text+0x0): first defined
here
libsim.a(sim-trace.o): In function `sim_addr_range_hit_p':
../../.././sim/msp430/../common/sim-trace.c:(.text+0x0): multiple
definition of `sim_addr_range_hit_p'
nrun.o:../../.././sim/msp430/../common/nrun.c:(.text+0x0): first defined
here
libsim.a(sim-utils.o): In function `sim_addr_range_hit_p':
../../.././sim/msp430/../common/sim-utils.c:(.text+0x0): multiple
definition of `sim_addr_range_hit_p'
nrun.o:../../.././sim/msp430/../common/nrun.c:(.text+0x0): first defined
here
libsim.a(msp430-sim.o): In function `sim_addr_range_hit_p':
../../.././sim/msp430/msp430-sim.c:(.text+0x0): multiple definition of
`sim_addr_range_hit_p'
nrun.o:../../.././sim/msp430/../common/nrun.c:(.text+0x0): first defined
here
libsim.a(sim-cpu.o): In function `sim_addr_range_hit_p':
../../.././sim/msp430/../common/sim-cpu.c:(.text+0x0): multiple
definition of `sim_addr_range_hit_p'
nrun.o:../../.././sim/msp430/../common/nrun.c:(.text+0x0): first defined
here
libsim.a(sim-engine.o): In function `sim_addr_range_hit_p':
../../.././sim/msp430/../common/sim-engine.c:(.text+0x0): multiple
definition of `sim_addr_range_hit_p'
nrun.o:../../.././sim/msp430/../common/nrun.c:(.text+0x0): first defined
here
libsim.a(sim-hload.o): In function `sim_addr_range_hit_p':
../../.././sim/msp430/../common/sim-hload.c:(.text+0x0): multiple
definition of `sim_addr_range_hit_p'
nrun.o:../../.././sim/msp430/../common/nrun.c:(.text+0x0): first defined
here
libsim.a(sim-hrw.o): In function `sim_addr_range_hit_p':
../../.././sim/msp430/../common/sim-hrw.c:(.text+0x0): multiple
definition of `sim_addr_range_hit_p'
nrun.o:../../.././sim/msp430/../common/nrun.c:(.text+0x0): first defined
here
libsim.a(sim-reason.o): In function `sim_addr_range_hit_p':
../../.././sim/msp430/../common/sim-reason.c:(.text+0x0): multiple
definition of `sim_addr_range_hit_p'
nrun.o:../../.././sim/msp430/../common/nrun.c:(.text+0x0): first defined
here
libsim.a(sim-resume.o): In function `sim_addr_range_hit_p':
../../.././sim/msp430/../common/sim-resume.c:(.text+0x0): multiple
definition of `sim_addr_range_hit_p'
nrun.o:../../.././sim/msp430/../common/nrun.c:(.text+0x0): first defined
here
libsim.a(sim-stop.o): In function `sim_addr_range_hit_p':
../../.././sim/msp430/../common/sim-stop.c:(.text+0x0): multiple
definition of `sim_addr_range_hit_p'
nrun.o:../../.././sim/msp430/../common/nrun.c:(.text+0x0): first defined
here
libsim.a(sim-command.o): In function `sim_addr_range_hit_p':
../../.././sim/msp430/../common/sim-command.c:(.text+0x0): multiple
definition of `sim_addr_range_hit_p'
nrun.o:../../.././sim/msp430/../common/nrun.c:(.text+0x0): first defined
here
libsim.a(sim-config.o): In function `sim_addr_range_hit_p':
../../.././sim/msp430/../common/sim-config.c:(.text+0x0): multiple
definition of `sim_addr_range_hit_p'
nrun.o:../../.././sim/msp430/../common/nrun.c:(.text+0x0): first defined
here
libsim.a(sim-core.o): In function `sim_addr_range_hit_p':
../../.././sim/msp430/../common/sim-core.c:(.text+0x0): multiple
definition of `sim_addr_range_hit_p'
nrun.o:../../.././sim/msp430

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

[David W. Schultz]

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 like it completely
forgot about the EABI.

-- 
David W. Schultz
http://home.earthlink.net/~david.schultz
Returned for Regrooving



--
___
Mspgcc-users mailing list
Mspgcc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mspgcc-users

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

[Peter Bigot]

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 I suggest TI make the effort to rebase the next compiler release
on gcc 5.2 since that was released last July (three months after 5.1).  I
don't know if they have a 5.3 coming up before you expect your version to
be out, but you might want to coordinate with the GNU folks on that.

On Fri, Sep 25, 2015 at 3:07 AM, Ghannouchi, Youssef 
wrote:

> 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 scheme
> for the package described below.
>
> b.  The MSP430 GCC standalone package has a software manifest included
> in the package (attached also GCC_14r1_manifest.pdf) which describe in
> details all sub components and their version.
>
> c.   The package contains:
>
>i.  GGC
> 4.9.1
>
>  ii.  GDB
> 7.5.0
>
> iii.
> binutils 2.23
>
>iv.  Tcl
> 8.4.1
>
>  v.
> MSP430 Debug Stack 3.5.1.1
>
>vi.  MSP430
> Support Files 1.173
>
>   vii.  MSP430
> GDB Agent 6.0.14.5
>
>
>
> 2.   MSP430 GCC 5.1
>
> a.   The MSP430 GCC standalone package v3.5.0.0 uses the GCC 4.9.1.
> The purpose of this package was to give a quick update on GCC compiler
> including the latest bug fixes to allow our customers continuing their
> development easily.
>
> b.  We are working on preparing an MSP430 compiler based on GCC 5.1.
> This package is expected to be released by end of this year. I will keep
> informed.
>
>
> Thank you for the valuable feedbacks, we really appreciate it.
> We would like to continue improving MSP430 GCC offer, so please feel free
> to send any suggestions or recommendations.
> For better tracking and handling please use TI e2e community<
> https://e2e.ti.com/> to submit your requests.
>
> Best regards,
> 
> Youssef Ghannouchi
> Product Manager - Texas Instruments Inc.
>
>
>
> Texas Instruments Deutschland GmbH, Haggertystr. 1, D-85356 Freising.
> Amtsgericht München HRB 40960. Geschäftsführer: Dr. Wolfram Tietscher.
> Vorsitzender des Aufsichtsrates: Andreas Schwaiger
>
>
> From: Ghannouchi, Youssef
> Sent: Sunday, September 20, 2015 6:18 PM
> To: 'GCC for MSP430 - http://mspgcc.sf.net'
> Cc: 'Brendan Conoboy (b...@redhat.com)'; Miller, Greg; Mitnacht, Thomas
> Subject: 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<
> http://software-dl.ti.com/msp430/msp430_public_sw/mcu/msp430/MSPGCC/3_05_00_00/index_FDS.html
> >!
> The stand-alone package includes all binaries, the source code and MSP430
> device specific support files.
> The MSP430 GCC build is also available in CCSv6 App Center on all
> platforms (Windows, Linux and Mac OSX).
>
>
> · Highlights
>
> o   MSP430 GCC compiler latest build (14r1-364)
>
> o   MSP430 GCC for Mac OS X (beta release)
>
> o   A new MSP430 GCC User Guide
>
>
>
> · Package Content
>
> o   Full Packages
>
> §  msp430-gcc-full-linux-installer-3.5.0.0.run: MSP430 GCC Linux installer
> incl. support files and debug stack and USB drivers - apply chmod x before
> executing the package
>
> §  msp430-gcc-full-osx-installer-3.5.0.0-beta.zip: MSP430 GCC Mac OS X
> installer incl. support files and debug stack and USB drivers - beta release
>
> §  msp430-gcc-full-windows-installer-3.5.0.0.exe: MSP430 GCC Windows
> installer incl. support files and debug stack and USB drivers
>
> o   Compiler Only Packages
>
> §  msp430-gcc-linux-installer-3.5.0.0.run: MSP430 GCC Linux installer -
> compiler only - apply chmod x before executing the package
>
> §  msp430-gcc-osx-installer-3.5.0.0-beta.zip: MSP430 GCC Mac OS X
> installer - compiler only - beta release
>
> §  msp430-gcc-windows-installer-3.5.0.0.exe: MSP430 GCC Windows installer
> - compiler only
>
> o   MSP430 Support Files
>
> §  msp430-gcc-support-files.zip: MSP430 Header and linker Files
>
> o   MSP430 GCC Sources files
>
> §  msp430-gcc-source.tar.bz2: MSP430 GCC source files
>
>
>
> · What's New
>
> o   Key Changes to MSP430 GCC
>
> §  Updated GCC compil

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

[Ghannouchi, Youssef]

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 scheme for 
the package described below.

b.  The MSP430 GCC standalone package has a software manifest included in 
the package (attached also GCC_14r1_manifest.pdf) which describe in details all 
sub components and their version.

c.   The package contains:

   i.  GGC 4.9.1

 ii.  GDB 7.5.0

iii.  binutils 
2.23

   iv.  Tcl 8.4.1

 v.  MSP430 
Debug Stack 3.5.1.1

   vi.  MSP430 
Support Files 1.173

  vii.  MSP430 GDB 
Agent 6.0.14.5



2.   MSP430 GCC 5.1

a.   The MSP430 GCC standalone package v3.5.0.0 uses the GCC 4.9.1. The 
purpose of this package was to give a quick update on GCC compiler including 
the latest bug fixes to allow our customers continuing their development easily.

b.  We are working on preparing an MSP430 compiler based on GCC 5.1. This 
package is expected to be released by end of this year. I will keep  informed.


Thank you for the valuable feedbacks, we really appreciate it.
We would like to continue improving MSP430 GCC offer, so please feel free to 
send any suggestions or recommendations.
For better tracking and handling please use TI e2e 
community to submit your requests.

Best regards,

Youssef Ghannouchi
Product Manager - Texas Instruments Inc.



Texas Instruments Deutschland GmbH, Haggertystr. 1, D-85356 Freising. 
Amtsgericht München HRB 40960. Geschäftsführer: Dr. Wolfram Tietscher. 
Vorsitzender des Aufsichtsrates: Andreas Schwaiger


From: Ghannouchi, Youssef
Sent: Sunday, September 20, 2015 6:18 PM
To: 'GCC for MSP430 - http://mspgcc.sf.net'
Cc: 'Brendan Conoboy (b...@redhat.com)'; Miller, Greg; Mitnacht, Thomas
Subject: 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 source code and MSP430 
device specific support files.
The MSP430 GCC build is also available in CCSv6 App Center on all platforms 
(Windows, Linux and Mac OSX).


· Highlights

o   MSP430 GCC compiler latest build (14r1-364)

o   MSP430 GCC for Mac OS X (beta release)

o   A new MSP430 GCC User Guide



· Package Content

o   Full Packages

§  msp430-gcc-full-linux-installer-3.5.0.0.run: MSP430 GCC Linux installer 
incl. support files and debug stack and USB drivers - apply chmod x before 
executing the package

§  msp430-gcc-full-osx-installer-3.5.0.0-beta.zip: MSP430 GCC Mac OS X 
installer incl. support files and debug stack and USB drivers - beta release

§  msp430-gcc-full-windows-installer-3.5.0.0.exe: MSP430 GCC Windows installer 
incl. support files and debug stack and USB drivers

o   Compiler Only Packages

§  msp430-gcc-linux-installer-3.5.0.0.run: MSP430 GCC Linux installer - 
compiler only - apply chmod x before executing the package

§  msp430-gcc-osx-installer-3.5.0.0-beta.zip: MSP430 GCC Mac OS X installer - 
compiler only - beta release

§  msp430-gcc-windows-installer-3.5.0.0.exe: MSP430 GCC Windows installer - 
compiler only

o   MSP430 Support Files

§  msp430-gcc-support-files.zip: MSP430 Header and linker Files

o   MSP430 GCC Sources files

§  msp430-gcc-source.tar.bz2: MSP430 GCC source files



· What's New

o   Key Changes to MSP430 GCC

§  Updated GCC compiler (14r1-364)

· Code to disable watchdog timer has been removed from start-up 
sequence (See examples).

· Fixes for Hardware Multiplier issues for F5 series 
(Details).

· Please refer to the changelogs.txt in the install directory for more 
details about all changes vs. the previous build 14r1-167.

§  MSP430 GCC for Mac OS X (beta release)

§  Updated GDB agent (6.0.14.5)

· Added support for following GDB monitor commands:

o   'monitor reset' - reset the CPU

o   'monitor halt' - halt the CPU

o   MSP Debug Stack v3.5.1.1 support

§  Please refer to the release 
notes
 for more details.

o   Key Changes to He

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

[David Brown]

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
>> here!
>>
>> 
>> The stand-alone package includes all binaries, the source code and >>
MSP430 device specific support files.
>> The MSP430 GCC build is also available in CCSv6 App Center on all
>> platforms (Windows, Linux and Mac OSX).
> 
> What version of GCC is it?  Neither 3.5.0 nor 14r1-364 are GCC
> version numbers.  Development of GCC 3.x ended a decade ago.
> 
> Regards, Mark
> 

It looks like it is gcc 4.9 (based on
 - I haven't downloaded
the new release).

It seems strange that they have stuck to 4.9, since the 5.x series has
been out for a while, but there is not a huge difference (5.x has some
nice new warnings, and more complete C++14, as well as a few more
optimisations).


--
___
Mspgcc-users mailing list
Mspgcc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mspgcc-users

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

[Mark Rages]

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 
> here!
> The stand-alone package includes all binaries, the source code and MSP430 
> device specific support files.
> The MSP430 GCC build is also available in CCSv6 App Center on all platforms 
> (Windows, Linux and Mac OSX).

What version of GCC is it?  Neither 3.5.0 nor 14r1-364 are GCC version
numbers.  Development of GCC 3.x ended a decade ago.

Regards,
Mark

--
___
Mspgcc-users mailing list
Mspgcc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mspgcc-users