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-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <mvm1t3onxru.fsf@hawking.suse.de>
Date:	Thu, 23 Jun 2016 09:56:53 +0200
From:	Andreas Schwab <schwab@...e.de>
To:	Andrew Pinski <pinskia@...il.com>
Cc:	Yury Norov <ynorov@...iumnetworks.com>,
	Szabolcs Nagy <szabolcs.nagy@....com>,
	GNU C Library <libc-alpha@...rceware.org>,
	LKML <linux-kernel@...r.kernel.org>, nd <nd@....com>,
	Arnd Bergmann <arnd@...db.de>,
	Catalin Marinas <catalin.marinas@....com>,
	Marcus Shawcroft <marcus.shawcroft@....com>, philb@....org,
	David Miller <davem@...emloft.net>,
	Maxim Kuvyrkov <maxim.kuvyrkov@...aro.org>,
	"Joseph S. Myers" <joseph@...esourcery.com>,
	Andrew Pinski <apinski@...ium.com>
Subject: Re: [PATCH 01/27] [AARCH64] Fix utmp struct for compatibility reasons.

Andrew Pinski <pinskia@...il.com> writes:

> So the question becomes do we care enough about the incompatibles
> between AARCH32 and AARCH64 to fix this and go just worry about ILP32
> and LP64?

Some armv8 chips do not implement all of armv7, so how relevant is
aarch32 on aarch64?

Andreas.

-- 
Andreas Schwab, SUSE Labs, schwab@...e.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE  1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