[Mono-bugs] [Bug 324134] Add support for Mac OS X / ppc64

[bugzilla_noreply at novell.com]

https://bugzilla.novell.com/show_bug.cgi?id=324134

User andreas.faerber at web.de added comment
https://bugzilla.novell.com/show_bug.cgi?id=324134#c25


Andreas Färber <andreas.faerber at web.de> changed:

           What    |Removed                                         |Added
----------------------------------------------------------------------------
 Attachment #214933|0                                               |1
        is obsolete|                                                |




--- Comment #25 from Andreas Färber <andreas.faerber at web.de>  2008-05-18 13:28:54 MST ---
Created an attachment (id=216246)
 --> (https://bugzilla.novell.com/attachment.cgi?id=216246)
draft ppc64 patch (3/3)

New pass, extending ppc64 support:

* mono/arch/ppc/ppc-codegen.h:
  - add cmpd mnemonic
  - fix ppc_fctidzx (...emit32)
  - fix ppc_rldiclx (Rc), add mnemonics
  - complete rldicrx mnemonics
* mono/mini/mini-ppc.c:
  - keep emit_darwing5_tls in common section, use ppc_load_reg
  - OSX sysctl changes were moved to patch 2/3 and fixed there
  - use ppc_load_func for loading void* func argument (correct?)
  - fix emit_float_to_int
  - fix integer conversions to byte, short
  - add support for integer conversion to int
  - fix shift ops
  - fix multiplication ops
  - fix localloc op
  - add support for floating point conversion to long
  - removed stray debug printf
  - commented out offsets_from_pthread_key, try_offset_access changes

Behavior is still unchanged: According to gdb, it encounters an illegal
instruction during mono_runtime_invoke in create_exception_two_strings
(mono/metadata/exception.c) while setting up the runtime. When running without
gdb, I assume Mono's attempt to handle the error appears to lead to the
perceived hang in form of an infinite loop trying to handle the error.


-- 
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.