Results 1 to 10 of 24

Thread: Google Wants LLVM To Mainline x32 ABI Support

Hybrid View

  1. #1
    Join Date
    Jan 2007
    Posts
    14,539

    Default Google Wants LLVM To Mainline x32 ABI Support

    Phoronix: Google Wants LLVM To Mainline x32 ABI Support

    The Google Native Client (NaCl) team is looking to upstream some of their LLVM changes such as support for Software Fault Isolation (SFI). As part of pushing forward the changes for Native Client in LLVM, they're also looking to see mainlined the x32 ABI support. X32 is the Application Binary Interface that looks to take advantage of common x86_64 CPU features like increased CPU registers and more instruction set extensions while using 32-bit pointers...

    http://www.phoronix.com/vr.php?view=MTI3NTk

  2. #2
    Join Date
    Nov 2007
    Posts
    1,353

    Default

    I'm sorry, but I just don't see the point in x32. It seems like a complete waste of effort.

  3. #3
    Join Date
    Mar 2008
    Posts
    206

    Default

    Quote Originally Posted by duby229 View Post
    I'm sorry, but I just don't see the point in x32. It seems like a complete waste of effort.
    totally agreed. ram is so cheap this is silly.

  4. #4
    Join Date
    Nov 2008
    Location
    Madison, WI, USA
    Posts
    862

    Default

    Quote Originally Posted by bnolsen View Post
    totally agreed. ram is so cheap this is silly.
    On newer Desktop/laptop machines, this is true. On an atom/brazos machine, there are sometimes hardware limitations to the amount of RAM the system can have... In those cases, the chip might be able to run 64-bit code (and get the new instructions and more registers), but it wouldn't hurt to have 32-bit pointers to items in RAM.

  5. #5
    Join Date
    Aug 2009
    Location
    Russe, Bulgaria
    Posts
    504

    Default

    Not to mention that weak CPUs have way less caches.

  6. #6
    Join Date
    Jul 2009
    Posts
    49

    Default

    Quote Originally Posted by bnolsen View Post
    totally agreed. ram is so cheap this is silly.
    It is not so much about reduced RAM usage. The important point is that with smaller pointers you can fit more into the CPU caches.
    The biggest slowdown is usually cache misses, and those could be reduced with smaller pointers

  7. #7
    Join Date
    Aug 2010
    Posts
    58

    Default

    Only a little off topic, but it still related to Google's Native Client.
    There are plenty of games, built with Native Client and they are of nearly quality.
    I would like to point those from CoreOnline.com (a SquareEnix website), which includes: Lara Croft and the Guardians of Light.
    Some of these games works really great on Linux if you have proper video cards with proper device drivers and the latest stable Linux version of Google Chrome.
    Phoronix usually don't like to cover these titles.
    In my opinion, Steam is the best thing ever on Linux gaming, but there are some other platforms on Linux, which are less known, but with great capabilities and are very innovative, like Native Client.

  8. #8
    Join Date
    Dec 2012
    Posts
    196

    Default

    Quote Originally Posted by fernandoc1 View Post
    Only a little off topic, but it still related to Google's Native Client.
    There are plenty of games, built with Native Client and they are of nearly quality.
    I would like to point those from CoreOnline.com (a SquareEnix website), which includes: Lara Croft and the Guardians of Light.
    Some of these games works really great on Linux if you have proper video cards with proper device drivers and the latest stable Linux version of Google Chrome.
    Phoronix usually don't like to cover these titles.
    In my opinion, Steam is the best thing ever on Linux gaming, but there are some other platforms on Linux, which are less known, but with great capabilities and are very innovative, like Native Client.
    I really thought nobody was using Native Client. It will boost very much their Chrome OS.
    Anyway, being sandboxed, despite its benefits regarding security, I find it pretty limiting for real world apps, except games. If it can't even access the filesystem it is pointless to port any non-game app to Native Client for Chrome

  9. #9
    Join Date
    Oct 2009
    Posts
    845

    Default

    Quote Originally Posted by Koorac View Post
    It is not so much about reduced RAM usage. The important point is that with smaller pointers you can fit more into the CPU caches.
    The biggest slowdown is usually cache misses, and those could be reduced with smaller pointers
    Exactly. Google's interest in this is that of the performance impact rather than ram usage impact.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •