Looking for the latest version? Download LTS-20120406 (417.6 kB)
Home / Patches
Name Modified Size Downloads / Week Status
Parent folder
gcc-4.7.0 2012-09-11 11 weekly downloads
binutils-2.22 2012-09-11 0
LTS 2012-05-02 3636 weekly downloads
gcc-4.6.3 2012-04-06 0
binutils-2.21.1a 2012-04-06 0
gcc-4.6.2 2012-03-31 0
gcc-4.6.1 2012-02-24 0
gdb-7.2a 2011-12-05 44 weekly downloads
binutils-2.21 2011-07-27 0
binutils-2.21.1 2011-07-27 0
gcc-4.5.2 2011-07-27 0
gcc-4.5.3 2011-07-27 0
gdb-7.2 2011-07-27 0
RELEASES.txt 2012-09-11 2.0 kB 0
README.rst 2012-05-12 1.9 kB 0
COPYING 2011-07-25 219 Bytes 0
Totals: 16 Items   4.1 kB 41

MSPGCC Patch Archive

This area contains patches that add TI MSP430 support to the GNU development toolchain.

The intent is that this contain all released patches. The file RELEASES indicates which patches were collected into mspgcc releases: these collections may be assumed to work together, while mixing/matching other versions might result in problems.

The Patches repository is intended for maintainers and downstream packagers. Users who simply want a working mspgcc should follow the standard installation instructions for their system.

Packagers can obtain a local copy that tracks future additions with the following command:

git checkout -b patches git://mspgcc.git.sourceforge.net/gitroot/mspgcc/mspgcc

The mspgcc patches intentionally do not add version information, as it is the responsibility of the packager to select from among the "official" patches provided here and any distribution-specific changes.

LTS release series starting with 20120406 will include the following content in the gcc-X.Y.Z/gcc/DEV-PHASE file, allowing the compiler release version to be identified with the -version option:

mspgcc LTS YYYYMMDD unpatched

Similarly, for binutils the file binutils-X.Y/bfd/version.h in the release will have the following line:

#define BFD_MSPGCC_VERSION LTS YYYYMMDD unpatched

Downstream maintainers should update this file to represent in some way the set of patches that have been applied to the release. If all and only official mspgcc LTS patches are applied, one possibility is to replace "unpatched" with "patched to YYYYMMDD" representing the date of the most recent patch download from the corresponding LTS patch directory under https://sourceforge.net/projects/mspgcc/files/Patches/LTS/.

Source: README.rst, updated 2012-05-12

Thanks for helping keep SourceForge clean.

Screenshot instructions:
Windows
Mac
Red Hat Linux   Ubuntu

Click URL instructions:
Right-click on ad, choose "Copy Link", then paste here →
(This may not be possible with some types of ads)

More information about our ad policies
X

Briefly describe the problem (required):

Upload screenshot of ad (required):
Select a file, or drag & drop file here.

Please provide the ad click URL, if possible:

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.

No, thanks