issue with AMD processors?

plmonkey has asked for the wisdom of the Perl Monks concerning the following question:

Hi all. I recently wrote a short perl script (i use active perl, under windows) which works fine on my PC with an Intel CPU. I copied the script to my other computer which has an AMD 2400+ processor. When I run the script on the AMD machine CPU usage instantly jumps to 99% and the memory usage keeps steadily increasing. Both machines are similar in other respects, 1 gig ram, running windows XP. Is there a known issue with AMD processors that could cause this, or is the culprit likely something else? Any input is really appreciated!!!! Thanks in advance to anyone who can offer advice. plmonkey.

Comment on issue with AMD processors?

Replies are listed 'Best First'.
Re: issue with AMD processors? by CountZero (Bishop) on Jul 20, 2005 at 23:06 UTC
I run AS Perl on both Genuine Intel and AMD machines and never noticed such problems as you describe. Can you post the short script so we can check/test it too? CountZero "If you have four groups working on a compiler, you'll get a 4-pass compiler." - Conway's Law	[reply]
Re: issue with AMD processors? by 5mi11er (Deacon) on Jul 20, 2005 at 22:13 UTC
So, does the script actually work on the AMD system? I'm guessing no, but you didn't say. Have you verified that your script didn't get corrupted during the transfer? Have you verified that perl is correctly installed on the AMD machine? I'm fairly certain AMD based XP versions of activestate perl are tested in the same way that Intel based versions are tested, so I'm doubting there is a Perl specific bug with AMD based systems... -Scott Update: Oooo! Did you perhaps grab a non-AMD binary version of Perl and install that on the AMD machine? Update: Never mind, Active state doesn't appear to care whether the machine is AMD or Intel based...	[reply]
Re: issue with AMD processors? by gellyfish (Monsignor) on Jul 20, 2005 at 22:14 UTC
I can't offer advice but I might suggest that the output of `perl -V` might be useful, it could well be to do with the compiler and/or the flags that were used to build the perl in question. /J\	[reply] [d/l]