Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp4336826imu; Fri, 30 Nov 2018 15:27:00 -0800 (PST) X-Google-Smtp-Source: AFSGD/UrwJmj9hu0URWpwFDbC4PQ/1T46FpVPAVf3ULPKij7erCqRJs59/SUXamaKG6X4+wKuX7B X-Received: by 2002:a17:902:a50a:: with SMTP id s10mr7143438plq.278.1543620420439; Fri, 30 Nov 2018 15:27:00 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1543620420; cv=none; d=google.com; s=arc-20160816; b=g7KeM7HFZZcbZH9FDw3JOowsBzUgSExhSXFe44NEuRg6vTOZ6YNhj+l+n+F1EEM4IY NIqJZj84zCj4nDc2jGqrRV6ZuQgs0JJpoP3Pipd2jghDe3xvv8m4FsZXNN2Vh/cdF3sv xUhjpf71435WCH5ZWsF4VUPXuS0Ma/1Ua4hQHHcSfFZvruTBNAiZ/kah+hHhlnwrJyzd 7J9DOmg6K8SGyPI6a/Sg/0tu+dH3bgFUZrf0vFG0fMrKhtHrqz4tpzcrG3+7qYkLvTlT GlS/ZCMs34l30LNcZRUTrJLIm4ZSLxg9h3XT+xZekVfmdYvizsxDED0ftO+nawm/n3gR 5Ktw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:user-agent:references :message-id:in-reply-to:subject:cc:to:from:date; bh=xXQ6iK3hjdQkACFgm6vSJPT6v0vVcv1G+wtemgW2RX8=; b=ng3aV0J3ppzve1GSI3CFiw5WFyNnKViaXzFOmlmaJZVrdWRRjH9SXME/NG4VRY+gKK JSQkYv7Si40C+ocHQqv+fHDNDJW0E6MgCqGsFFkLDx7zmmDokP9gJTqmiMUPki12MiTn yvgdO4umZP/B9leMgiU2t51sFLCSkcw3bYl6/XkAJkn2I7y02Btu72z1MESxNMsoa4QF yAWfbDBXw41e2/DhXVLXvHti8OqPAGfLC85FUKb1jSwTXI7YiSIVZwut6dOKGCWzIYYR Td5q+s2fD/ElMHJSHM1ZcAxY35qAF5qxMl+myRsWc6mn/lPuXfv0WmfcI4EIT665LUG2 w+WA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id y7si6003267plk.275.2018.11.30.15.26.44; Fri, 30 Nov 2018 15:27:00 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726340AbeLAKhF (ORCPT + 99 others); Sat, 1 Dec 2018 05:37:05 -0500 Received: from eddie.linux-mips.org ([148.251.95.138]:51374 "EHLO cvs.linux-mips.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725790AbeLAKhF (ORCPT ); Sat, 1 Dec 2018 05:37:05 -0500 Received: (from localhost user: 'macro', uid#1010) by eddie.linux-mips.org with ESMTP id S23992919AbeK3XZJgjDI7 (ORCPT ); Sat, 1 Dec 2018 00:25:09 +0100 Date: Fri, 30 Nov 2018 23:25:09 +0000 (GMT) From: "Maciej W. Rozycki" To: Bernd Petrovitsch cc: Ingo Molnar , Andy Lutomirski , X86 ML , LKML , Borislav Petkov , Peter Zijlstra , Tycho Andersen , Daniel Colascione , Florian Weimer , Carlos O'Donell , Rich Felker Subject: Re: Cleaning up numbering for new x86 syscalls? In-Reply-To: <87cbf7b4-9e77-adc1-8e18-14dd206f0b79@petrovitsch.priv.at> Message-ID: References: <20181120073352.GA79825@gmail.com> <87cbf7b4-9e77-adc1-8e18-14dd206f0b79@petrovitsch.priv.at> User-Agent: Alpine 2.21 (LFD 202 2017-01-01) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 21 Nov 2018, Bernd Petrovitsch wrote: > And yes, lots of stuff will not compile out of the box (especially if > one uses a somewhat sane set of gcc options - not only -Wall -Wextra > -Werror) but if one gets software to compile for i386 and x86_64, > getting it to compile for x32 is a Friday afternoon job (more or less). > And yes, there is enough hardware/systems out there that uses 64bit CPUs > (for whatever reason - if only that one can't get a 32bit CPU for that > board) but will never ever need more than 2-3 GB RAM ..... The functionally equivalent 64-bit ILP32 MIPS n32 ABI has been around supported by Linux and the GNU toolchain for some 17 years now and people have been using it, so by now any sane piece of software that does not use handcoded assembly should work out of the box for the x86-64 x32 ABI as well. NB the important advantage of an LP64 ABI over an ILP32 ABI is the ability to mmap(2) files that exceed 4GiB in size (and in reality even smaller ones, as some user VM space is surely needed for other stuff), regardless of how much physical RAM is actually supported or has been installed. And these days even a web browser can easily overrun a 4GiB VM space. :( FWIW, Maciej