News for hackers. Stuff that matters.
Re:32-bit x86 Position Independent Code – It's That Bad by bla2 on Wednesday April 15, 2015 @10:45AM (#9381287)
Is 32-bit Linux still worth worrying about? It seems that 64-bit CPUs and kernels have been around for a really long time now. (Honest question.)
Re:32-bit x86 Position Independent Code – It's That Bad by davidgerard on Wednesday April 15, 2015 @12:11PM (#9381940)
We still have embedded 8-bit. Expect embedded 32-bit approximately forever.
Re:32-bit x86 Position Independent Code – It's That Bad by ori_b on Wednesday April 15, 2015 @01:57PM (#9382795)
Embedded 32 bit x86, with the SysV ABI and support for register calling conventions, though?

This is specific to i386, as far as I'm aware. And even then, the worst parts of it are only specific to i386 using the same SysV calling conventions -- ARM has PC relative addressing, as do most other processors commonly used in embedded systems. If you have PC-relative addressing, the entire problem goes away.

Re:32-bit x86 Position Independent Code – It's That Bad by wtallis on Wednesday April 15, 2015 @02:01PM (#9382829)
Yeah, but we all know the embedded 32-bit stuff that's going to be around forever is ARM, not x86.
Re:32-bit x86 Position Independent Code – It's That Bad by creshal on Wednesday April 15, 2015 @04:28PM (#9383860)
We hope it's not going to be x86… I dunno. I still see too many embedded 486/686 clones around for my liking, and Intel is now trying to get into the whole IoT business with x86-32 Quark CPUs.
Re:32-bit x86 Position Independent Code – It's That Bad by creshal on Wednesday April 15, 2015 @11:43AM (#9381702)
Intel is still selling (well, trying to…) 32-bit only Atom/Quark CPUs for smartphones and IoT devices.

Coincidentally, Android defaults to PIC in newer SDK versions. So there is still a pressure to optimize for IA32+PIC.

Re:32-bit x86 Position Independent Code – It's That Bad by SamReidHughes on Wednesday April 15, 2015 @12:51PM (#9382293)
Say you want to build flying robots 1/64 of an inch in diameter. Do you want 64-bit CPUs?
Re:32-bit x86 Position Independent Code – It's That Bad by comex on Wednesday April 15, 2015 @03:00PM (#9383302)
No, but you don't want x86 either, at least given anything vaguely resembling today's technology. See, for example, the Michigan Micro-Mote, which is only a few times that size(!) but has ROM and RAM sizes measured in bytes:

http://www.ee.columbia.edu/~mgseok/pdfs/phoenix_isscc_dac_de...

Re:32-bit x86 Position Independent Code – It's That Bad by TheSoftwareGuy on Wednesday April 15, 2015 @01:28PM (#9382581)
If you want linux to run in places where hardware is less frequently updated, yes.