comp.lang.idl-pvwave archive
Messages from Usenet group comp.lang.idl-pvwave, compiled by Paulo Penteado

Home » Public Forums » archive » MacTel
Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend 
Switch to threaded view of this topic Create a new topic Submit Reply
MacTel [message #44313] Mon, 06 June 2005 19:12 Go to next message
Ken Mankoff is currently offline  Ken Mankoff
Messages: 158
Registered: February 2000
Senior Member
I've just heard that Mac will be moving from PPC to x86 chips in the
next few years. I'm not sure what this means for IDL on Mac. Any
thoughts from RSI or anyone else?

-k.
Re: MacTel [message #44368 is a reply to message #44313] Thu, 09 June 2005 19:25 Go to previous message
netnews.comcast.net is currently offline  netnews.comcast.net
Messages: 10
Registered: October 2004
Junior Member
Ken Mankoff wrote:

> I've just heard that Mac will be moving from PPC to x86 chips in the
> next few years. I'm not sure what this means for IDL on Mac. Any
> thoughts from RSI or anyone else?

I'm sure many of you have read this already but Cringely is out with his
angle on the MacTel merger. More drama can be found here:

http://www.pbs.org/cringely/pulpit/pulpit20050519.html

A little far fetched but one can dream...

-r
Re: MacTel [message #44394 is a reply to message #44313] Wed, 08 June 2005 06:56 Go to previous message
Ken Mankoff is currently offline  Ken Mankoff
Messages: 158
Registered: February 2000
Senior Member
On Mon, 6 Jun 2005, Ken Mankoff wrote:
> I've just heard that Mac will be moving from PPC to x86 chips in
> the next few years. I'm not sure what this means for IDL on Mac.
> Any thoughts from RSI or anyone else?

I had a colleague at WWDC test an IDL app on a MacTel that Apple set
up for testing purposes. It is a simple app running in the VM that
reads netCDFs, produces PNGs, and uses the Z-buffer. It ran without
a problem as-is. I guess this means their emulation layer (Rosetta?)
works in this case.

-k.
Re: MacTel [message #44396 is a reply to message #44313] Tue, 07 June 2005 14:16 Go to previous message
JD Smith is currently offline  JD Smith
Messages: 850
Registered: December 1999
Senior Member
On Tue, 07 Jun 2005 15:04:57 -0500, Kenneth Bowman wrote:

> In article <d84ngk$r9f$1@news.nems.noaa.gov>,
> Rick Towler <rick.towler@nomail.noaa.gov> wrote:
>
>> As far as IDL on OS X is concerned it's hard to say (this is
>> comp.lang.idl-pvwave, isn't it?) The next 18-24 months will be
>> difficult as Apple transitions. I don't think anyone is going to run
>> IDL using the binary translation layer so what does RSI do? We know they
>> are reticent to support IDL on the OS X PPC architecture. Now are they
>> going to support both? I think we can only hope that the claims that
>> most applications can be recompiled in a few hours with just "minor
>> tweaks" are true.
>
> Since the OS X version is basically the Unix version (i.e., runs from the
> command line under X Windows) the port should be straightforward, if not
> trivial. It is not so much an OS X application as a FreeBSD application. ;-)
> Altivec optimizations will need to be replaced with sorta-equivalent Intel
> optimizations, but maybe the compiler will take care of that.

Well, the current OSX IDL really doesn't have too much in the way of
Altivec optimizations; they had put some effort into that before
pulling the plug on a Mac-native IDL several years ago, but that
didn't pan out. Looks like they made the right call after all.

Personal anecdote: I got my shiny new Powerbook G4 several months ago,
and decided to put IDL to a speed test. Not that I bought it for
hard-core cruching, but I figured it should at least keep up with my 3
year old desktop. Sadly, my 3 year old PIII Dell laptop fully bested
it by about a factor of 2 in TIME_TEST3. When normalized to clock
speed, the slower PIII actually was 3x faster per clock. Ouch! When
I queried RSI on this, it seems the consensus opinion is that GCC,
which RSI uses to compile IDL under OSX (and Apple recommends),
produces fairly slow PPC code. In fact, between OS9 and OSX, there
was a general slowdown of IDL on the same hardware, when they switched
compilers. I fully believe had the time been invested to optimize IDL
for the G4/G5, it would have handily trounced equivalent processors on
a clock for clock basis, but that was not to be. Altivec was/is
widely acknowledged as the most capable of the consumer-grade SIMD
units. That said, GCC is much more mature and robust for x86. So
really, our Altivec units are sitting there quietly twiddling their
thumbs when IDL runs, so, in terms of IDL performance, IDL/MacTel is
actually a fairly big win, assuming it ever sees the light of day. I
suspect their port will be similarly trivial to Mathematicas, which
took editing 20 lines of code, checking one box, and waiting 2 hours.
It's programs which have invested significantly in the Mac/PPC
platform exclusively that will have trouble. Natively cross-platform
apps should be fine.

>> You have to wonder what the Macatistas are thinking. Some of the cachet
>> of the Mac platform was it's mysterious RISC based PPC architecture.
>> Now you guys will be so ordinary. :) And <gasp> what if you could walk
>> into your local apple store and buy a copy of OS X to run on your home
>> built x86 PC? Then how would you discern yourself from the slobbering
>> masses? You say it won't happen... And they said OS X would never run
>> on x86 too.
>
> Apple said yesterday that OS X will not run on generic PC hardware, although how
> they will accomplish that has yet to be revealed. Apple is still mostly a
> hardware company and can't afford to lose their hardware business.
>
> The new machines may have Pentia inside, but they will still *look* cooler than
> wintel machines outside. ;-) (And still cost more, no doubt.)
>
> It has been an open secret that Apple has maintained a parallel x86 version of
> OS X.

Yes, definitely no OSX on the beige box, but the RISC cachet issue may
prove damaging to more than just the egos of Mac fanatics. Imagine
this scenario: one of the x86 emulators, like VMWare, gets ported to
OSX/Intel, and runs at nearly full speed (since it no longer needs to
emulate the x86 underneath). Company X (e.g. RSI) tries out the
Windows version of their program under VMWare and finds that, indeed,
it runs at perfectly acceptable speed with just a few interface
glitches, and some general ugliness. They declare this "good enough",
and the Mac port is quietly dropped. (You could argue RSI has already
done this, dumping the native Aqua IDL port in favor of the Unix/X11
flavor). Something to think about.

JD
  Switch to threaded view of this topic Create a new topic Submit Reply
Previous Topic: Re: problem restoring a save file from within a procedure
Next Topic: Re: annotations in a contour plot.

-=] Back to Top [=-
[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Wed Oct 08 15:17:26 PDT 2025

Total time taken to generate the page: 0.00479 seconds