Mac OS 8.2 Beta! As most of you know I collect a lot of old Macs. Well today I found one in the attic that I forgot I had there, a PowerMac 7100. Well I went to boot it up and noticed something odd. The startup screen said 'Welcome to Mac OS Debugger Installed'. I wondered what that ment. MacOS Big Sur elevates the most advanced desktop operating system in the world to a new level of power and beauty. Experience Mac to the fullest with a refined new design. Enjoy the biggest Safari update ever. Discover new features for Maps and Messages. And get even more transparency around your privacy. Mac OS V666 is a horror operating system of Macintosh. Back in 1988, a guy named Richard Perkins was going to a thrift store, a store that has a lot of old stuff. He sees a Macintosh computer and it says 'Mac 666'. Richard wanted to buy it but the cashier says 'Beware young man, this OS is cursed like hell, it might haunt you!' Richard seems he doesn't believe it and he buys it, while going. By PlaNet-3 Software Grapple is a string finder for the Mac that is both friendly and intuitive to use.

• Grapple Man (prototype) Mac Os X
• Grapple Man (prototype) Mac Os 7
• Grapple Man (prototype) Mac Os 8
• Grapple Man (prototype) Mac Os Catalina
• Grapple Man (prototype) Mac Os X

macOS Big Sur elevates the most advanced desktop operating system in the world to a new level of power and beauty. Experience Mac to the fullest with a refined new design. Enjoy the biggest Safari update ever. Discover new features for Maps and Messages. Get even more transparency around your privacy.

Chances are, your Mac can run macOS Big Sur

The following models are supported:

• MacBook (2015 or later)
• MacBook Air (2013 or later)
• MacBook Pro (Late 2013 or later)
• Mac mini (2014 or later)
• iMac (2014 or later)
• iMac Pro (2017 or later)
• Mac Pro (2013 or later)

To see which model you have, click the Apple icon in your menu bar and choose About This Mac.

Make sure you’re ready to upgrade.

Before you upgrade, we recommend that you back up your Mac. If your Mac is running OS X Mavericks 10.9 or later, you can upgrade directly to macOS Big Sur. You’ll need the following:

• OS X 10.9 or later
• 4GB of memory
• 35.5GB available storage on macOS Sierra or later*
• Some features require an Apple ID; terms apply.
• Some features require a compatible Internet service provider; charges may apply.

Upgrading is free and easy

Upgrading from macOS Catalina 10.15 or Mojave 10.14?

Go to Software Update in System Preferences to find macOS Big Sur. Click Upgrade Now and follow the onscreen instructions.

Upgrading from an older version of macOS?

If you’re running any release from macOS 10.13 to 10.9, you can upgrade to macOS Big Sur from the App Store. If you’re running Mountain Lion 10.8, you will need to upgrade to El Capitan 10.11 first.

• OS X 10.9 or later
• 4GB of memory
• 35.5GB available storage on macOS Sierra or later*

• Some features require an Apple ID; terms apply.
• Some features require a compatible Internet service provider; charges may apply.

For details about your Mac model, click the Apple icon at the top left of your screen and choose About This Mac. These Mac models are compatible with macOS Big Sur:

• MacBook (2015 or later)
• MacBook Air (2013 or later)
• MacBook Pro (Late 2013 or later)
• Mac mini (2014 or later)

• iMac (2014 or later)
• iMac Pro (2017 or later)
• Mac Pro (2013 or later)

Siri

Requires a broadband Internet connection and microphone (built-in or external).

Hey Siri

Supported by the following Mac models:

• MacBook Pro (2018 or later)
• MacBook Air (2018 or later)
• iMac Pro (2017 or later)

Dictation, Voice Control and Voice Memos

Requires a microphone (built-in or external).

Spotlight Suggestions

Requires a broadband Internet connection.

Gestures

Requires a Multi-Touch trackpad, Force Touch trackpad, Magic Trackpad or Magic Mouse.

Force Touch gestures require a Force Touch trackpad.

VoiceOver gestures require a Multi-Touch trackpad, Force Touch trackpad or Magic Trackpad.

