On Fri, Apr 18, 2014 at 6:11 PM, Sébastien Bernard <[email protected]>wrote:
> > Doh, beat me to it by a minute. Yeah, you see what I mean. :) >> >> It would be platform suicide to drop 32-bit code generation. Like many >> RISC architectures, switching to 64-bit is only done for apps that need it, >> because it is not free and will not, in general, make apps faster. Anyone >> who has worked on PPC, MIPS, SPARC, etc will be able to confirm this in a >> heartbeat, and no doubt gcc-sparc maintainers are aware of this as well. >> >> Patrick >> >> So this does not really help to understand why the switch to gcc-4.8 > didn't happened on the sparc architecture. > Because GCC maintainers have been saying for years, that they are unwilling to support the weird use case of Debian sparc port, which has 64-bit kernel but 32-bit userspace. I can find discussions about it going back as far as 2009: https://lists.debian.org/debian-sparc/2009/08/msg00010.html Another possibly relevant bit is that Aurelien Jarno started working on an unofficial sparc64 port a while ago, but the current status of it is unknown to me. See, for example https://wiki.debian.org/Sparc64 > > Cheers. > > Sébastien > > > > -- > To UNSUBSCRIBE, email to [email protected] > with a subject of "unsubscribe". Trouble? Contact > [email protected] > Archive: https://lists.debian.org/[email protected] > > -- Jurij Smakov | [email protected] | Key ID: 43C30A7D
