Forums

Bug in latest IAR MSP430 compiler optimization???

Started by larwe April 27, 2008
In message <9Mydna-Se5gDfonVnZ2dnUVZ8uKdnZ2d@lyse.net>, David Brown 
<david.brown@hesbynett.removethisbit.no> writes
>Vladimir Vassilevsky wrote: >> Chris H wrote: >> >>> Chris H wrote: >>>> >>>>> If you find a bug in ANY compiler (not just IAR) that is fixed in >>>>>a newer version they tell you to get the latest version.
>It is not unreasonable to expect a compiler supplier to provide updates >for a certain time after purchase - you should not have to upgrade just >to get a bug fix. (Note that I have no idea what IAR's policy is in >this - I'm just expressing general comments.)
IAR in common with nearly all compilers I know of give you free updates AND upgrades for 12 months. After that you have to buy support. -- \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\ \/\/\/\/\ Chris Hills Staffs England /\/\/\/\/ \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/
In article <JogEctNATJFIFAwF@phaedsys.demon.co.uk>, chris@phaedsys.org=20
says...
> In message=20 > <4e894752-5193-471a-8ef3-1e1aa8c12b67@w5g2000prd.googlegroups.com>,=20 > larwe <zwsdotcom@gmail.com> writes > >On Apr 27, 8:33=A0am, Chris H <ch...@phaedsys.org> wrote: > > > >> >I haven't yet groveled through the assembly output to see exactly wha=
t
> >> >the difference between the two output flavors is. But this is such an > >> >astoundingly show-stopping bug I'm appalled it escaped. > >> > >> What did IAR support say about it when you told them? > > > >Kickstart has no support. >=20 > Of course not it is a FREE size limited eval version. However that does=
=20
> not mean you can't report bugs to the support team. Why wouldn't you? >=20 > >Of course, last time I was working with a > >bought version of their compiler, and found a [different] bug, the > >answer was "buy the latest upgrade". >=20 > Because you had a very old version (IAR compilers have 12 months=20 > support) and they had fixed the bug in a later version. It would only=20 > be "buy" a new version if you were out of support. Which you would be or=
=20
> you would have got the update for free. >=20 > You do like trying to make mountains out of molehills. >=20 > If you find a bug in ANY compiler (not just IAR) that is fixed in a=20 > newer version they tell you to get the latest version. If you are on=20 > support it is usually free. You only have to pay if it is a very old=20 > version. >=20 > However if you want to use an old version that is your look out.
Following is what the latest Kickstart version I have (came with the=20 EZ2500 kit) says when About... is clicked. Considering that practically=20 every component has a different version and build #, it's virtually=20 impossible to ever say with certainty what "version" of IAR anyone has. --Gene IAR Assembler for MSP430 V4.09A/W32 (4.9.1.9) D:\Program Files\IAR Systems\Embedded Workbench 4.0\430\bin\a430.exe 9/26/2007 9:38:38 AM, 688128 bytes IAR C/C++ Compiler for MSP430 V4.09A/W32 [Kickstart] (4.9.1.3) D:\Program Files\IAR Systems\Embedded Workbench 4.0\430\bin\icc430.exe 9/26/2007 9:27:24 AM, 9121792 bytes Uninstall Program for FTDI Drivers 3.0.0.33 (3.0.0.33) D:\Program Files\IAR Systems\Embedded Workbench 4.0\430\drivers\Olimex \FTDIUNIN.exe 9/26/2007 1:27:04 PM, 420864 bytes D:\Program Files\IAR Systems\Embedded Workbench 4.0\430\drivers\Olimex \omjtunin.exe 9/26/2007 1:27:04 PM, 28672 bytes Windows Setup API 5.1.2600.0 built by: WinDDK (5.1.2600.0) D:\Program Files\IAR Systems\Embedded Workbench 4.0\430\drivers\Olimex \omjtunin2k.exe 9/26/2007 1:27:04 PM, 47616 bytes PreInstaller MFC Application 1, 0, 0, 1 (1.0.0.1) D:\Program Files\IAR Systems\Embedded Workbench 4.0\430\drivers\Olimex \PreInstaller.exe 9/26/2007 1:27:04 PM, 32768 bytes Uninstall Program for FTDI D2XX Drivers 2.2.0.2 (2.2.0.2) D:\Program Files\IAR Systems\Embedded Workbench 4.0\430\drivers \SoftBaugh\FTD2XXUN.EXE 9/26/2007 1:26:58 PM, 406528 bytes D:\Program Files\IAR Systems\Embedded Workbench 4.0\430\src\examples \Segger\embOS\embOSView.exe 9/26/2007 1:28:34 PM, 53760 bytes IAR CSpyBat 5.0.1.254.6782 (5.0.1.254) D:\Program Files\IAR Systems\Embedded Workbench 4.0\common\bin \CSpyBat.exe 9/25/2007 1:53:50 PM, 270336 bytes IAR Build Utility 5.0.1.254.6782 (5.0.1.254) D:\Program Files\IAR Systems\Embedded Workbench 4.0\common\bin \iarbuild.exe 9/25/2007 1:53:50 PM, 69632 bytes IAR Embedded Workbench IDE 5.0.1.254.6782 (5.0.1.254) D:\Program Files\IAR Systems\Embedded Workbench 4.0\common\bin \IarIdePm.exe 9/25/2007 1:53:50 PM, 364544 bytes IAR Library Builder 1.03L (1.3.12.0) D:\Program Files\IAR Systems\Embedded Workbench 4.0\common\bin\xar.exe 8/31/2007 2:02:14 PM, 98304 bytes IAR XLIB 3.29P/386 (3.29.0.16) D:\Program Files\IAR Systems\Embedded Workbench 4.0\common\bin\xlib.exe 8/31/2007 2:03:18 PM, 425984 bytes IAR XLINK 4.60K (4.60.11.0) D:\Program Files\IAR Systems\Embedded Workbench 4.0\common\bin\xlink.exe 8/31/2007 3:03:52 PM, 1388544 bytes IAR C-SPY Batch Simulator Driver for MSP430 V4.09A/W32 (4.9.1.9) D:\Program Files\IAR Systems\Embedded Workbench 4.0\430\bin\430bat.dll 9/25/2007 3:16:50 PM, 270336 bytes IAR C-SPY Emulator Driver for MSP430 V4.09A/W32 [Kickstart] (4.9.1.3) D:\Program Files\IAR Systems\Embedded Workbench 4.0\430\bin\430fet.dll 9/25/2007 3:04:06 PM, 892928 bytes IAR C-SPY Library Support Plug-in for MSP430 V4.09A/W32 (4.9.1.9) D:\Program Files\IAR Systems\Embedded Workbench 4.0\430\bin \430libsupport.dll 9/25/2007 3:15:48 PM, 376832 bytes IAR C-SPY Processor Descriptor for MSP430 V4.09A/W32 (4.9.1.9) D:\Program Files\IAR Systems\Embedded Workbench 4.0\430\bin\430proc.dll 9/25/2007 3:15:36 PM, 1179648 bytes IAR C-SPY Simulator Driver for MSP430 V4.09A/W32 [Kickstart] (4.9.1.3) D:\Program Files\IAR Systems\Embedded Workbench 4.0\430\bin\430sim.dll 9/25/2007 2:59:20 PM, 1228800 bytes CP210x 1.2 (1.2.0.0) D:\Program Files\IAR Systems\Embedded Workbench 4.0\430\bin \CP210xManufacturing.dll 9/26/2007 1:30:04 PM, 69632 bytes IAR Project File Converter for MSP430 V3.21A/W32 (3.21.1.9) D:\Program Files\IAR Systems\Embedded Workbench 4.0\430\bin\cwtd430.dll 9/26/2007 1:27:06 PM, 352256 bytes FTD2XX library 3.01.06 (3.1.6.1) D:\Program Files\IAR Systems\Embedded Workbench 4.0\430\bin\FTD2XX.dll 9/26/2007 1:30:04 PM, 81920 bytes HIL 1, 2, 2, 0 (1.2.2.0) D:\Program Files\IAR Systems\Embedded Workbench 4.0\430\bin\hil.dll 9/26/2007 1:30:04 PM, 32768 bytes SEGGER J-Link MSP430 interface DLL 2.1.1.0 (2.1.1.0) D:\Program Files\IAR Systems\Embedded Workbench 4.0\430\bin\JLink430.dll 9/26/2007 1:30:04 PM, 114688 bytes MSP430.dll for the USB-MSP430-FPA v10.0 2, 1, 10, 0 (2.1.10.0) D:\Program Files\IAR Systems\Embedded Workbench 4.0\430\bin\MSP430- FPA.dll 9/26/2007 1:30:04 PM, 348160 bytes MSP430 Version (2.3.1.0) D:\Program Files\IAR Systems\Embedded Workbench 4.0\430\bin\msp430.dll 9/26/2007 1:30:04 PM, 225280 bytes MSP430 1, 0, 1, 1 (1.0.1.1) D:\Program Files\IAR Systems\Embedded Workbench 4.0\430\bin\olimex.dll 9/26/2007 1:30:06 PM, 458752 bytes SBMSP430_DLL DLL 2, 1, 8, 1 (2.1.8.1) D:\Program Files\IAR Systems\Embedded Workbench 4.0\430\bin\sbmsp430.dll 9/26/2007 1:30:06 PM, 258048 bytes SiUSBXp 2, 3, 0, 0 (2.3.0.0) D:\Program Files\IAR Systems\Embedded Workbench 4.0\430\bin\SiUSBXp.dll 9/26/2007 1:30:06 PM, 90112 bytes MSP430 Version (2.1.8.1) D:\Program Files\IAR Systems\Embedded Workbench 4.0\430\bin \SoftBaugh.dll 9/26/2007 1:30:06 PM, 32768 bytes IAR Workbench Target Descriptor for MSP430 V4.09A/W32 (4.9.1.9) D:\Program Files\IAR Systems\Embedded Workbench 4.0\430\bin\swtd430.dll 9/25/2007 3:16:40 PM, 749568 bytes IAR Workbench Target Descriptor, Emulator, for MSP430 V4.09A/W32 (4.9.1.9) D:\Program Files\IAR Systems\Embedded Workbench 4.0\430\bin \swtd430fet.dll 9/25/2007 2:45:40 PM, 360448 bytes IAR Workbench Target Descriptor, Simulator, for MSP430 V4.09A/W32 (4.9.1.9) D:\Program Files\IAR Systems\Embedded Workbench 4.0\430\bin \swtd430sim.dll 9/25/2007 2:59:54 PM, 294912 bytes FTD2XX library 3.00.05 (3.0.5.1) D:\Program Files\IAR Systems\Embedded Workbench 4.0\430\drivers\Olimex \FTD2XX.dll 9/26/2007 1:27:04 PM, 81920 bytes FTD2XX library 2.00.11 (2.0.11.1) D:\Program Files\IAR Systems\Embedded Workbench 4.0\430\drivers \SoftBaugh\FTD2XX.dll 9/26/2007 1:26:58 PM, 69632 bytes LCD Plugin for EW430 3.42A (3.42.1.9) D:\Program Files\IAR Systems\Embedded Workbench 4.0\430\plugins\Lcd \lcd.dll 9/26/2007 2:06:54 PM, 266240 bytes SEGGER embOS IAR-Plugin 2, 0, 5, 0 (2.0.5.0) D:\Program Files\IAR Systems\Embedded Workbench 4.0\430\plugins\rtos \embOS\embOSPlugin.dll 9/26/2007 1:28:34 PM, 397312 bytes =B5C/OS-II KA Plug-in for C-SPY DLL 2.50 2007-09-10 (2.5.0.0) D:\Program Files\IAR Systems\Embedded Workbench 4.0\430\plugins\rtos \uCOS-II\uCOS-II-KA-CSpy.dll 9/26/2007 1:28:34 PM, 339968 bytes IAR CSpyBat Language Specific Resources 5.0.1.254.6782 (5.0.1.254) D:\Program Files\IAR Systems\Embedded Workbench 4.0\common\bin \CSpyBat.ENU.dll 9/25/2007 1:53:50 PM, 4608 bytes IAR C-SPY Debugger GUI 5.0.1.254.6782 (5.0.1.254) D:\Program Files\IAR Systems\Embedded Workbench 4.0\common\bin \DebuggerGui.dll 9/25/2007 1:53:50 PM, 1159168 bytes IAR C-SPY Debugger GUI Language Specific Resources 5.0.1.254.6782 (5.0.1.254) D:\Program Files\IAR Systems\Embedded Workbench 4.0\common\bin \DebuggerGui.ENU.dll 9/25/2007 1:53:50 PM, 73728 bytes IAR Find In Files 5.0.1.254.6782 (5.0.1.254) D:\Program Files\IAR Systems\Embedded Workbench 4.0\common\bin \FindInFiles.dll 9/25/2007 1:53:50 PM, 188416 bytes IAR Find In Files Language Specific Resources 5.0.1.254.6782 (5.0.1.254) D:\Program Files\IAR Systems\Embedded Workbench 4.0\common\bin \FindInFiles.ENU.dll 9/25/2007 1:53:50 PM, 5632 bytes IAR Build Utility Language Specific Resources 5.0.1.254.6782 (5.0.1.254) D:\Program Files\IAR Systems\Embedded Workbench 4.0\common\bin \iarbuild.ENU.dll 9/25/2007 1:53:50 PM, 4096 bytes IAR Embedded Workbench IDE Language Specific Resources 5.0.1.254.6782 (5.0.1.254) D:\Program Files\IAR Systems\Embedded Workbench 4.0\common\bin \IarIdePm.ENU.dll 9/25/2007 1:53:50 PM, 479232 bytes IAR IDE Framework 5.0.1.254.6782 (5.0.1.254) D:\Program Files\IAR Systems\Embedded Workbench 4.0\common\bin \IdeFramework.dll 9/25/2007 1:53:50 PM, 655360 bytes IAR IDE Framework Language Specific Resources 5.0.1.254.6782 (5.0.1.254) D:\Program Files\IAR Systems\Embedded Workbench 4.0\common\bin \IdeFramework.ENU.dll 9/25/2007 1:53:50 PM, 5120 bytes IAR C-SPY Debugger Kernel 5.0.1.254.6782 (5.0.1.254) D:\Program Files\IAR Systems\Embedded Workbench 4.0\common\bin \Kernel.dll 9/25/2007 1:53:50 PM, 1576960 bytes IAR C-SPY Debugger Kernel Language Specific Resources 5.0.1.254.6782 (5.0.1.254) D:\Program Files\IAR Systems\Embedded Workbench 4.0\common\bin \Kernel.ENU.dll 9/25/2007 1:53:50 PM, 8192 bytes IAR Log Window 5.0.1.254.6782 (5.0.1.254) D:\Program Files\IAR Systems\Embedded Workbench 4.0\common\bin \LogWindow.dll 9/25/2007 1:53:50 PM, 212992 bytes IAR Log Window Language Specific Resources 5.0.1.254.6782 (5.0.1.254) D:\Program Files\IAR Systems\Embedded Workbench 4.0\common\bin \LogWindow.ENU.dll 9/25/2007 1:53:50 PM, 11264 bytes IAR Project Manager Engine 5.0.1.254.6782 (5.0.1.254) D:\Program Files\IAR Systems\Embedded Workbench 4.0\common\bin \ProjectManagerEngine.dll 9/25/2007 1:53:50 PM, 1073152 bytes IAR Project Manager Engine Language Specific Resources 5.0.1.254.6782 (5.0.1.254) D:\Program Files\IAR Systems\Embedded Workbench 4.0\common\bin \ProjectManagerEngine.ENU.dll 9/25/2007 1:53:50 PM, 13824 bytes IAR Project Manager Gui 5.0.1.254.6782 (5.0.1.254) D:\Program Files\IAR Systems\Embedded Workbench 4.0\common\bin \ProjectManagerGui.dll 9/25/2007 1:53:50 PM, 708608 bytes IAR Project Manager Gui Language Specific Resources 5.0.1.254.6782 (5.0.1.254) D:\Program Files\IAR Systems\Embedded Workbench 4.0\common\bin \ProjectManagerGui.ENU.dll 9/25/2007 1:53:50 PM, 106496 bytes IAR Text Editor 5.0.1.254.6782 (5.0.1.254) D:\Program Files\IAR Systems\Embedded Workbench 4.0\common\bin \TextEditor.dll 9/25/2007 1:53:50 PM, 491520 bytes IAR Text Editor Language Specific Resources 5.0.1.254.6782 (5.0.1.254) D:\Program Files\IAR Systems\Embedded Workbench 4.0\common\bin \TextEditor.ENU.dll 9/25/2007 1:53:50 PM, 26112 bytes Shared Library for Xerces-C Version 1.5.1 1, 5, 1 (1.5.1.0) D:\Program Files\IAR Systems\Embedded Workbench 4.0\common\bin\xerces-c_ 1_5_1.dll 9/25/2007 1:53:48 PM, 1257472 bytes D:\Program Files\IAR Systems\Embedded Workbench 4.0\common\bin \XmlLib.dll 9/25/2007 1:53:48 PM, 90112 bytes IAR Code Coverage Plug-in 5.0.1.254.6782 (5.0.1.254) D:\Program Files\IAR Systems\Embedded Workbench 4.0\common\plugins \CodeCoverage\CodeCoverage.dll 9/25/2007 1:53:48 PM, 303104 bytes IAR Code Coverage Plug-in Language Specific Resources 5.0.1.254.6782 (5.0.1.254) D:\Program Files\IAR Systems\Embedded Workbench 4.0\common\plugins \CodeCoverage\CodeCoverage.ENU.dll 9/25/2007 1:53:48 PM, 10752 bytes IAR ORTI RTOS Plug-in 5.0.1.254.6782 (5.0.1.254) D:\Program Files\IAR Systems\Embedded Workbench 4.0\common\plugins\Orti \Orti.dll 9/25/2007 1:53:48 PM, 413696 bytes D:\Program Files\IAR Systems\Embedded Workbench 4.0\common\plugins\Orti \Orti.ENU.dll 9/25/2007 1:53:48 PM, 8704 bytes IAR Profiling Plug-in 5.0.1.254.6782 (5.0.1.254) D:\Program Files\IAR Systems\Embedded Workbench 4.0\common\plugins \Profiling\Profiling.dll 9/25/2007 1:53:48 PM, 299008 bytes IAR Profiling Plug-in Language Specific Resources 5.0.1.254.6782 (5.0.1.254) D:\Program Files\IAR Systems\Embedded Workbench 4.0\common\plugins \Profiling\Profiling.ENU.dll 9/25/2007 1:53:48 PM, 10752 bytes IAR Stack Plug-in 5.0.1.254.6782 (5.0.1.254) D:\Program Files\IAR Systems\Embedded Workbench 4.0\common\plugins\Stack \Stack.dll 9/25/2007 1:53:48 PM, 331776 bytes IAR Stack Plug-in Language Specific Resources 5.0.1.254.6782 (5.0.1.254) D:\Program Files\IAR Systems\Embedded Workbench 4.0\common\plugins\Stack \Stack.ENU.dll 9/25/2007 1:53:48 PM, 8192 bytes
In message <MPG.227ec5c2de8d322e98990c@news.verizon.net>, Gene S. 
Berkowitz <first.last@verizon.net> writes
>In article <JogEctNATJFIFAwF@phaedsys.demon.co.uk>, chris@phaedsys.org >says... >> In message >> <4e894752-5193-471a-8ef3-1e1aa8c12b67@w5g2000prd.googlegroups.com>, >> larwe <zwsdotcom@gmail.com> writes >> >On Apr 27, 8:33&#2013266080;am, Chris H <ch...@phaedsys.org> wrote: >> > >> >> >I haven't yet groveled through the assembly output to see exactly what >> >> >the difference between the two output flavors is. But this is such an >> >> >astoundingly show-stopping bug I'm appalled it escaped. >> >> >> >> What did IAR support say about it when you told them? >> > >> >Kickstart has no support. >> >> Of course not it is a FREE size limited eval version. However that does >> not mean you can't report bugs to the support team. Why wouldn't you? >> >> >Of course, last time I was working with a >> >bought version of their compiler, and found a [different] bug, the >> >answer was "buy the latest upgrade". >> >> Because you had a very old version (IAR compilers have 12 months >> support) and they had fixed the bug in a later version. It would only >> be "buy" a new version if you were out of support. Which you would be or >> you would have got the update for free. >> >> You do like trying to make mountains out of molehills. >> >> If you find a bug in ANY compiler (not just IAR) that is fixed in a >> newer version they tell you to get the latest version. If you are on >> support it is usually free. You only have to pay if it is a very old >> version. >> >> However if you want to use an old version that is your look out. > >Following is what the latest Kickstart version I have (came with the >EZ2500 kit) says when About... is clicked. Considering that practically >every component has a different version and build #, it's virtually >impossible to ever say with certainty what "version" of IAR anyone has.
As with ALL compiler suites. You are either being deliberately obtuse or don't understand the tools. Neither trait is good for a developer. The package has a release number (on the CD, zip file etc) and the individual components also have release numbers as you listed. It is called version control. Something that happens in professional software development. I used to have this problem a lot with Keil C51 when asking what version of the compiler someone was using. I often got the version of the IDE. -- \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\ \/\/\/\/\ Chris Hills Staffs England /\/\/\/\/ \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/