Photo Booth

Requires a FaceTime or iSight camera (built-in or external), or USB video class (UVC) camera.

FaceTime

Audio calls require a microphone (built-in or external) and broadband Internet connection.

Video calls require a built-in FaceTime camera, an iSight camera (built-in or external), or a USB video class (UVC) camera; and broadband Internet connection.

Apple TV

High dynamic range (HDR) video playback is supported by the following Mac models:

• MacBook Pro (2018 or later)
• iMac Pro (2017 or later)
• Mac Pro (2019) with Pro Display XDR

Dolby Atmos soundtrack playback is supported by the following Mac models:

• MacBook Air (2018 or later)
• MacBook Pro (2018 or later)

Sidecar

Supported by the following Mac models:

• MacBook (2016 or later)
• MacBook Air (2018 or later)
• MacBook Pro (2016 or later)
• Mac mini (2018 or later)
• iMac (late 2015 or later)
• iMac Pro (2017 or later)
• Mac Pro (2019)

Supported by all iPad models with Apple Pencil support:

• 12.9-inch iPad Pro
• 11-inch iPad Pro
• 10.5-inch iPad Pro
• 9.7-inch iPad Pro
• iPad (6th generation or later)
• iPad mini (5th generation)
• iPad Air (3rd and 4th generation)

Continuity Camera

Requires an iPhone or iPad that supports iOS 12 or later.

Continuity Sketch and Continuity Markup

Requires an iPhone with iOS 13 or later or an iPad with iPadOS 13 or later.

Handoff

Requires an iPhone or iPad with a Lightning connector or with USB-C and iOS 8 or later.

Instant Hotspot

Requires an iPhone or iPad with cellular connectivity, a Lightning connector or USB-C, and iOS 8.1 or later. Requires Personal Hotspot service through your carrier.

Universal Clipboard

Requires an iPhone or iPad with a Lightning connector or with USB-C and iOS 10 or later.

Auto Unlock

Requires an Apple Watch with watchOS 3 or later or an iPhone 5 or later.

Approve with Apple Watch

Requires an Apple Watch with watchOS 6 or later or an iPhone 6s or later with iOS 13 or later.

Phone Calling

Requires an iPhone with iOS 8 or later and an activated carrier plan.

SMS

Requires an iPhone with iOS 8.1 or later and an activated carrier plan.

Home

Requires an iPhone with iOS 12 or later and a configured Home app.

AirDrop

AirDrop to iOS and iPadOS devices requires an iPhone or iPad with a Lightning connector or with USB-C and iOS 7 or later.

AirPlay

AirPlay Mirroring requires an Apple TV (2nd generation or later).

AirPlay for web video requires an Apple TV (2nd generation or later).

Peer-to-peer AirPlay requires a Mac (2012 or later) and an Apple TV (3rd generation rev A, model A1469 or later) with Apple TV software 7.0 or later.

Time Machine

Requires an external storage device (sold separately).

Maps electric vehicle routing

Requires an iPhone with iOS 14 and a compatible electric vehicle.

Maps number plate restrictions

Requires an iPhone running iOS 14 or an iPad running iPadOS 14.

Boot Camp

Allows Boot Camp installations of Windows 10 on supported Mac models.

Exchange Support

Requires Microsoft Office 365, Exchange 2016, Exchange 2013 or Exchange Server 2010. Installing the latest Service Packs is recommended.

Windows Migration

Supports OS X 10.7 or later and Windows 7 or later.

App Store

Available only to persons aged 13 or older in the US and many other countries and regions.

Photos

The improved Retouch tool is supported on the following Mac models:

• MacBook Pro (15-inch and 16-inch models) introduced in 2016 or later
• iMac (Retina 5K models) introduced in 2014 or later
• iMac (Retina 4K models) introduced in 2017 or later
• iMac Pro (2017 or later)
• Mac Pro introduced in 2013 or later

