From owner-freebsd-ppc@freebsd.org Sun Oct 29 00:04:01 2017 Return-Path: Delivered-To: freebsd-ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 47CE7E518D0; Sun, 29 Oct 2017 00:04:01 +0000 (UTC) (envelope-from chmeeedalf@gmail.com) Received: from mail-lf0-x230.google.com (mail-lf0-x230.google.com [IPv6:2a00:1450:4010:c07::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id BFC8B14B0; Sun, 29 Oct 2017 00:04:00 +0000 (UTC) (envelope-from chmeeedalf@gmail.com) Received: by mail-lf0-x230.google.com with SMTP id p184so10957947lfe.12; Sat, 28 Oct 2017 17:04:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=UFBzB5yRggvmXSDA4i1Qx52O0bkv2bZ/nYuU+euMvgk=; b=fU3+b3N/Gmo/dkK922Q1iee9G1TFAsJEKAosUB1dunBsi8tDtd1oTyNATL4GCsFdn6 P5k9dGpI2aCYUGId0nxPbGHP0N6VyXf1yPc3aJMp97eqwldhLi2y7BGSYvLjKHS5x3Kj mitcpvoAoXk6rS0OECw5oldobLe11Neq/EKJzLQ01qOmt9CGfrpQgCk2VUI/zt8cne/G sbqSU+wFWv4+07OzU3rfFHMbhzT/v3hE5PhMfVevLqL3qZqpJbeJEKtnDyEjeTVmHt3b jXFwGfy1vqTIBHXFzxJ7neO+6a07GPI4xLXoWKGa792MmmzvJ80HgfNhJbfYuH6BOb+a 9N6w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=UFBzB5yRggvmXSDA4i1Qx52O0bkv2bZ/nYuU+euMvgk=; b=FBQzTkqmwfvLrfvNotlchJdip5FsGEzQXSGpoYBzZYM9ILMBiG9YwAAXtl6mNlVOkS xqO4g82KTsm232MZ4I5i13w21DwJfWdzFJy4KQLKExJva8oybokpMDIRR4FwjX7O3W10 gqqeSLbky8FKyiVWM+p6jZ3u3/hU2+q70ihETrQ6f1QQeqj/XJUh3BtBFYLcUJuJ9tsS bl3/bsoE9OwGXiu0VH9g3koBf61iK3pzWkwT7L4aASmdXNm+97/VK/L08Q3tSD8rZNCx aCfqvdzn5uxNdnL9MoVT8AVRUQc7HeJtpMufB0DaKMV+IBFSDtNvthsQT+9KTsUZoKHl x1VA== X-Gm-Message-State: AMCzsaUzEzqIxw4C/lCb5DLEwYQ20a/CswcN/CKAs8VHp7AwZCj0ja6u 17GOeILwwqi0KEJIb17AMSdTGymIG1id53MIU7A= X-Google-Smtp-Source: ABhQp+QQv5zVIkFek73MYXAU4RowfgEYqOlg6zKRWubY+fePD+NzHFjRLlACqPp1uakSFPO/9e5b+6wWQRoH6tf/HvM= X-Received: by 10.46.93.137 with SMTP id v9mr1796791lje.39.1509235438668; Sat, 28 Oct 2017 17:03:58 -0700 (PDT) MIME-Version: 1.0 Received: by 10.46.86.7 with HTTP; Sat, 28 Oct 2017 17:03:57 -0700 (PDT) Received: by 10.46.86.7 with HTTP; Sat, 28 Oct 2017 17:03:57 -0700 (PDT) In-Reply-To: <618F5419-0BB7-496E-B1B8-DA8BE6D54A58@dsl-only.net> References: <618F5419-0BB7-496E-B1B8-DA8BE6D54A58@dsl-only.net> From: Justin Hibbits Date: Sat, 28 Oct 2017 19:03:57 -0500 Message-ID: Subject: Re: Question for powerpc64 lib32 (powerpc) support: what ABI is the powerpc code supposed to be using? To: Mark Millard Cc: FreeBSD PowerPC ML , freebsd-hackers Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Oct 2017 00:04:01 -0000 Hi Mark On Oct 28, 2017 17:08, "Mark Millard" wrote: powerpc64 and powerpc have very different stack handling rules for FreeBSD. As an example, powerpc does not require red-zones for signal handling in the kernel but powerpc64 does. For lib32 support, what ABI is the powerpc code supposed to follow in the powerpc64 environment? What style of stack handling (and related register usage) is supposed to be in use? If it is distinct from powerpc native's ABI, what documentation should be looked at for the ABI? === Mark Millard markmi at dsl-only.net PowerPC via lib32 should be using the 32-bit svr4 ABI. If you see any discrepancy in that, it's a bug that needs fixed. - Justin