#60 GCC-3's bug(?)
I have some trouble with GCC-3.
My main sake of using Basilisk is to use IgorPro on my
Linux box.
Therefore, I cannot be satisfied only by compiling and
running
Basilisk without error. I need IgorPro running without
any toruble.
Previously, I found I was happy with '--enable-fpe=uae'
option. (I was still un-happy that I cannot use
JIT-compiler.)
Recently, I upgraded my Linux box using Slackware-9.0,
where the GCC version is 3.2.2. And I also knew the
newest JIT version (BasiliskII_src_14032003.tar.bz2).
Then I make new BasiliskII on my new box.
With '--enable-fpe=uae', the compilation was completed
without
error. The binary might run. However, IgorPro said
unexpected error. It was quite coplicate to explain:
Igor can hold
internal states.. But,
I think, it might be relating to value-rounding.
Logged In: YES
user_id=111143
Sorry, the message was sent while I edit it.
(snip)
> It was quite coplicate to explain:
Igor can hold nternal states, which can be chaged by user.
Certain of them can be 0 or 1 as flag. However, I could not
set it to 1. I think, internal upper limit was badly held.
On the other hand, Intel Compiler gave good result.
Using icc/icpc, the binary may run without any trouble.
Therefore, there is some bug or incompatibilities with GCC-3.
Someone hear about it?