• Apple Books
• Apple News
• App Store
• Automator
• Calculator
• Calendar
• Chess
• Contacts
• Dictionary
• DVD Player
• FaceTime
• Find My
• Font Book
• Home
• Image Capture
• Launchpad
• Mail
• Maps

• Messages
• Mission Control
• Music
• Notes
• Photo Booth
• Photos
• Podcasts
• Preview
• QuickTime Player
• Reminders
• Safari
• Siri
• Stickies
• Stocks
• System Preferences
• TextEdit
• Time Machine
• TV
• Voice Memos

• Activity Monitor
• AirPort Utility
• Audio MIDI Setup
• Bluetooth File Exchange
• Boot Camp Assistant
• ColorSync Utility
• Console
• Digital Color Meter
• Disk Utility

• Grapher
• Keychain Access
• Migration Assistant
• Screenshot
• Screen Time
• Script Editor
• Sidecar
• System Information
• Terminal
• VoiceOver Utility

• Arabic
• Catalan
• Croatian
• Simplified Chinese
• Traditional Chinese
• Traditional Chinese (Hong Kong)
• Czech
• Danish
• Dutch
• English (Australia)
• English (UK)
• English (US)
• Finnish
• French
• French (Canada)
• German
• Greek
• Hebrew
• Hindi
• Hungarian

• Indonesian
• Italian
• Japanese
• Korean
• Malay
• Norwegian
• Polish
• Brazilian Portuguese
• Portuguese
• Romanian
• Russian
• Slovak
• Spanish
• Spanish (Latin America)
• Swedish
• Thai
• Turkish
• Ukrainian
• Vietnamese

These notes are for the MacOS X 10.3 Release of the compilertools. They contain information about the following topics:

• The Mac OS X Mach-O GNU-based assemblers
• The Mac OS X Mach-O static link editor
• The Mac OS X Mach-O dynamic link editor
• Mach-O object file tools (nm, otool, and so on)

Notes Specific to Mac OS X 10.3 Release

New Features

The static linker as option to find@executable_path dynamic libraries

Added the -executable_path path_name option told(1) where path_name is is used to replace@executable_path for dependent libraries.

Notes Specific to Mac OS X June 2003 Developer Release

New Features

The compiler tools now support the PowerPC 970processor

The compiler tools now support the PowerPC 970 processor. Thearchitecture specific flag -arch ppc970 is used to specifythis specific processor. The assembler will only assemble 64-bitinstructions and other PowerPC AS User Instruction Set ArchitectureVersion 2.00 instructions supported by the PowerPC 970 processor when-arch ppc970 or -force_cpusubtype_ALL is specified.

To specify branch predictions which use the AT bit encodings forThe branch is very likely to be taken and The branch isvery likely not to be taken the two character suffixes ++ and --are used. For example:

bge-- foo

The single character suffixes + and - continue to encode branchpredictions which use the Y-bit encoding by default. The encoding canbe changed for the single character suffixes to use the AT bitencodings with the assembler flag-static_branch_prediction_AT_bits (see the as(1) manpage for more details).

The compiler tools now support stublibraries

The compiler tools now support stub libraries created from dynamiclibraries which are used in the SDKs. Stub libraries are created viastrip(1) and the new -c option. And can be linkedagainst in place of the actual dynamic library.

The static linker now can search for librariesfirst in the library paths

By default when the -dynamic flag is in effect, the-lx and -weak-lx options first search fora file of the form libx.dylib in each directory in the librarysearch path, then a file of the form libx.a is searched for inthe library search paths. The new option -search_paths_firstchanges it so that in each path libx.dylib is searched forthen libx.a before the next path in the library search path issearched.

The static linker now supports forcing a dynamiclibrary to be weak

Added the -weak_framework, -weak_library and-weak-l options to ld(1) to force the dynamic libraryand the symbols referenced from it to be marked as weak imports. Seethe ld(1) man page for more details.

The static linker now has a work around for nothaving dead code stripping

Added the -undefined define_a_way option to ld(1) asa work a round to not having dead-code stripping that also strips outreferences to undefined symbols from the dead code. Which leads tolink time failures due to undefined symbols. With this optionld(1) defines the remaining undefined symbols as privatedefinitions and allows the link to succeed. The program then runs aslong as it does not use any of the undefined symbols.

