Forums

Bug in latest IAR MSP430 compiler optimization???

Started by larwe April 27, 2008
In article <PUAFTtFCVXFIFAS7@phaedsys.demon.co.uk>, chris@phaedsys.org=20
says...
> In message <MPG.227ec5c2de8d322e98990c@news.verizon.net>, Gene S.=20 > 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=A0am, 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 do=
es
> >> 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. >=20 > As with ALL compiler suites. You are either being deliberately obtuse or=
=20
> 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=20 versioning, which makes it quite difficult to document what toolchain=20 "version" was/should be used to build a particular "version" of an=20 application. The choice is to either archive the entire IAR environment used to=20 produce the executable, or never/rarely "upgrade".
> The package has a release number (on the CD, zip file etc) and the=20 > individual components also have release numbers as you listed. It is=20 > called version control. Something that happens in professional software=
=20
> development.
Ooh, touchy, aren't we? Of course, it also ignores the fact that not=20 all "releases" of the various components work with earlier release=20 components of the same major version.
> I used to have this problem a lot with Keil C51 when asking what version=
=20
> of the compiler someone was using. I often got the version of the IDE.
Right, my point exactly. --Gene
In article <MPG.2287858dc3a919a298990f@news.verizon.net>,=20
first.last@verizon.net says...
> In article <PUAFTtFCVXFIFAS7@phaedsys.demon.co.uk>, chris@phaedsys.org=20 > says... > > In message <MPG.227ec5c2de8d322e98990c@news.verizon.net>, Gene S.=20 > > 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=A0am, Chris H <ch...@phaedsys.org> wrote: > > >> > > > >> >> >I haven't yet groveled through the assembly output to see exactl=
y what
> > >> >> >the difference between the two output flavors is. But this is su=
ch 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 on=
ly
> > >> be "buy" a new version if you were out of support. Which you would b=
e 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 o=
n
> > >> support it is usually free. You only have to pay if it is a very o=
ld
> > >> 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 practical=
ly
> > >every component has a different version and build #, it's virtually > > >impossible to ever say with certainty what "version" of IAR anyone has=
.
> >=20 > > As with ALL compiler suites. You are either being deliberately obtuse o=
r=20
> > don't understand the tools. Neither trait is good for a developer. >=20 > Excuse me, but it isn't ME being obtuse, it's IAR's method of=20 > versioning, which makes it quite difficult to document what toolchain=20 > "version" was/should be used to build a particular "version" of an=20 > application. >=20
> The choice is to either archive the entire IAR environment used to=20 > 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=20 directory. EWARM 5.10 takes up about 622MB of hard disk ( about 20 cents=20 worth of a 250GB disk). The IAR menu bar tab gives you an entry for=20 each installed version, so it's easy to start the appropriate version.
>=20 > > The package has a release number (on the CD, zip file etc) and the=20 > > individual components also have release numbers as you listed. It is=20 > > called version control. Something that happens in professional softwar=
e=20
> > development. >=20 > Ooh, touchy, aren't we? Of course, it also ignores the fact that not=20 > all "releases" of the various components work with earlier release=20 > components of the same major version. >=20 > > I used to have this problem a lot with Keil C51 when asking what versio=
n=20
> > of the compiler someone was using. I often got the version of the IDE. >=20 > Right, my point exactly.
Mark Borgerson