From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18673 invoked by alias); 3 Oct 2011 23:48:21 -0000 Received: (qmail 18664 invoked by uid 22791); 3 Oct 2011 23:48:20 -0000 X-SWARE-Spam-Status: No, hits=-1.8 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,TW_JL X-Spam-Check-By: sourceware.org Received: from mail-ww0-f51.google.com (HELO mail-ww0-f51.google.com) (74.125.82.51) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 03 Oct 2011 23:47:59 +0000 Received: by wwf10 with SMTP id 10so5764657wwf.8 for ; Mon, 03 Oct 2011 16:47:58 -0700 (PDT) MIME-Version: 1.0 Received: by 10.216.14.2 with SMTP id c2mr4352015wec.30.1317685677929; Mon, 03 Oct 2011 16:47:57 -0700 (PDT) Received: by 10.216.168.10 with HTTP; Mon, 3 Oct 2011 16:47:57 -0700 (PDT) In-Reply-To: <201110031903.43037.vapier@gentoo.org> References: <201110031834.35051.vapier@gentoo.org> <201110031903.43037.vapier@gentoo.org> Date: Mon, 03 Oct 2011 23:48:00 -0000 Message-ID: Subject: Re: new triplet for x32 psABI? From: Michael LIAO To: Mike Frysinger Cc: autoconf@gnu.org, gcc@gcc.gnu.org, x32-abi@googlegroups.com, config-patches@gnu.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org X-SW-Source: 2011-10/txt/msg00031.txt.bz2 On Mon, Oct 3, 2011 at 4:03 PM, Mike Frysinger wrote: > On Monday, October 03, 2011 18:57:28 Michael LIAO wrote: > > please don't top post > sorry, it's my first post on mailing. >> Most examples would be related to tools generating code. >> >> Suppose you have a software package with several hard-coded fully >> optimized assembly file for different targets. Your build system need >> to know the current target as well as target ABI to select the correct >> assembly file to build it. It even desirable if it includes a simple >> script to help generate assembly code (like the one in OpenSSL), you'd >> better know the target ABI to prepare proper glue code without >> breaking ABI. > > hjlu posted examples to the x32 site as to handle this. =C2=A0the only di= fference > between x86_64 and x32 is the size of the pointers. > Besides the pointer size, there are other differences like indirect branch which need different code sequence on x32 and x64. Indirect branch would be used in assembly code (yeah, concrete example would valuable here but indirect branch should be used potentially and possibly in assembly code.) If the assembly code use indirect branch, it needs to know the target ABI and generate/use difference code path. > please explain why his example won't cover the OpenSSL's needs. =C2=A0(si= de note; > OpenSSL is a terrible example to use because (1) they don't even use auto= conf > or any autotools and (2) they don't generally use sane tuples like the co= nfig > project). > -mike > Openssl may not a good example and I just used as I remembered it uses assembly code.