Notes Specific to Mac OS X November 2002 Developer Release

New Features

Exports lists can now be specified to the staticlinker

The static link editor, ld(1), now has two new options,-exported_symbols_list filename and-unexported_symbols_list filename to limit theglobal symbols in the linked output file. This was previously done bywith an nmedit(1). By using the new options to ld(1)the use of nmedit(1) can be eliminated resulting in fasterbuild times.

Grapple Man (prototype) Mac Os X

The static linker now can build single moduledynamic libraries

The static link editor, ld(1), now has a new option,-single_module, to build a dynamic library containing only onemodule. This was previously done by first creating a master.o filewith an ld(1) -r step and then using the master.o tocreated the dynamic library. By using the new -single_moduleoption to ld(1) this first step can be eliminated resulting infaster build times.

The default in the static link editor remains the same and dynamiclibraries are built with multiple modules. The new flag-multi_module has also been added to allow this to beexplicitly specified.

The static linker's -s option now works likestrip on dynamic executables

The static link editor's -s option can now be used to stripan executable that use the dynamic link editor. This will produce thesame result as running strip(1) with no options on theexecutable. By using the -s option when building an executablethe strip(1) step can be eliminated resulting in faster buildtimes.

Notes Specific to Mac OS X 10.2 Release

The compiler tools for the MacOS X 10.2 Release must be used withprebound images (executables, and shared libraries) from the MacOS X10.2 User Release. The compiler tools in MacOS 10.1 will not workwith prebound images from with the MacOS X 10.2 User Release. If the10.1 compiler tools are used on prebound images from the MacOS X 10.2User Release the compiler tools will generate error messagesindicating that the image is a malformed file.

New Features

The dynamic linker now supports weak referencesand weak dylibs

The dynamic linker now supports weak symbol references and weakdymamic libraries. When creating a binary with the static link editorif all the symbols referenced from a given dependent dynamic libraryare weak references then the library is marked weak. When the binaryis used at execution time and a weak library is missing the dynamiclinker will not cause an error. For all weak symbols that are missingexecution time the dynamic linker uses zero as their address. Thisallows a weak symbol's address to be tested for zero at runtimeallowing the code to avoid using the weak symbol when it is missing.Binaries that use weak references require a dynamic linker from MacOS X 10.2 or later.

To indicate a symbol is to be a weak reference the__attribute((weak_import)) is used on the prototype of the symbol.When a binary is created by the static link editor normally the allthe undefined symbol references of the object files being linkedshould be consistent for each undefined symbol. That is all undefinedsymbols should either be weak or non-weak references. If they are notby default this is treated as an error and can be changed with theld(1) -weak_reference_mismatchestreatment flag (seethe ld(1) man page for more details).

Weak referenced symbols and weak libraries are only created in theoutput by the static link editor, ld(1), when theMACOSX_DEPLOYMENT_TARGET environment variable is set to 10.2. If nota warning is generated when a weak reference would be in the outputand it is not marked weak. Note the default for theMACOSX_DEPLOYMENT_TARGET environment variable 10.1 so weak referencedsymbols and weak libraries are not created by default. See theld(1) man page for more information on theMACOSX_DEPLOYMENT_TARGET environment variable.

redo_prebinding can now slide dylibs

The redo_prebinding(1) command now can slide dymamic libraries tonew prefered addresses (see the man page for more details).

Notes Specific to Mac OS X 10.1 Release

You must use the 10.1 compiler tools with images (executables,plugins and shared libraries) created with the 10.1 tools. Thecompiler tools in MacOS 10.0 will not work with images created withthe 10.1 compiler tools. If you attempt to use the 10.0 compilertools on images created with the 10.1 compiler tools, error messagesmay result indicating that the image is a malformed file.

By default the compiler tools build images using the new two-levelnamespace binding semantics, which has important consequences forcompatibility with Mac OS X 10.0 (see belowfor more information).

