From owner-freebsd-toolchain@freebsd.org Sat Jan 4 13:31:47 2020 Return-Path: Delivered-To: freebsd-toolchain@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 54C241ED254; Sat, 4 Jan 2020 13:31:47 +0000 (UTC) (envelope-from jhb@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 47qjNg1btPz4FZB; Sat, 4 Jan 2020 13:31:47 +0000 (UTC) (envelope-from jhb@FreeBSD.org) Received: from John-Baldwins-MacBook-Pro-7.local (unknown [IPv6:2601:648:8881:1e90:8d3e:cb31:1f4e:f50]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) (Authenticated sender: jhb) by smtp.freebsd.org (Postfix) with ESMTPSA id BAF2E1F047; Sat, 4 Jan 2020 13:31:46 +0000 (UTC) (envelope-from jhb@FreeBSD.org) Subject: Re: svn commit: r356289 - head To: Mark Millard , svn-src-head@freebsd.org Cc: FreeBSD Toolchain References: From: John Baldwin Openpgp: preference=signencrypt Autocrypt: addr=jhb@FreeBSD.org; keydata= mQGiBETQ+XcRBADMFybiq69u+fJRy/0wzqTNS8jFfWaBTs5/OfcV7wWezVmf9sgwn8TW0Dk0 c9MBl0pz+H01dA2ZSGZ5fXlmFIsee1WEzqeJzpiwd/pejPgSzXB9ijbLHZ2/E0jhGBcVy5Yo /Tw5+U/+laeYKu2xb0XPvM0zMNls1ah5OnP9a6Ql6wCgupaoMySb7DXm2LHD1Z9jTsHcAQMD /1jzh2BoHriy/Q2s4KzzjVp/mQO5DSm2z14BvbQRcXU48oAosHA1u3Wrov6LfPY+0U1tG47X 1BGfnQH+rNAaH0livoSBQ0IPI/8WfIW7ub4qV6HYwWKVqkDkqwcpmGNDbz3gfaDht6nsie5Z pcuCcul4M9CW7Md6zzyvktjnbz61BADGDCopfZC4of0Z3Ka0u8Wik6UJOuqShBt1WcFS8ya1 oB4rc4tXfSHyMF63aPUBMxHR5DXeH+EO2edoSwViDMqWk1jTnYza51rbGY+pebLQOVOxAY7k do5Ordl3wklBPMVEPWoZ61SdbcjhHVwaC5zfiskcxj5wwXd2E9qYlBqRg7QeSm9obiBCYWxk d2luIDxqaGJARnJlZUJTRC5vcmc+iGAEExECACAFAkTQ+awCGwMGCwkIBwMCBBUCCAMEFgID AQIeAQIXgAAKCRBy3lIGd+N/BI6RAJ9S97fvbME+3hxzE3JUyUZ6vTewDACdE1stFuSfqMvM jomvZdYxIYyTUpC5Ag0ERND5ghAIAPwsO0B7BL+bz8sLlLoQktGxXwXQfS5cInvL17Dsgnr3 1AKa94j9EnXQyPEj7u0d+LmEe6CGEGDh1OcGFTMVrof2ZzkSy4+FkZwMKJpTiqeaShMh+Goj XlwIMDxyADYvBIg3eN5YdFKaPQpfgSqhT+7El7w+wSZZD8pPQuLAnie5iz9C8iKy4/cMSOrH YUK/tO+Nhw8Jjlw94Ik0T80iEhI2t+XBVjwdfjbq3HrJ0ehqdBwukyeJRYKmbn298KOFQVHO EVbHA4rF/37jzaMadK43FgJ0SAhPPF5l4l89z5oPu0b/+5e2inA3b8J3iGZxywjM+Csq1tqz hltEc7Q+E08AAwUIAL+15XH8bPbjNJdVyg2CMl10JNW2wWg2Q6qdljeaRqeR6zFus7EZTwtX sNzs5bP8y51PSUDJbeiy2RNCNKWFMndM22TZnk3GNG45nQd4OwYK0RZVrikalmJY5Q6m7Z16 4yrZgIXFdKj2t8F+x613/SJW1lIr9/bDp4U9tw0V1g3l2dFtD3p3ZrQ3hpoDtoK70ioIAjjH aIXIAcm3FGZFXy503DOA0KaTWwvOVdYCFLm3zWuSOmrX/GsEc7ovasOWwjPn878qVjbUKWwx Q4QkF4OhUV9zPtf9tDSAZ3x7QSwoKbCoRCZ/xbyTUPyQ1VvNy/mYrBcYlzHodsaqUDjHuW+I SQQYEQIACQUCRND5ggIbDAAKCRBy3lIGd+N/BCO8AJ9j1dWVQWxw/YdTbEyrRKOY8YZNwwCf afMAg8QvmOWnHx3wl8WslCaXaE8= Message-ID: Date: Sat, 4 Jan 2020 05:31:44 -0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:60.0) Gecko/20100101 Thunderbird/60.9.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Jan 2020 13:31:47 -0000 On 1/3/20 2:34 AM, Mark Millard wrote: > John Baldwin jhb at FreeBSD.org wrote on > Thu Jan 2 21:41:07 UTC 2020 : > >> On 1/2/20 1:34 PM, John Baldwin wrote: >>> Author: jhb >>> Date: Thu Jan 2 21:34:44 2020 >>> New Revision: 356289 >>> URL: https://svnweb.freebsd.org/changeset/base/356289 >>> >>> Log: >>> Look for cross toolchain makefiles in /usr/share/toolchains. >>> >>> The freebsd-binutils and freebsd-gcc* packages install toolchain >>> makefiles to /usr/share/toolchains rather than LOCALBASE. >> >> The short version is that you can do something like this to use GCC >> as the system compiler (/usr/bin/cc): >> >> cd /usr/ports/base/binutils ; make install clean >> cd ../gcc6 ; make install clean >> >> Then 'make CROSS_TOOLCHAIN=freebsd-gcc6 buildworld', etc. If you aren't >> planning on doing cross-builds you can set CROSS_TOOLCHAIN in /etc/src.conf. >> >> As described elsewhere, the base/* packages can be cross-built (along >> with pkg), so for any architectures not yet using clang we could fairly >> easily provide a cross-built package repo (though that architecture list >> is becoming rather small). I will probably add a base/gcc9 port once we >> can build a full system with gcc9. > > Just an FYI from some experiments that I did recently: > > devel/binutils@powerpc and devel/binutils@powerpc64 and > base/binutils@powerpc and base_binutils@powerpc64 do > not put out the same content as lld or the old > toolchain's ld (still used normally for 32-bit powerpc). > buildkernel runs to completion but the result > crashes from the kernel sseflf-loading and what was > produced not matching. For example, binutils put out > very few ABS symbols compared to lld/old-ld and > classifies the kernel as ET_EXEC, not ET_DYN, because > of the non-zero VirtAddr in: > > Program Headers: > Type Offset VirtAddr PhysAddr FileSiz MemSiz Flg Align > . . . > LOAD 0x000000 0x00100000 0x00100000 0xd9786c 0x1083648 RWE 0x10000 > . . . > > (I'm not claiming that is all there is that matters.) > > > These points are true using system-clang as the > compiler. (I've only cross-built so far.) > > I do not know if other architectures have similar issues > or not. But, it appears that in some cases, there is more > work to allowing the GNU linker to be used, for at least > buildkernel . > > I do not know if there is an intent to support a (modern) > GNU binutils ld (in addition to lld) or not. So it may be > that the effort would not be put in. (I'm not claiming > which side(s) would change if the effort was put in.) I have only really tested amd64, mips, and risc-v with GCC. Other platform maintainers would have to work through any MD issues. The expectation is that GCC + ld.bfd should hopefully work as well as clang + lld. Trying to cross-thread those (GCC + lld or clang + ld.bfd) might also work in theory, but is a bit harder to guarantee, especially GCC + lld. -- John Baldwin