From owner-freebsd-toolchain@freebsd.org Tue Apr 3 20:44:24 2018 Return-Path: Delivered-To: freebsd-toolchain@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 374C6F7ED91 for ; Tue, 3 Apr 2018 20:44:24 +0000 (UTC) (envelope-from shawn.webb@hardenedbsd.org) Received: from mail-wm0-x242.google.com (mail-wm0-x242.google.com [IPv6:2a00:1450:400c:c09::242]) (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 AD07472F3B for ; Tue, 3 Apr 2018 20:44:23 +0000 (UTC) (envelope-from shawn.webb@hardenedbsd.org) Received: by mail-wm0-x242.google.com with SMTP id r82so38033572wme.0 for ; Tue, 03 Apr 2018 13:44:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hardenedbsd-org.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=ygm+xUKafvyhS8kIQOYht+UqcON4i7Pxgc5sJXnQAaM=; b=T93rjxv4XY3Bq+C2iz0KrGC+PP6twHrpq9sQuXYifIEFlyM7+wdthGTIk1IIfUFS8N 8gXmi5wsbZTlBxa75ez0Eo4PVnNS5xRfXYGcxN9++ZkAz0cOY7cg3NoxGbviDtbqrI2K yCOwEYCDsiVjwLk4eUlMqqwn2cp6Iuiyl4/DYDZPNYjxtN3CJp2MBLGzXQVJD9gY03EY uqiYwvOlYtWa3T6V3rJb7X0YwIbp3lQEhme+oGrBniA1nyrpeYSVfLu56nTCaBAXk+xS 0CZMZn8EKFUL16s4/Z3UFcY/iD2SoLQEgNv/x5KYoWzGaqICQIZf3bo3WMr8qz0OmRsv g6Qw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=ygm+xUKafvyhS8kIQOYht+UqcON4i7Pxgc5sJXnQAaM=; b=YQox5F2Yda3c8YY4iQkAIBjPNAnqCj30NWWdpRVoZUlpmU1SdHVO59I+wzW6iB2rDe RBvWjIJG0VHFync5s5cqqZloPKxSrDENRCQslidztLiTuyIBN2SqYuRuuI+rJ7fEQHTT J61g6yhKlty4XNqgHwN652tA84B23W3jRz5xYRV/c1MrBd720kOldB6PJq/pNP8WjwCb WonOgU3f2wwfkw+wzdg7jEKVoDn0CSep89TtPyGpX8oWUd5k37rLFZZ+1U6HPf1dYl8x MsJkstgG6ixvV2TosSIpMBTImk2iIPo7HHQZ9m6sZIWmvI/oIU8GmIvZxZICh2hWzVoH Igvg== X-Gm-Message-State: AElRT7EdYXsod1m7CTl5Q1/N2Q2Qnc4dLM0fMYvH35pR+7UPe7d1Nz9Q FZAofZKN0o4eLUtTninE9XOG6nzMl70= X-Google-Smtp-Source: AIpwx4/EovZkqXRhCoUFiO0aZ2sckoHJoVLx2YlX/z1R2YddzEc5vLvMYn2vW1MaXseRK+uEDFDelA== X-Received: by 10.80.189.138 with SMTP id y10mr7609813edh.249.1522788262532; Tue, 03 Apr 2018 13:44:22 -0700 (PDT) Received: from mutt-hbsd ([185.104.120.60]) by smtp.gmail.com with ESMTPSA id i48sm2271940ede.39.2018.04.03.13.44.20 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Tue, 03 Apr 2018 13:44:21 -0700 (PDT) Date: Tue, 3 Apr 2018 16:44:10 -0400 From: Shawn Webb To: Brooks Davis Cc: freebsd-toolchain@freebsd.org, Ali Mashtizadeh Subject: Re: splitting libc -> libc + libsys and static linking Message-ID: <20180403204410.zfxziemnzeiejqlp@mutt-hbsd> References: <20180403203210.GA23045@spindle.one-eyed-alien.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="dbgvktdl2m5aziov" Content-Disposition: inline In-Reply-To: <20180403203210.GA23045@spindle.one-eyed-alien.net> X-Operating-System: FreeBSD mutt-hbsd 12.0-CURRENT FreeBSD 12.0-CURRENT X-PGP-Key: http://pgp.mit.edu/pks/lookup?op=vindex&search=0x6A84658F52456EEE User-Agent: NeoMutt/20171215 X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Apr 2018 20:44:24 -0000 --dbgvktdl2m5aziov Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Apr 03, 2018 at 08:32:10PM +0000, Brooks Davis wrote: > We (mostly Ali) are working on a patch to to split the actual syscalls > (__sys_) out of libc and into a libsys. For dynamic linking, > this is fairly straightforward (link libc against libsys, maybe as a > filter). For static linking, I'm looking for feedback on the right > approach. Do we link libsys.a into libc.a? Do we try to teach all the > compilers to add -lsys? I'm pretty sure we don't modify all the ports > that statically link programs. Is there some easy approach I'm missing? Hey Brooks, I'm curious about the reasoning behind this change. Could you explain in more detail why you'd like to create a libsys? Thanks, --=20 Shawn Webb Cofounder and Security Engineer HardenedBSD Tor-ified Signal: +1 443-546-8752 Tor+XMPP+OTR: lattera@is.a.hacker.sx GPG Key ID: 0x6A84658F52456EEE GPG Key Fingerprint: 2ABA B6BD EF6A F486 BE89 3D9E 6A84 658F 5245 6EEE --dbgvktdl2m5aziov Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEKrq2ve9q9Ia+iT2eaoRlj1JFbu4FAlrD55YACgkQaoRlj1JF bu6IRxAArWO8pudmzUWfvWWEYFfhWfJSc4vfrBzQ1kFFnCwQeN+iONG3F2ZTpWde bvuxtkjWX5mDPCkw/sUBDqRbgg0NPi5hl6M3GPcQuA3tkNGDqcAVD/N94P7y9cMR Cg9qCEHqT+uNccigNdeVK0FKUxG38rBq9ExwP5pWiMbsu2+7YMNDel/aTi5s8fXO p6ZKPHLBpEQ0qWXlFO0AxwjxSEAWS8tpxBoGKQwUVyRvCK+2TUgoenxzwz0CU4eI kjjtMauDe8ZOqOPICb2H9T+oDg7n6tXTZfUxLfYnfAfp+nOQGKBCSJAg9CYwus6/ qNfkDNQJ9T1Bs8vnO1Oy1tX6Uweh1S1RmQ6BlbfGHgtLUg2zab5M385vd4aFH3b9 kyrxWCLrQfTz53GDwJVxhk+tU638JMu8556bi2HmWB/L5DdjJCk/APm3l5gxp17S z+weGjW2rS47j2vfksS+VZIwJPOP9tVZZHzh8jgcGoVwjfI4oPJLjbN/pT2il900 M4bTMUBTLSriVVSdHclnQhLvfOlif8Io9FE3flrz/TZPlIVwpoINX9D1usRkyKzs 5z5IyGGFhd0R5Ynrfg0CVwzZ9gMTRxhpS8n5aTpTH4WpsUQ6OasjUoDS6Rt3eATF AbG2lWHVDpMa/KACYL9dLFbbDCAu9aoFzl3Axdp+8lzb7xp9e7U= =MzEX -----END PGP SIGNATURE----- --dbgvktdl2m5aziov--