New Features

The following new features have been added to the Compiler Toolsfor the Mac OS X 10.1 system release.

• The compiler tools now support two-level namespaces for binding undefined references from shared libraries. In flat namespace images, all symbols are referenced globally using a single name table. In two-level namespace images, symbols are referenced by library name and symbol name. This prevents multiple-defined-symbol errors when one image exports the same symbol as another image in the same program. You must rebuild your applications and plugins to take advantage of this feature, and there are compatibility restrictions with Mac OS X 10.0 that you should understand. For more information see the ld(1) man page and the two-level namespace release note.
• The dynamic linker now has API's for doing two-levelnamespace lookups. They are NSAddImage(), NSLookupSymbolInImage() and NSIsSymbolNameDefinedInImage(). For more information see the NSModule(3) man page. [This fixes Apple bug number 2689833.]
• Prebinding is now documented in a release note. [This fixes Apple bug number 2611234.]

Notes Specific to Mac OS X 10.0 Release

• There are no notes specific to the Mac OS X 10.0 release of the compiler tools.

Notes Specific to Mac OS X Public Beta Release

New Features

The following new features have been added to the Compiler Toolssince the Mac OS X Developer Release 4.

• The dynamic linker now calls shared library initialization routines in their dependent order (reference number 2441683).
• The new function __initialize_Cplusplus() now can be called from a shared library initialization routine to cause the static C++ objects in the library to be initialized. This allows shared library initialization routines to make use of statically initialized C++ objects (reference number 2441683).
• The dynamic linker now supports module termination functions for all types of images (executables, plugins that are not unloaded and shared libraries). See the decription below as part of the notes specific to Mac OS X Developer preview of module termination functions (reference number 2469527).
• The compiler tools support the new directory layout for MacOS X Public Beta. The new location for Frameworks local to the machine is /MacOSX/Library/Framework (in DP4 and previous releases this was /Local/Library/Frameworks).

Notes Specific to Mac OS X Developer Release 4

• There are no notes specific to the compiler tools for Developer Release 4.

Notes Specific to Mac OS X Developer Release 3

New Features

The following new features have been added to the Compiler Toolssince the Mac OS X Developer Release 2.

• The static linker supports removing duplicate debugging information from header files when this information appears in multiple linked object files. This is done with the -Si option to the static link editor and is now the default. To have no symbols stripped when linking use the new -Sn option.

Notes Specific to Mac OS X Developer Release 2

New Features

The following new features have been added to the Compiler Toolssince the Mac OS X Developer Preview Release.

