Slashdot Mirror


Apple Switching to Intel

Steve Jobs announced at the WWDC keynote today that Apple is switching to Intel processors. MacNN has live coverage. The bottom line is that Mac OS X for the last five years has been running on Intel, the switch is expected to be complete in two years, and Rosetta will allow PPC apps to run on Intel-based Macs, transparently. If you're using Xcode, it is small changes and a recompile; otherwise, you might be seeing a lot of work ahead of you. You will be able to order the 10.4.1 preview for Intel today.

25 of 2,950 comments (clear)

  1. From Apple's PR site by doubleacr · · Score: 3, Informative
  2. Paste from Macworld..read before flaming by Danathar · · Score: 4, Informative

    The rumors are true: Intel will be inside

    Jobs talked about the major transitions in the Mac's life -- starting from the Mac's Motorola 68000-series processor to PowerPC. "The PowerPC set Apple up fro the next decade. It was a good move," he said.

    "The second transition was even better -- the transition from Mac OS 9 to Mac OS X that we just did," he continued. "This was a brain transplant. And even though these operating systems (9 and x) vary only by one in name, they are very different, and this has set Apple up for the next 20 years."

    As the Intel logo lowered on the stage screen, Jobs said, "We are going to make the transition from PowerPC to Intel processors, and we are going to do it for you now, and for our customers next year. Why? Because we want to be making the best computer for our customers looking forward."

    "I stood up here two years ago and promised you 3.0 GHz. I think a lot of you would like a G5 in your PowerBook, and we haven't been able to deliver that to you," said Jobs. "But as we look ahead, and though we've got great products now, and great PowerPC products still to come, we can envision great products we want to build, and we can't envision how to build them with the current PowerPC roadmap," said Jobs.

    Intel processors provide more performance per watt than PowerPC processors do, said Jobs. "When we look at future roadmaps, mid-2006 and beyond, we see PoweRPC gives us 15 units of perfomance per watt, but Intel's roadmap gives us 70. And so this tells us what we have to do," he explained.

    Transition to Intel by 2007, and yes, Marklar exists

    "Starting next year, we will introduce Macs with Intel processors," said Jobs. "This time next year, we plan to ship Macs with Intel processors. In two years, our plan is that the transition will be mostly complete, and will be complete by end of 2007."

    Jobs then confirmed a long-held belief that Apple was working on an Intel-compatible version of Mac OS X that some have termed "Marklar."

    Mac OS X has been "leading a secret double life" for the past five years, said Jobs. "So today for the first time, I can confirm the rumors that every release of Mac OS X has been compiled for PowerPC and Intel. This has been going on for the last five years."

    Jobs demonstrated a version of Mac OS X running on a 3.6GHz Pentium 4-processor equipped system, running a build of Mac OS X v10.4.1. He showed Dashboard widgets, Spotlight, iCal, Apple's Mail, Safari and iPhoto all working on the Intel-based system.

    Apple needs developers' help to complete the transition

    "We are very far along on this, but we're not done," said Jobs. "Which is why we're going to put it in your hands very soon, so you can help us finish it."

    Widget, scripts and Java applications should work in the new environment without any conversion, said Jobs. Cocoa-based applications will require "a few minor tweaks and a recompile." Carbon-based applications require "a few more tweaks," recompiling, and "they'll work," said Jobs. And projects built using Metrowerks' CodeWarrior need to be moved to Xcode.

    The future of Mac OS X development is moving to Xcode, said Jobs. Of Apple's top 100 developers, more than half -- 56 percent -- are already using Xcode, and 25 percent are in the process of switching to Xcode. "Less than 20 percent are not on board yet. Now is a good time to get on board," said Jobs.

    A new build of Xcode, version 2.1, is being released today. This new release enables developers to specify PowerPC or Intel architectures. "... and you're going to build what's called a universal binary. It contains all the bits for both architectures," said Jobs. "One binary, works on both PowerPC and Intel architecture. So you can ship one CD that supports both processors."

    "This is nothing like Carbonizing"

    Many developers reading this news may be thinking that they'll have to go through the same woes they had to in order to get their Mac OS 9 applications "Carbonized" to run on

    1. Re:Paste from Macworld..read before flaming by Danathar · · Score: 4, Informative

      Continued paste from Macworld...

      Rosetta keeps old apps running

      Jobs also discussed a new technology called Rosetta, that he described as "a dynamic binary translator." It runs existing PowerPC applications on the Intel platform, he said. Jobs described Rosetta as "lightweight," and said "it's nothing like Classic."

      Jobs demonstrated Rosetta by running Microsoft Office applications, Quicken and Photoshop CS 2 -- all unmodified PowerPC-binary versions, unlike Mathematica -- on the new Intel-based hardware.

      "So that is Rosetta, Jobs concluded. "These PowerPC apps just run. And that's what we're going to have for our users, because every app isn't going to be there for our users on day one."

      Microsoft's Roz Ho and Adobe's Bruce Chizen both took the stage to reaffirm their commitment to the Macintosh platform. Ho said that Microsoft has been "working with Apple for some time" to create future versions of Office using Apple's Xcode tools, and will create universal binaries accordingly." Chizen called Apple's decision to move to Intel "great," and gently chided Steve Jobs: "What took you so long?"

  3. Re:Holy crap. by cosmo7 · · Score: 4, Informative

    Here's Apple's press release.

    Dispel any remaining doubts; we are now living in the evil mirror universe.

  4. Re:You know what this means, Power PC Apple Users? by Radon+Knight · · Score: 4, Informative

    Possibly not - the new version of XCode builds universal binaries for both Intel and PPC. So, what's the problem again?

  5. Re:Have a taste... by Golias · · Score: 5, Informative

    You have plenty of time. The rumors were only half-true.

    Apple is adopting Intel, but is not "ditching" IBM.

    New G5 towers will still be around for at least another year, and probably at least two. Intel is probably going to start by replacing the G4 CPUs in Powerbooks and minis.

    At the Stevenote, he informed devs that they would be supporting both platforms for a long time to come.

    --

    Information wants to be anthropomorphized.

  6. Re:This is bullshit. by Redshift · · Score: 5, Informative

    1. If Rosetta works as well as demonstrated (Jobs showed unmodified PPC versions of Photoshop+filters and MS Office running happily and fast on the Intel Mac box) then this will be less painful than you think.

    2. The way the Intel and PowerPC raodmaps are going I think in three uears time there will be a HUGE difference in capability. Jobs was demoing a Pentium 3.6GHz quad for God's sake!

  7. Re:Apple getting out of hardware? by stickyc · · Score: 3, Informative
    Now that Apple has announced that it is moved to Intel, who is going to buy a G5 now?

    RTFA. The announcement is not that Apple is porting OS-X to run on ANY x86 box. It's that they're going to port it to run on THEIR x86 box. You're not going to be able to fire up OS-X on your Dell, Acer, Gateway, or eMachines PC. You're still going to be buying Apple's low-to-mid-range hardware (eMac line?). It's just going to have an Intel processor inside instead of the PPC. The release says they will be using the processor in their mid-range boxes, not their high-end boxes. So the demographic who will be buying the G5s in the future are be the same ones who're buying it now. People with a need for a stinky-fast machine that runs OS-X.

    Also does this mean I will be able to buy a Dell PowerEdge 2850 running Mac OSX Server?

    Not likely. See above.

  8. Re:This is bullshit. by mangu · · Score: 4, Informative
    so long as you weren't using any Altivec-heavy apps (since SSE is a poor replacement)


    Do you have any evidence to back this assertion? Generally speaking, Altivec in the G5 has the same function and performance as SSE2 in the Pentium 4. I use floating point functions that I have developed and coded in assembly language myself, and I don't see any difference between Altivec and SSE2 at the fundamental level.


    Most of the derogatory comments by Apple users about the supposed shortcomings of SSE2 are ill informed, they seem to confuse SSE2 with MMX. Optimization for either the Altivec or SSE2 is a complex subject. First, one has to find an algorithm that works well for vector operations, which means making sure that add and multiply operations will overlap correctly. Then one has to adapt that algorithm for the cache size, CPU clock, and memory bus cycle times. The main problem here is to avoid starving the cache. One has to balance how many operations are done by the CPU for each byte that comes from/to RAM and make sure that the timing is right. All these factors vary a lot between different CPU, mobo, and RAM models. To state that Altivec is either better or worse than SSE2 is simplistic, they are functionally identical and the relative performance between them will be determined by secondary factors.


    The biggest problem in SSE2 is that the only compiler that optimizes it well is Intel's, gcc sucks when generating code for the P4, but with hand-optimized code this is irrelevant. If the Intel architecture that Apple will adopt has SSE2, this could be very good news for developers. Let's hope Apple implements efficient optimization for SSE2.

  9. Re:So here it is - not just any PC platform by Anonymous Coward · · Score: 3, Informative

    C|Net has an update to their article with some more specific news regarding OSX on any old PC:
    "After Jobs' presentation, Apple Senior Vice President Phil Schiller addressed the issue of running Windows on Macs, saying there are no plans to sell or support Windows on an Intel-based Mac. "That doesn't preclude someone from running it on a Mac. They probably will," he said. "We won't do anything to preclude that."
    However, Schiller said the company does not plan to let people run Mac OS X on other computer makers' hardware. "We will not allow running Mac OS X on anything other than an Apple Mac."

  10. Re:So here it is by Queer+Boy · · Score: 4, Informative
    Is apple going to sell prototypes of Apple Intel systems to any developer who wants to test their app?

    Yes, you should have read all the keynote transcripts. They did the same thing when the PowerPC came out, developers were given prototype 6100s as part of their developer kit.

    --
    Not since Marie-Antoinette played milkmaid has looking simple and honest been so fake and complicated.
  11. Re:So here it is by MustardMan · · Score: 5, Informative

    As others have pointed out elsewhere in this thread, the dev kit includes the hardware. They aren't just shipping a Tiger CD you pop into your dell.

  12. Re:This is bullshit. by WhiteWolf666 · · Score: 3, Informative

    Oh, I see.

    Thats why I run World of Warcraft, Half Life 2, and Farcry, on my AMD64 box, at *native* speeds, in SuSE 9.3.

    With Cedega, a Wine derivative.

    No, not any Windows software.

    But lots of Windows software works *very* well under Wine, even Direct3D apps.

    --
    WhiteWolf666 an exBush supporter. All you new-school,compassionate,save the children Republicans can rot in hell
  13. Re:It makes sense though... by boarder · · Score: 3, Informative

    Is there a 64-bit x86 laptop available now?

    Yes.
    Many.
    at walmart even

    --
    IANAL, but I play one on /.
  14. Re:So much for YellowDog by zapp · · Score: 3, Informative

    As one of the few Terra Soft / slashdotters, it is my pleasure to represent the company on this situation:

    I guess you're wrong.

    This is a change, and a big change at that, but our business has changed before, and we're fighters. Apple isn't the only company producing PPC hardware, and we already have established business connections with several other PPC-based manufaturers.

    -AJ

    --
    no comment
  15. Wrong...will actually make native OOo wait longer by soullessbastard · · Score: 4, Informative

    Disclaimer: I am an OpenOffice.org Mac OS X devleoper and a founder of the NeoOffice project

    Quote: This means OpenOffice.org 2.0 will work *now*. This means no more second-class Mac versions of popular OS apps.

    This statement couldn't actually be farther from the truth. In fact, it will actually make the push for OpenOffice.org, at least, more difficult. If you dig into the details it means there's much more work ahead:

    • Most Unix based apps don't use XCode. Just about all Linux and Unix derived applications use command line build systems. According to the information from Apple, universal binary support only applies to XCode based projects. With hundreds of thousands of files and a custom build system, it would take years just to get OpenOffice.org to build with XCode and it may not even be possible.
    • Delivery of fat binaries is impractical for large open source applications. A single platform binary of OOo already clocks in at greater than 100 MB. People already complain about that size. A true integrated universal binary would probably close to double that size (though perhaps less due to use of cisc). Downloaders will love that.
    • To compile will require the use of GCC 4.0. I don't know about other projects, but moving OpenOffice.org to new GCC versions is a real pain in the butt. Code doesn't compile, options change, the way things link change, but, more importantly...
    • Apple is using their own ABI. OpenOffice.org requires knowledge of the ABI in order to get UNO objects to communicate (the OOo incarnation of COM). This ABI glue is coded in assembly and is unique for each compiler on each architecture (e.g. the gcc 2 C++ ABI is different from 3, which is different from 4, etc.). Since Apple is using their own ABI, code from Linux or Windows can't simply be moved over even if it is the same compiler. No work can begin on an Intel port until the ABI is solidified.
    • Linux apps don't use Carbon/Cocoa. The transition to a native OpenOffice.org will still require the type of work we're doing in the NeoOffice project, the piecemeal replacement of X11 dependencies with native code. Most people who speak of a native OOo on a Mac don't give a hoot about X11, they want the one with the blue buttons.
    • Apple isn't offering hardware to people not in their developer programs. Few contributors to open source projects have funds already, but the fact that one has to be a member of one of their paying developer programs will make it even more difficult for Mac open source contributors to get a grasp on the Intel switch. It was bad enough with Tiger where we didn't have access to test things before it got released, and that was just software!

    Changing processors does nothing to help OpenOffice.org development on Mac OS X except slow it down yet again. Chances are you'll probably see it running in an emulator for a long time before it's running on Mactel hardware.

    ed

  16. No, Dvorak was wrong by btarval · · Score: 3, Informative
    Here's some crow for Dvorak, and is what first came up from a quick google search on his predictions for Apple:

    Note the date: 03.18.03:
    "Apple Computer Corp. will switch to Intel processors within the next 12 to 18 mo nths."

    Oops. Nope, he's wrong here; off by a few years.

    "Apple will announce its Intel initiative by showing a transition machine that us es both the Intel and Motorola processors."

    No, wrong again. None of this dual-core nonsense; it's all or nothing.

    "Apple will announce its use of the Itanium chip,"

    This is funny. Even back in 2003 it was clear that the Itanium was a dog, doomed to fail.

    "Waiting until 2004 is too risky,"

    Heh. Enough said.

    Like someone else said, even a broken clock is right twice a day. So, just refer back to his previous predictions if Dvorak gets too smug for you.

    --
    The best way to predict the future is to create it. - Peter Drucker.
  17. Apple posts Intel docs; No OpenFirmware on x86 by Knytefall · · Score: 4, Informative

    Apple posted Intel Universal Binary documentation to their website. It's interesting, and everyone should read it. Notable is a caveat that OpenFirmware is going away. That seems to point towards more standard hardwware.

  18. CISC, RISC, and MMX by Creepy · · Score: 4, Informative

    Quite simply, Intel no longer uses CISC. Sure the instruction set is CISC, but it's all microcode reduced to RISC instructions underneath the hood (which was done WAAAY back with the Pentium II and may have partially been implemented on the original Pentium). MMX has been dead for a while, replaced by SIMD and SIMD2, which can actually run in parallel to the floating point unit and no longer requires a context switch. Seriously, though, outside of the math world, you probably don't need either unless you're doing software rendering of graphics - the original reason for MMX was to speed up processing of games and video effects in software and this work is now pretty much entirely handled by the GPU.

  19. Re:This is bullshit. by ArbitraryConstant · · Score: 3, Informative

    "1. If Rosetta works as well as demonstrated (Jobs showed unmodified PPC versions of Photoshop+filters and MS Office running happily and fast on the Intel Mac box) then this will be less painful than you think."

    Anything CPU intensive will be iffy on Intel processors, and emulation of Altivec code is explicitly
    not supported by Rosetta.

    ". The way the Intel and PowerPC raodmaps are going I think in three uears time there will be a HUGE difference in capability. Jobs was demoing a Pentium 3.6GHz quad for God's sake!"

    That was a single processor machine.

    It'll be okay for most legacy apps, but anything that actually cares how fast a machine is will have to be native. There is no way around this.

    Also, while Intel processors will be faster per watt, a given thread will not be faster. All the CPU manufacturors have hit a performance wall in terms of how much work can be done in one processor, and even if you have a dual-core dual-CPU machine, one thread will have to run on one core, and under emulation that means every thread will be slower.

    --
    I rarely criticize things I don't care about.
  20. Re:Have a taste... by TylerL82 · · Score: 4, Informative

    According to Apple's Universal Binary whitepaper (http://developer.apple.com/documentation/MacOSX/C onceptual/universal_binary/universal_binary.pdf), the Intel Macs will NOT be using Open Firmware...

    I can't wait to see what people are able to do (legitimately or not) with the x86 dev boxes...

  21. Re:Intel yes, Pentium no by demon · · Score: 3, Informative

    If you saw the video of the keynote, you'd know that Jobs was running the entire presentation from a system running Mac OS X - a Pentium 4 system, specifically. He even showed off the "About this Mac" window that showed it in no uncertain terms. So yes, this does mean Pentium 4 (maybe Pentium M for laptops) systems running OS X.

    --

    Sam: "That was needlessly cryptic."
    Max: "I'd be peeing my pants if I wore any!"
  22. Re:This is bullshit. by LionMage · · Score: 3, Informative
    Well, it's funny you should mention this, as Apple today published the Universal Binary Programming Guidelines on their developer site. I took a gander through this document, and noticed that a good percentage of it dealt with the differences between vector processing in the two architectures. Some choice quotes:
    Before you start
    rewriting AltiVec instructions for the Intel instruction set architecture, read "Differences Between Instruction Set Architectures" (page 54). If the differences impact your code a great deal, you may want to consider simply rewriting your code to use the Accelerate framework.

    To Apple's credit, they are providing a nice API to take the drudgery out of writing your own vector code; they call it the Accelerate framework, and it's been around since 10.3.

    Speaking of differences between AltiVec and SSE/SSE2/SSE3:
    • Integer multiplication algorithms are not equivalent.
      AltiVec has 13 or so different flavors of integer multiplication with variations. The x86 architecturehas 3 with almost no variations. In certain cases, algorithms designed to showcase the AltiVec multiply-accumulate facility need to be rewritten to showcase the x86 multipliers.
    • There is no direct translation for vec_perm.
      There is no way to perform a permute operation on x86 for which the permute map is unknown at compile time. Some byte permutes are also not possible. Operations like byte swapping in an SIMD register, using the permute unit as a lookup table, and using the permute unit to handle alignment simply don't work, or require a prohibitive amount of computation.
      Vectorization may not be possible for AltiVec code such as small lookup tables that rely heavily on vec_perm(). There is a permute-like shuffle facility (SHUFPS, SHUFPD, PSHUFD, PSHUFLW, PSHUFHW) available. However, the permute map must be determined at compile time, meaning that no run time decisions can be made about how to shuffle the data.
    • There are no fused multiply-add operations.
    • There are no x86 counterparts to vec_splat_u8() and vec_lvsl() for generating vector constants.
      Most vector constants must be loaded from storage. A few such as 0 and -1 can be created with clever application of XOR and the vector compare instructions.

    I haven't covered all the bulleted items, just the ones that were of interest to me. I also found the following interesting:
    AltiVec only performs aligned loads and relies on a patented permute crossbar to extract a misaligned vector from the two bracketing aligned vectors. While x86 provides aligned vector loads, it doesn't have a permute operation. The long vector left and right shifts take immediate arguments that must be determined at compile time, as do the shuffle instructions. As a result, it is not easy to perform software alignment. The x86 architecture instead provides hardware support for misaligned vector loads and stores.

    So, yeah, there are some of the big glaring differences between SSE/SSE2/SSE3 and AltiVec/VMX. Some of the differences are just that, differences. Others are a pain. I have a feeling more developers are going to rely on Apple's abstraction framework rather than hand-tweaking vectorized code, or else they'll rely on auto-vectorization from the compiler. For pre-existing code, though, it's going to be a bitter pill to swallow; nobody wants to throw out painstakingly hand-optimized vector code.
  23. Re:Wrong...will actually make native OOo wait long by sidb · · Score: 4, Informative

    Apple's gcc supports universal (fat) binaries. XCode uses gcc for compilation, but it's just a wrapper. Gcc still works fine without it.

  24. Re:You're right.... dammit! by nikster · · Score: 4, Informative

    These new x86 processors have way more innovation in them than the 10 year old new and clean design of the PPC. They are not CISC processors anymore in that they internally are RISC/CISC hybrids. The PPC has grown in the other direction, and is now also a RISC/CISC hybrid.

    From an architectural standpoint, PPC is still a lot cleaner than x86. But the immense brainpower and $ that Intel has put behind x86 made it into something that is hard to beat even with a cleaner design.

    In the end, it's a matter of priorities: Intel had to go low-power and had the resources to develop this technology while the company line was going in the exact opposite direction (P4). Now they are killing with it. Even AMD is way behind regarding low power chips.
    IBM never wanted to commit the resources or people to make the G5 portable. They would have had to spend serious money - chip design is extremely expensive - and hire very very good people. IBM never had this commitment.

    Besides, I have this feeling that the G5 was designed with some P4-envy in mind: Huge pipeline, high clock speeds. And using lots of power and generating lots of heat... Intel had the Pentium-M as a 'plan B' for this boneheaded strategy, whereas Apple/IBM did not.