Chris H wrote:


>> I have no illusion that the compiler development >> is different from any other sw development. Same kind of lousy and >> pitifull business. > > > So your software development is a "lousy and pitiful business" and you > judge all the rest by your standards? >
The software development is lousy and pitiful business. The ones who state the different either have no clue, or deliberately lying, or never wrote anything longer then "Hello World". Vladimir Vassilevsky DSP and Mixed Signal Design Consultant http://www.abvolt.com
On 2008-04-27, larwe <zwsdotcom@gmail.com> wrote:
> On Apr 27, 8:33?am, Chris H <ch...@phaedsys.org> wrote: > >> >I haven't yet groveled through the assembly output to see exactly what >> >the difference between the two output flavors is. But this is such an >> >astoundingly show-stopping bug I'm appalled it escaped. >> >> What did IAR support say about it when you told them? > > Kickstart has no support.
That may be true de jure, but not de facto. If you report the bug on the MSP430 mailing list, I'd bet a doughnut that somebody from IAR will respond.
> Of course, last time I was working with a bought version of > their compiler, and found a [different] bug, the answer was > "buy the latest upgrade".
Um, that's pretty much how commercial software works. If you were using mspgcc, you could just fix the problem, submit the patch, and get on with your work. Worst case, you could report the problem and wait for a day or two while somebody else fixes it. For free. -- Grant Edwards grante Yow! We're going to a at new disco! visi.com
In message <YXkRj.12293$GE1.363@nlpi061.nbdc.sbc.com>, Vladimir 
Vassilevsky <antispam_bogus@hotmail.com> writes
> > >Chris H wrote: > > >>> I have no illusion that the compiler development is different from >>>any other sw development. Same kind of lousy and pitifull business. >> So your software development is a "lousy and pitiful business" and >>you judge all the rest by your standards? >> > >The software development is lousy and pitiful business. The ones who >state the different either have no clue, or deliberately lying, or >never wrote anything longer then "Hello World".
Well you are wrong on all three counts. Perhaps it is just your world. -- \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\ \/\/\/\/\ Chris Hills Staffs England /\/\/\/\/ \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/
In article <GLSdnZPTPfSDQYjVnZ2dnUVZ_t3inZ2d@visi>, grante@visi.com 
says...
> On 2008-04-27, larwe <zwsdotcom@gmail.com> wrote: > > On Apr 27, 8:33?am, Chris H <ch...@phaedsys.org> wrote: > > > >> >I haven't yet groveled through the assembly output to see exactly what > >> >the difference between the two output flavors is. But this is such an > >> >astoundingly show-stopping bug I'm appalled it escaped. > >> > >> What did IAR support say about it when you told them? > > > > Kickstart has no support. > > That may be true de jure, but not de facto. If you report the > bug on the MSP430 mailing list, I'd bet a doughnut that > somebody from IAR will respond. > > > Of course, last time I was working with a bought version of > > their compiler, and found a [different] bug, the answer was > > "buy the latest upgrade". > > Um, that's pretty much how commercial software works. If you > were using mspgcc, you could just fix the problem, submit the > patch, and get on with your work.
I'm not sure that someone qualified to write good embedded code for the MSP430 is also qualified to patch the code generator of mspgcc. I've written a lot of embedded code for the MSP430 and other embedded systems, but I've never even LOOKED at the source for the code generator of any compiler! That may be because I got into embedded systems from oceanography---and have never taken any computer science course other than a freshman introductory course---and that in 1968! Oddly enough, I did teach computer science at the U for a few years---sophomore and junior level courses in architecture and assembly-language programming.
> Worst case, you could report > the problem and wait for a day or two while somebody else > fixes it. For free. > >
Mark Borgerson
In message <MPG.227f99fe4c3cef81989841@newsgroups.comcast.net>, Mark 
Borgerson <mborgerson@comcast.net> writes
>In article <GLSdnZPTPfSDQYjVnZ2dnUVZ_t3inZ2d@visi>, grante@visi.com >says... >> Um, that's pretty much how commercial software works. If you >> were using mspgcc, you could just fix the problem, submit the >> patch, and get on with your work. > >I'm not sure that someone qualified to write good embedded >code for the MSP430 is also qualified to patch the code >generator of mspgcc.
I would agree... most only think they are. -- \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\ \/\/\/\/\ Chris Hills Staffs England /\/\/\/\/ \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/
In message 
<4e894752-5193-471a-8ef3-1e1aa8c12b67@w5g2000prd.googlegroups.com>, 
larwe <zwsdotcom@gmail.com> writes
>On Apr 27, 8:33&#2013266080;am, Chris H <ch...@phaedsys.org> wrote: > >> >I haven't yet groveled through the assembly output to see exactly what >> >the difference between the two output flavors is. But this is such an >> >astoundingly show-stopping bug I'm appalled it escaped. >> >> What did IAR support say about it when you told them? > >Kickstart has no support.
Their response to a bug in
>IAR C/C++ Compiler for MSP430 >V4.10E/W32 [Kickstart] (4.10.5.3)
IE a Kickstart compiler that has "no support" was:- /////////////////// It is documented that Hi optimization level is a very very aggressive level that must be always tested against the application. At level LOW the user will get ALL the industry standard optimization techniques, most of the new techniques are represented at the hi level. There are several guidelines how to deal with these situation, the IAR compiler support optimization on the function level, using #prgama optimization in case you really want to use the high level, declaring variables as volatile will help the optimizer decide whether to optimize out a variable or not, avoiding empty delay loops and simply including a __no_operation() intrinsic function inside an empty loop will help the optimizer decide etc... If you have a specific sample code that we can compile and link and debug, then send it over to fwd to development . /////////////////// So it is Documented... You did read the documentation? If you would like to send IAR some sample code they will look at the problem. So much for "no support" you did not even ask! You just made assumptions and tried to discredit a compiler company. Rather unprofessional of you to say the least. -- \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\ \/\/\/\/\ Chris Hills Staffs England /\/\/\/\/ \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/
On 2008-04-28, Mark Borgerson <mborgerson@comcast.net> wrote:

>>> Of course, last time I was working with a bought version of >>> their compiler, and found a [different] bug, the answer was >>> "buy the latest upgrade". >> >> Um, that's pretty much how commercial software works. If you >> were using mspgcc, you could just fix the problem, submit the >> patch, and get on with your work. > > I'm not sure that someone qualified to write good embedded > code for the MSP430 is also qualified to patch the code > generator of mspgcc.
Possibly not. Then you've the option of waiting for somebody else to fix it or paying somebody else to fix it. -- Grant Edwards grante Yow! I want to mail a at bronzed artichoke to visi.com Nicaragua!