• Dynamic shared libraries now can have a dynamic shared library initialization routine (reference number 2367584). This routine is specified to libtool(1) with the new '-init symbol_name' argument. The library initialization routine is called before any symbol is used from the library including C++ static initializers (and #pragma CALL_ON_MODULE_BIND routines). So the code in a library initialization routine or code called by it can not depend on C++ static initializers. Also code in a library initialization routine or code called by it can not call any of the dynamic linker API, <mach-o/dyld.h>, otherwise that could result in more than one library initialization routine being partially executed on the stack.
• The dynamic linker now supports shared library install names that start with '@executable_path/' and substitutes the directory path of the executable for '@executable_path/'when locating the library. This requires a kernel from Mac OS X Developer Release 2 or later. Without that kernel, this feature can only be used if argv[0] is in fact the name of the executable and it is an absolute path or relative to the current directory (contains at a '/' in the argv[0] string).
• The NSLinkModule() API now has an option to cause it to return when there is an error loading the module and a new API NSLinkEditError() to get the error information. To use this the constant NSLINKMODULE_OPTION_RETURN_ON_ERROR needs to be or'ed into the options parameter to NSLinkModule(). Then if NSLinkModule() returns NULL the error information can be retrieved with NSLinkEditError().

  The NSLINKMODULE_OPTION_RETURN_ON_ERROR option is an alternative method to the existing dyld error handling which fits better with a plugin model. With the NSLINKMODULE_OPTION_RETURN_ON_ERROR option, the model for handling errors is to simply return without any changes to the program. To support this model of error handling a new API has been added to allow the programmer to get the error information that the dyld error handlers would normally have gotten. The API is similar to the dyld linkEdit error handler except that all the parameters are passed as pointers to be filled in.

  • extern void NSLinkEditError(
    NSLinkEditErrors *c,
    int *errorNumber,
    const char **fileName,
    const char **errorString);

  The last two parameters return pointers to static buffers allocated in the dynamic linker which get reused on subsequent calls to NSLinkEditError(). The NSLinkEditErrors enum has been extended to include NSLinkEditUndefinedError and NSLinkEditMultiplyDefinedError.

Notes Specific to Mac OS X Developer Preview Release

New Features

The following new features have been added to the Compiler Toolssince the Mac OS X Server Release.

• The NSLinkModule() API now can create private modules and the new API NSLookupSymbolInModule() allows symbols to be looked up in a private module. To do this the interface to NSLinkModule() has changed in a compatible way from:
  • extern NSModule NSLinkModule(
    NSObjectFileImage objectFileImage,
    const char *moduleName,
    enum bool bindNow);

  to:

  • extern NSModule NSLinkModule(
    NSObjectFileImage objectFileImage,
    const char *moduleName,
    unsigned long options);

  with the options as follows:

  • #define NSLINKMODULE_OPTION_NONE 0x0
    #define NSLINKMODULE_OPTION_BINDNOW 0x1
    #define NSLINKMODULE_OPTION_PRIVATE 0x2

  The first two are the same as bindNow with a value of FALSE and TRUE. The private options are used to load a private module. The API for getting to the symbols of a NSModule that has been privately linked is:

  • extern NSSymbol NSLookupSymbolInModule(
    NSModule module,
    const char *symbolName);

  Then to get the address of the returned NSSymbol, the existing NSAddressOfSymbol() API can be used.

  The NSUnLinkModule() API is now implemented with enough functionality to make Apache work (reference number 2262020). It currently has the following limitations (to be fixed in future releases):

  • only works for plugins (can only be called on modules that were returned by NSLinkModule).
  • C++ plugins that have a static destructor can't be unloaded. The program will crash in atexit(3) when the unlinked destructor is attempted to be called.
  • Objective-C plugins should not be unloaded. The Objective-C runtime has not been updated to know about unloading and the result is very likely to crash the program.
  • The debugger has not been updated to know about unloading and trying to debug a program that unloads its plugins may confuse or crash the debugger.

  The interface to NSUnLinkModule has changed in a compatible way from:

  • extern enum bool NSUnLinkModule(
    NSModule module,
    enum bool keepMemoryMapped);

  to:

  • extern enum bool NSUnLinkModule(
    NSModule module,
    int options);

  where the options are:

  • #define NSUNLINKMODULE_OPTION_NONE 0x0
    #define NSUNLINKMODULE_OPTION_KEEP_MEMORY_MAPPED 0x1
    #define NSUNLINKMODULE_OPTION_RESET_LAZY_REFERENCES 0x2

  The first two are the same as keepMemoryMapped with a value of FALSE and TRUE. The reset lazy references option allows unloading modules with only call sites to undefined functions (direct calls, not calls through pointers) to not cause an undefined symbol error. Then if a subsequent module is loaded that defines symbols that were previously undefined, the call sites will use the new definitions. This is currently only implemented for PowerPC.

  Support for module termination functions has been added for plugins (only). Currently the compiler pragma CALL_ON_UNLOAD (as well as CALL_ON_LOAD) is not yet implemented to use this feature as intended. A work around can be done in place of having the pragma:

  • void my_term(void)
    {
    /* do module termination */
    }
    /* #pragma CALL_ON_UNLOAD my_term */
    #pragma SECTION data '.section __DATA, __mod_term_func, mod_init_funcs'
    static void (*dummy)(void) = my_term;
    #pragma SECTION data

Notes Specific to Mac OS X Server Release

New Features

The following new features have been added to the Compiler Toolssince the Rhapsody Developer Release 2.

• The 4.4bsd ar extended format #1 is now supported by the compiler tools. The default is to use 4.4bsd ar extended format #1 when creating static archives whose member names are longer than 16 characters or have spaces in the name. The tools that create static archives, ar(1), libtool(1) and ranlib(1), all take the options -T (to truncate member names) and -L (to used long member names, the default) (reference 1670513).
• The AltiVec opcodes have been added to the Mac OS X PowerPC assembler. To assemble files with these instructions it requires the option -force_cpusubtype_ALL and then it is the code's responsibility to only use these instructions when the CPU supports them. (references 2237908, 2227999, 2213821, 2004760).
• The header file <mach-o/getsect.h> has been added to the system as the proper place to get the prototypes of the Mach-O routines. (reference 2227839).

There are no Notes Specific to Rhapsody Developer Release 2

Notes Specific to Rhapsody Developer Release

New Features

The following new features have been added to the compiler toolssince OPENSTEP 4.2 (NeXT).

• The PowerPC architecture is now supported via the -arch ppc switch.
  

Known Problems

These bugs are known to exist in the compiler tools:

Grapple Man (prototype) Mac Os 7

Bugs Fixed

The following bug has been fixed:

PowerPC Assembly Instruction Parameter Differences

Register names can't be designated with just a number. You mustrefer to them with their register name. This restriction includesgeneral registers (rN), floating point registers,(fN), condition registers(crN), and segment registers(srN). However, you can refer to specialregisters by their register number or their special register names.The special register names are in lowercase only (for example,mq, xer, lr, ctr,and dsisr).

For instance, for the ppcasm assember you could code a movefrom segment register instruction as:

But, for the Mac OS X assembler, this same move would be codedas:

For instructions that take the value 0 or a register, shown in theprocessor manual as '(rA 0)', r0 can't be used and 0 must be coded.The Mac OS X assembler generates an error messages in thesecases.

Where a numeric value is expected as a parameter, a register namecan't be use. For example, the ppcasm assembler allows thefollowing:

Grapple Man (prototype) Mac Os 8

For Mac OS X, this must be coded as:

The Mac OS X assembler generates a warning if branch prediction iscoded with an unconditional branch.

The Mac OS X assembler checks all fields for range errors andgenerates error messages if an expression is out of range. Theppcasm assembler simply uses the low N bits of theexpression (where N is the field width) if the value isgreater than zero. For example the simplified mnemonic:

is equivalent to

The following code:

assembles to

with ppcasm. This generates an out-of-range error with theMac OS X assembler.

For fields less than zero, the ppcasm assembler uses thevalue of zero. For example, the simplified mnemonic:

is equivalent to

Thus the following code:

assembles to:

with ppcasm. This generates an out-of-range error with theMac OS X assembler.

All integer expressions in the Mac OS X assembler are signed32-bit values. Parameters that are 16-bit signed or unsignedimmediate values must agree in their upper 16 bits or the assemblergenerates an out-of-range error message.

For example:

generates the message 'Parameter error: expression out of range(parameter 3)'.

Grapple Man (prototype) Mac Os Catalina

The addi instruction takes a signed immediate valueso it will sign extend its parameter to 32 bits before performing theoperation. If the value 0xffffffff is intended, it would be codedas:

If this is half of a two-instruction 32-bit add it should be codedas:

Many of the simplified mnemonics are implemented as Mac OS Xassembler macros (as noted in the listing of PowerPC assemblerinstructions in the assember manual). Like all macros, the macro isexpanded and assembled. This expansion can result in errors that canseem confusing when you look at the coded macro. For example, thesimplified mnemonic:

is equivalent to

Thus the following code:

generates the error message 'Parameter error: expression out ofrange (parameter 4),' which refers to 'n-1' or '0-1', or parameter 4of the expanded macro.

The instruction tlbiex, which has been removed fromthe PowerPC architecture, is not supported by the Mac OS X assembler.This instruction is assembled by ppcasm.

Grapple Man (prototype) Mac Os X

Copyright ©2003 Apple Computer, Inc.