linux-kernel - gcc "internal error" with 32-bit userspace, 64-bit kernel

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 25 May 2008 11:27:28 +0200
From:	Pierre Ossman <drzeus-list@...eus.cx>
To:	LKML <linux-kernel@...r.kernel.org>, tglx@...utronix.de,
	mingo@...hat.com, hpa@...or.com
Subject: gcc "internal error" with 32-bit userspace, 64-bit kernel

I'm having a bit of a problem with the x86 32-bit compatibility and I
don't really know how to debug it.

The problem is that gcc fails some builds with "internal error" when
I'm running a 32-bit userspace on a 64-bit kernel. The same test
scenario with a 32-bit kernel works fine.

More specifically, I'm using Red Hat's mock tool on Fedora 9 to build
packages. It sets up a chroot:ed environment where (as far as I can
tell) everything is from the target system. Building for 32-bit Fedora
8 succeeds, but not Fedora 9 or RHEL 5.

Ideas on how to proceed? From what I've read, the 32-bit compatibility
of the kernel should be 100%.

Rgds

-- 
     -- Pierre Ossman

  Linux kernel, MMC maintainer        http://www.kernel.org
  rdesktop, core developer          http://www.rdesktop.org
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/