Bug in latest IAR MSP430 compiler optimization???
in [Embedded]
|
Prev: AC spike go pass XFRM and regulator to reset CPU!!??
Next: Loss of synchronisation: Are the chips reliable?
From: Gene S. Berkowitz on 4 May 2008 09:34 In article <PUAFTtFCVXFIFAS7(a)phaedsys.demon.co.uk>, chris(a)phaedsys.org says... > In message <MPG.227ec5c2de8d322e98990c(a)news.verizon.net>, Gene S. > Berkowitz <first.last(a)verizon.net> writes > >In article <JogEctNATJFIFAwF(a)phaedsys.demon.co.uk>, chris(a)phaedsys.org > >says... > >> In message > >> <4e894752-5193-471a-8ef3-1e1aa8c12b67(a)w5g2000prd.googlegroups.com>, > >> larwe <zwsdotcom(a)gmail.com> writes > >> >On Apr 27, 8:33 am, Chris H <ch...(a)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. Excuse me, but it isn't ME being obtuse, it's IAR's method of versioning, which makes it quite difficult to document what toolchain "version" was/should be used to build a particular "version" of an application. The choice is to either archive the entire IAR environment used to produce the executable, or never/rarely "upgrade". > 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. Ooh, touchy, aren't we? Of course, it also ignores the fact that not all "releases" of the various components work with earlier release components of the same major version. > 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. Right, my point exactly. --Gene
From: Mark Borgerson on 4 May 2008 13:30
In article <MPG.2287858dc3a919a298990f(a)news.verizon.net>, first.last(a)verizon.net says... > In article <PUAFTtFCVXFIFAS7(a)phaedsys.demon.co.uk>, chris(a)phaedsys.org > says... > > In message <MPG.227ec5c2de8d322e98990c(a)news.verizon.net>, Gene S. > > Berkowitz <first.last(a)verizon.net> writes > > >In article <JogEctNATJFIFAwF(a)phaedsys.demon.co.uk>, chris(a)phaedsys.org > > >says... > > >> In message > > >> <4e894752-5193-471a-8ef3-1e1aa8c12b67(a)w5g2000prd.googlegroups.com>, > > >> larwe <zwsdotcom(a)gmail.com> writes > > >> >On Apr 27, 8:33 am, Chris H <ch...(a)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. > > Excuse me, but it isn't ME being obtuse, it's IAR's method of > versioning, which makes it quite difficult to document what toolchain > "version" was/should be used to build a particular "version" of an > application. > > The choice is to either archive the entire IAR environment used to > produce the executable, or never/rarely "upgrade". I generally choose to keep the old versions around. IAR makes it easy to do that by allowing each new version to install in a different directory. EWARM 5.10 takes up about 622MB of hard disk ( about 20 cents worth of a 250GB disk). The IAR menu bar tab gives you an entry for each installed version, so it's easy to start the appropriate version. > > > 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. > > Ooh, touchy, aren't we? Of course, it also ignores the fact that not > all "releases" of the various components work with earlier release > components of the same major version. > > > 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. > > Right, my point exactly. Mark Borgerson |