Jump to content

user_hostile

Members
  • Content count

    4
  • Joined

  • Last visited

About user_hostile

  • Rank
    InsanelyMac Protégé
  1. AMD Lion Kernel

    And you fought my ignorance. So if I understand this problem, it's matter of taking the source code of the kernal, compiling it into assembly, doing a search for the instruction, swapping it out with a macro, and living happily ever after, right? I'm only trying to understand the scale of the work involved here (the SSSE3 to SSE3 conversion is a separate issue)
  2. [AMD] 10.7.3 Guide - Experimental Only

    Only when I launch DP2, do I see the HD icon; I've tried to remove the regular Finder from the desktop and replace it with DP2, but it won't let me remove or rename it. (Now that I think about it, will that cause a problem?). I dialed it back to 2 processors, and I don't see any change in response.
  3. AMD Lion Kernel

    A high level language, (aka as an HLL, e. g., C, Java, etc.) can be thought of as the Sargent who orders a private to dig the trenches. Assembly language can be thought of as the private who actually does the digging. In other words, assembly language is closer to the actual machine language that the processor uses than the HLL. In the early days of compiler design, not much effort was put into creating the most efficient implementation of an algorithm, and higher compiled languages typically ran slower then they should. In those cases where you needed responsive code (say communications on a PC), assembly language was used instead. It's also very tedious to write and rather boring, because one HLL statement can involve from as few as one (shift) to a as many as several hundred (so I was told, other's can correct me). (I recall that OS2 v2.0 was written in assembly! Which was the only way they could ensure a GUI worked responsively on a 80286 at the time; check out MS Windows for 286 and you will understand why.) Since then, compilers have come a long way in implementing clever short-cuts in code. Nowadays, there's very little to be gained to the point that you'd be challenged to write an assembly level version. But when new instruction come out, there's a learning curve involved with implementing them in an efficient manner in a compiler. Hence, we're better off writing at the assembly language level. From what little I see on wikipedia, I note that there are 16 discrete instructions for SSSE3. Presuming the various different kinds of execution for each instruction, we're looking at a lot of assembly instructions. The other problem is that fact that the hardware that can't be use the SSSE3 instruction is now obsolete. As time goes on, more folks will upgrade to hardware and the demand incentive to emulate SSSE3 will fade away. Unless there's a concerted effort by folks on this and other boards to make the patch for a working 64-bit 10.7 and beyond using AMD's sans SSSE3 will be gone by the end of the year. At least that's my take on it, YMMV.
  4. [AMD] 10.7.3 Guide - Experimental Only

    Mobo: Dell 0GK1k2, BIOS - v1.13, mfg: MSI Proc: Phenom II X6 1090T 3.2GHz, BIOS Dell vA06 Graph: PCI ATI Radeon HD 5450, 1GB DDR3 N/W: VirtualBox Host-Only Ethernet Adapter RAM: 2GB, DDR3 HDD: Virtual Drive. It works, but not stable. Mouse is sluggish. Straight VGA; DP2 Finder can be a little cranky. Running 4 CPUs for the heck of it. A lot of times will be entering text in a box and the window freezes. If I try to open up a picture, an icon opens up at the bottom and bounces, but clicking on it does nothing to change the state. Other things include the hard drive icon not showing up until DP2 Finder is launched (unlike its presence in SL). Took me probably three days to get this working; required Googling till my fingers were numb. But now I've got a much better feel for what's going on here; blunt force iterating-it-to-death is usually the best way to know the in's and out's of the system.
×