From owner-freebsd-arch@freebsd.org Tue Oct 1 15:15:59 2019 Return-Path: Delivered-To: freebsd-arch@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 D4B60138A09 for ; Tue, 1 Oct 2019 15:15:59 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from mailman.nyi.freebsd.org (mailman.nyi.freebsd.org [IPv6:2610:1c1:1:606c::50:13]) by mx1.freebsd.org (Postfix) with ESMTP id 46jNBl5KMsz3yhs for ; Tue, 1 Oct 2019 15:15:59 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id B4EA7138A08; Tue, 1 Oct 2019 15:15:59 +0000 (UTC) Delivered-To: arch@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 B4AE7138A07 for ; Tue, 1 Oct 2019 15:15:59 +0000 (UTC) (envelope-from kevans@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 46jNBl4MMbz3yhr for ; Tue, 1 Oct 2019 15:15:59 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from mail-qk1-f175.google.com (mail-qk1-f175.google.com [209.85.222.175]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) (Authenticated sender: kevans) by smtp.freebsd.org (Postfix) with ESMTPSA id 6C6DD17D5 for ; Tue, 1 Oct 2019 15:15:59 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: by mail-qk1-f175.google.com with SMTP id w2so11590437qkf.2 for ; Tue, 01 Oct 2019 08:15:59 -0700 (PDT) X-Gm-Message-State: APjAAAUGzwmftz0tTAcso0F0hzhv/UXKz5ZKkr1YlfH5JUDIfztvnTby rFl9LNAmR6LQgo2jKMRH0YIsSiohymPXY4/tZ4U= X-Google-Smtp-Source: APXvYqzsj8cmvrntWwLoIjht7uYf32OXSILzaq76kQSBf14Gk4DxrbRsvqCtg2WNdiWbh2dI/vmO3qXLrTZsYGdCxHY= X-Received: by 2002:a37:4f84:: with SMTP id d126mr6718499qkb.430.1569942958782; Tue, 01 Oct 2019 08:15:58 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Kyle Evans Date: Tue, 1 Oct 2019 10:15:47 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: PicoBSD Build Scripts To: "freebsd-arch@freebsd.org" Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Oct 2019 15:15:59 -0000 On Fri, Sep 13, 2019 at 2:52 PM Kyle Evans wrote: > > Hi, > > A PR[0] has recently surfaced pertaining to the PicoBSD build scripts > (see: picobsd(8), ^/release/picobsd) and how they fail to produce > usable output by default. Some further investigation revealed that the > build script is actually pretty broken, and has to have been for at > least a couple of years... see comment #2 on the referenced PR. > > Because of this and that it hasn't seen much active maintenance > (mostly drive-by mechanical changes, from what I can tell) for years, > I'd like to propose deprecation and removal of the PicoBSD build > scripts. The bits at ^/release/picobsd/tinyware can likely be moved to > the ^/tools hierarchy, as they might be independently useful. > > Specifically, I propose a soft deadline of October 31st for removal; > if someone comes forward with patches or an interest in working on it, > nothing will be removed at this time. I further propose a hard > deadline of December 31st for removal without patches posted to > address the various issue. I'll happily review any patches that come > across my virtual desk. > > Thoughts/comments/concerns? > > Thanks, > > Kyle Evans > > [0] https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240506 Resending the above as a reminder; I've received zero response, so as of now the PicoBSD build scripts will be deprecated/removed on October 31st (~30 days from now). simple_httpd has been moved out of ^/release/picobsd/tinyware as it was indicated that this is actually used, but I've heard no objections to anything else. The rest of the tinyware will leave with the build scripts unless there is interest in keeping them. Thanks, Kyle Evans From owner-freebsd-arch@freebsd.org Tue Oct 1 17:50:19 2019 Return-Path: Delivered-To: freebsd-arch@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 00BA313BDF5 for ; Tue, 1 Oct 2019 17:50:19 +0000 (UTC) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: from mailman.nyi.freebsd.org (mailman.nyi.freebsd.org [IPv6:2610:1c1:1:606c::50:13]) by mx1.freebsd.org (Postfix) with ESMTP id 46jRcp41cKz48HC for ; Tue, 1 Oct 2019 17:50:18 +0000 (UTC) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: by mailman.nyi.freebsd.org (Postfix) id 882BC13BDF4; Tue, 1 Oct 2019 17:50:18 +0000 (UTC) Delivered-To: arch@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 87EEF13BDF3 for ; Tue, 1 Oct 2019 17:50:18 +0000 (UTC) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: from gndrsh.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 46jRcp1DDPz48HB; Tue, 1 Oct 2019 17:50:17 +0000 (UTC) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: from gndrsh.dnsmgr.net (localhost [127.0.0.1]) by gndrsh.dnsmgr.net (8.13.3/8.13.3) with ESMTP id x91Ho8VP044792; Tue, 1 Oct 2019 10:50:08 -0700 (PDT) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: (from freebsd-rwg@localhost) by gndrsh.dnsmgr.net (8.13.3/8.13.3/Submit) id x91Ho8NF044791; Tue, 1 Oct 2019 10:50:08 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201910011750.x91Ho8NF044791@gndrsh.dnsmgr.net> Subject: Re: PicoBSD Build Scripts In-Reply-To: To: Kyle Evans Date: Tue, 1 Oct 2019 10:50:08 -0700 (PDT) CC: "freebsd-arch@freebsd.org" X-Mailer: ELM [version 2.4ME+ PL121h (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Rspamd-Queue-Id: 46jRcp1DDPz48HB X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-6.00 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-0.997,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; REPLY(-4.00)[] X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Oct 2019 17:50:19 -0000 > On Fri, Sep 13, 2019 at 2:52 PM Kyle Evans wrote: > > > > Hi, > > > > A PR[0] has recently surfaced pertaining to the PicoBSD build scripts > > (see: picobsd(8), ^/release/picobsd) and how they fail to produce > > usable output by default. Some further investigation revealed that the > > build script is actually pretty broken, and has to have been for at > > least a couple of years... see comment #2 on the referenced PR. > > > > Because of this and that it hasn't seen much active maintenance > > (mostly drive-by mechanical changes, from what I can tell) for years, > > I'd like to propose deprecation and removal of the PicoBSD build > > scripts. The bits at ^/release/picobsd/tinyware can likely be moved to > > the ^/tools hierarchy, as they might be independently useful. > > > > Specifically, I propose a soft deadline of October 31st for removal; > > if someone comes forward with patches or an interest in working on it, > > nothing will be removed at this time. I further propose a hard > > deadline of December 31st for removal without patches posted to > > address the various issue. I'll happily review any patches that come > > across my virtual desk. > > > > Thoughts/comments/concerns? > > > > Thanks, > > > > Kyle Evans > > > > [0] https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240506 > > Resending the above as a reminder; I've received zero response, so as > of now the PicoBSD build scripts will be deprecated/removed on October > 31st (~30 days from now). > > simple_httpd has been moved out of ^/release/picobsd/tinyware as it > was indicated that this is actually used, but I've heard no objections > to anything else. The rest of the tinyware will leave with the build > scripts unless there is interest in keeping them. > > Thanks, > Kyle Evans Please first commit a depreication notice, which you can do now, if someone invokes the PicoBSD build scripts it should emmit a warning that it is going away in 13, you can MFC that back to stable/12 and stable/11 to give folks a heads up, if you do that I have no objection for a axe cut of this code on Oct 31. Regards, -- Rod Grimes rgrimes@freebsd.org From owner-freebsd-arch@freebsd.org Tue Oct 1 18:57:33 2019 Return-Path: Delivered-To: freebsd-arch@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 319A813D50C for ; Tue, 1 Oct 2019 18:57:33 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 46jT6P0W5Rz4DTK for ; Tue, 1 Oct 2019 18:57:33 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id 0F8BE13D50B; Tue, 1 Oct 2019 18:57:33 +0000 (UTC) Delivered-To: arch@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 0F50713D50A for ; Tue, 1 Oct 2019 18:57:33 +0000 (UTC) (envelope-from kevans@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 46jT6N6gkgz4DTJ for ; Tue, 1 Oct 2019 18:57:32 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from mail-qt1-f180.google.com (mail-qt1-f180.google.com [209.85.160.180]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) (Authenticated sender: kevans) by smtp.freebsd.org (Postfix) with ESMTPSA id BBDAA30EB for ; Tue, 1 Oct 2019 18:57:32 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: by mail-qt1-f180.google.com with SMTP id r5so23045449qtd.0 for ; Tue, 01 Oct 2019 11:57:32 -0700 (PDT) X-Gm-Message-State: APjAAAU4tEzTkUlR1unkm8S6AjBTFTnst6QW3UOE4+XRfJuuSrgQq3y2 y08cv8pg9dpfe5wVv+7gqaTTXtEDxDjNbGGKdII= X-Google-Smtp-Source: APXvYqxZEZTadeLIbq2ihrM699h5VIbA2G+dpt0sDeq5AVabnl6XmiwhrfR4oPbL0RVTPl+Fa4llamHdEdmLxOCgEOw= X-Received: by 2002:ac8:33d3:: with SMTP id d19mr4037420qtb.60.1569956252110; Tue, 01 Oct 2019 11:57:32 -0700 (PDT) MIME-Version: 1.0 References: <201910011750.x91Ho8NF044791@gndrsh.dnsmgr.net> In-Reply-To: <201910011750.x91Ho8NF044791@gndrsh.dnsmgr.net> From: Kyle Evans Date: Tue, 1 Oct 2019 13:57:20 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: PicoBSD Build Scripts To: "Rodney W. Grimes" Cc: "freebsd-arch@freebsd.org" Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Oct 2019 18:57:33 -0000 On Tue, Oct 1, 2019 at 12:50 PM Rodney W. Grimes wrote: > > > On Fri, Sep 13, 2019 at 2:52 PM Kyle Evans wrote: > > > > > > Hi, > > > > > > A PR[0] has recently surfaced pertaining to the PicoBSD build scripts > > > (see: picobsd(8), ^/release/picobsd) and how they fail to produce > > > usable output by default. Some further investigation revealed that the > > > build script is actually pretty broken, and has to have been for at > > > least a couple of years... see comment #2 on the referenced PR. > > > > > > Because of this and that it hasn't seen much active maintenance > > > (mostly drive-by mechanical changes, from what I can tell) for years, > > > I'd like to propose deprecation and removal of the PicoBSD build > > > scripts. The bits at ^/release/picobsd/tinyware can likely be moved to > > > the ^/tools hierarchy, as they might be independently useful. > > > > > > Specifically, I propose a soft deadline of October 31st for removal; > > > if someone comes forward with patches or an interest in working on it, > > > nothing will be removed at this time. I further propose a hard > > > deadline of December 31st for removal without patches posted to > > > address the various issue. I'll happily review any patches that come > > > across my virtual desk. > > > > > > Thoughts/comments/concerns? > > > > > > Thanks, > > > > > > Kyle Evans > > > > > > [0] https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240506 > > > > Resending the above as a reminder; I've received zero response, so as > > of now the PicoBSD build scripts will be deprecated/removed on October > > 31st (~30 days from now). > > > > simple_httpd has been moved out of ^/release/picobsd/tinyware as it > > was indicated that this is actually used, but I've heard no objections > > to anything else. The rest of the tinyware will leave with the build > > scripts unless there is interest in keeping them. > > > > Thanks, > > Kyle Evans > > Please first commit a depreication notice, which you can do now, if > someone invokes the PicoBSD > build scripts it should emmit a warning that it is going away in 13, you > can MFC that back to stable/12 and stable/11 to give folks a heads up, > if you do that I have no objection for a axe cut of this code on Oct 31. > Indeed, I plan to do this ASAP -- I was waiting to see if anyone showed interest towards maintaining/fixing it to decide which date it'd be getting removed on/around, if either. I've also had two requests to split the tinyware/ bits out into another repo for preservation sake... I'm looking at the options here to see if it's worth it. Neither request was based on "I actively use it" (unlike with simple_httpd). Thanks, Kyle Evans From owner-freebsd-arch@freebsd.org Wed Oct 2 03:07:24 2019 Return-Path: Delivered-To: freebsd-arch@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 A6BAEFF87B for ; Wed, 2 Oct 2019 03:07:24 +0000 (UTC) (envelope-from mail_5d941457019da9.64355735@bounce.smtph7gw2.hlhk.net) Received: from smtph7gw2.hlhk.net (202181212054.hlhk.net [202.181.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 46jgzQ5ph1z3DW4 for ; Wed, 2 Oct 2019 03:07:13 +0000 (UTC) (envelope-from mail_5d941457019da9.64355735@bounce.smtph7gw2.hlhk.net) Received: from sender.e-post.com.hk (unknown [202.181.211.158]) by smtph7gw2.hlhk.net (Postfix) with ESMTPA id B2C8C3B731 for ; Wed, 2 Oct 2019 10:55:12 +0800 (HKT) Date: Wed, 2 Oct 2019 11:07:03 +0800 To: freebsd-arch From: giftcn Subject: =?UTF-8?B?5pyA5L2z57K+6YG4ICAgQmVzdCBTZWxlY3Rpb24=?= Message-ID: <69fc1f3e5344a7e758c90a4daf0ff354@sender.e-post.com.hk> X-Mailer: PHPMailer 5.2.11 (https://github.com/PHPMailer/PHPMailer/) Precedence: bulk X-SMTP: smtph7gw2.hlhk.net X-SMTPAPI: {"unique_args":{"mail_id":"mail_5d941457019da9.64355735"}} MIME-Version: 1.0 DKIM-Signature: v=1; a=rsa-sha1; q=dns/txt; l=10479; s=dkim; t=1569985623; c=relaxed/simple; h=From:To:Subject; d=postlinkhk.com; z=From:=20giftcn=20 |To:=20freebsd-arch=20 |Subject:=20=3D?UTF-8?B?5pyA5L2z57K+6YG4ICAgQmVzdCBTZWxlY3Rpb24=3D?=3D; bh=+IVIDJDNShZTmkVe7mOLW4xTkDM=; b=bDvSrKjCM7Tol3hxZvf6EGl1ozdQde04fH/WyubZJU6WN/+elHZr+Iijiu18W/HtR61viRM/J4T8pNVlkOdIUwGi2I/lvhAJ4RcCxv6DZV+VcFUOwZ1dhaXNhYYbRE/+s2qjx6MP5FDtNvCmdchHvfOzkW1Uq9ywxoy4IVQ4+jg= X-Rspamd-Queue-Id: 46jgzQ5ph1z3DW4 X-Spamd-Bar: +++++ Authentication-Results: mx1.freebsd.org; dkim=pass header.d=postlinkhk.com header.s=dkim header.b=bDvSrKjC; dmarc=fail reason="SPF not aligned (relaxed), DKIM not aligned (relaxed)" header.from=yeah.net (policy=none); spf=pass (mx1.freebsd.org: domain of mail_5d941457019da9.64355735@bounce.smtph7gw2.hlhk.net designates 202.181.212.54 as permitted sender) smtp.mailfrom=mail_5d941457019da9.64355735@bounce.smtph7gw2.hlhk.net X-Spamd-Result: default: False [5.20 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_SPF_ALLOW(-0.20)[+a:smtph7gw2.hlhk.net]; FREEMAIL_FROM(0.00)[yeah.net]; URI_COUNT_ODD(1.00)[7]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[postlinkhk.com:+]; FORGED_SENDER(0.30)[giftcn@yeah.net,mail_5d941457019da9.64355735@bounce.smtph7gw2.hlhk.net]; RCVD_NO_TLS_LAST(0.10)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; AUTOGEN_PHP_SPAMMY(1.00)[]; ASN(0.00)[asn:7540, ipnet:202.181.212.0/24, country:HK]; FROM_NEQ_ENVFROM(0.00)[giftcn@yeah.net,mail_5d941457019da9.64355735@bounce.smtph7gw2.hlhk.net]; PHISHING(1.17)[simplesite->postlinkhk]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[postlinkhk.com:s=dkim]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; PRECEDENCE_BULK(0.00)[]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; HAS_PHPMAILER_SIG(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arch@freebsd.org]; HAS_LIST_UNSUB(-0.01)[]; RCPT_COUNT_ONE(0.00)[1]; MANY_INVISIBLE_PARTS(0.05)[1]; IP_SCORE(0.00)[asn: 7540(2.80), country: HK(0.07)]; NEURAL_SPAM_MEDIUM(1.00)[0.999,0]; NEURAL_SPAM_LONG(1.00)[1.000,0]; IP_SCORE_FREEMAIL(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; DMARC_POLICY_SOFTFAIL(0.10)[yeah.net : SPF not aligned (relaxed), DKIM not aligned (relaxed), none] Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.29 List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Oct 2019 03:07:24 -0000 =E5=A6=82=E9=96=A3=E4=B8=8B=E6=9C=AA=E8=83=BD=E9=96=B1=E8=AE=80=E6=AD=A4=E9= =83=B5=E4=BB=B6=EF=BC=8C=E8=AB=8B=E6=8C=89=E6=AD=A4=E3=80=82 If you can=E2=80=99t see the image below, please click here =C2=A0=E6=9C=80=E4=BD=B3=E7=A6=AE=E5=93=81=E7=B2=BE=E9=81=B8 Best Choice fo= r your Souvenirs & Gifts =E5=B0=8A=E8=B2=B4=E5=AE=A2=E6=88=B6=C2=A0 =E6=9C= =AC=E5=85=AC=E5=8F=B8=E6=98=AF=E4=B8=80=E9=96=93=E5=B0=88=E6=A5=AD=E6=96=BC= =E7=8D=8E=E7=9B=83=E3=80=81=E6=B0=B4=E6=99=B6=E5=8F=8A=E5=8C=99=E7=89=8C=E7= =B4=80=E5=BF=B5=E7=A6=AE=E5=93=81=E6=9C=8D=E5=8B=99=E5=85=AC=E5=8F=B8,=E5= =9C=8B=E5=85=A7=E8=87=AA=E8=A8=AD=E5=BB=A0=E6=88=BF,=C2=A0=E5=85=A8=E9=83= =A8=E7=94=A2=E5=93=81=E4=BB=A5=E7=9B=B4=E9=8A=B7=E5=83=B9=E5=8F=8A=E4=B8=80= =E7=AB=99=E5=BC=8F=E6=9C=8D=E5=8B=99=E6=8F=90=E4=BE=9B=E4=BA=88=E5=90=84=E5= =AE=A2=E6=88=B6,=C2=A0=E5=A6=82=E6=82=A8=E6=9C=89=E8=A8=82=E5=88=B6=E7=8D= =8E=E7=9B=83=E3=80=81=E7=8D=8E=E7=89=8C=E6=88=96=E5=BB=A3=E5=91=8A=E5=8F=8A= =E7=B4=80=E5=BF=B5=E7=AD=89=E7=A6=AE=E5=93=81.=E8=AB=8B=E6=82=A8=E4=BF=9D= =E7=95=99=E6=AD=A4=E9=9B=BB=E9=83=B5,=C2=A0=E6=AD=A1=E8=BF=8E=E6=82=A8=E9= =9A=A8=E6=99=82=E5=88=A9=E7=94=A8=E6=AD=A4=E9=9B=BB=E9=83=B5=E6=8C=89=E4=B8= =8B=E2=80=9D=E5=9B=9E=E8=A6=86=E2=80=9D,=C2=A0=E4=B8=A6=E5=9C=A8=E5=85=A7= =E5=AE=B9=E6=89=93=E4=B8=8A=E6=82=A8=E6=AC=B2=E6=9F=A5=E8=A9=A2=E7=94=A2=E5= =93=81=E5=82=B3=E9=80=81=E8=87=B3=E6=9C=AC=E5=85=AC=E5=8F=B8,=C2=A0=E6=88= =91=E5=80=91=E6=9C=83=E6=8A=8A=E7=94=A2=E5=93=81=E8=A9=B3=E7=BB=86=E9=80=A0= =E5=83=B9=E5=A0=B1=E5=9B=9E=E7=B5=A6=E6=82=A8,=C2=A0=E6=82=A8=E5=8F=AF=E4= =BB=A5=E6=8A=8A=E9=80=99=E4=BB=BD=E9=80=A0=E5=83=B9=E4=BD=9C=E7=82=BA=E5=8F= =82=E8=80=83, =E6=88=96=E6=9C=89=E8=88=88=E8=B6=A3=E6=99=82=E5=86=8D=E9=80= =9A=E7=9F=A5=E6=88=91=E5=80=91=E7=BA=A6=E8=A6=8B. Dear Customer, Our compan= y is a professional gift service company with champion cups, medals, trophi= es, crystal prizes and key holders. With factory operated in China, all our= products are provided with the direct selling price and one-stop service t= o each customer. =C2=A0If you want to order prize products, trophies, adver= tising or gift items. Please reserve this email, mark down your product and= send a "reply" to us at any time. We will quote you as received your reply= .=C2=A0 =E8=81=AF=E7=B5=A1=E4=BA=BA/ Person=EF=BC=9AAndy Lau (=E5=8A=89=E7= =94=9F) =E9=9B=BB=E8=A9=B1/Tel :=C2=A06819 2528 / 61898347=C2=A0 =E5=82=B3= =E7=9C=9F/Fax=EF=BC=9A30076520=C2=A0 =E9=9B=BB=E9=83=B5 / Email : giftcn@ye= ah.net =E7=A7=91=E9=8A=98=E5=AF=A6=E6=A5=AD=E6=9C=89=E9=99=90=E5=85=AC=E5= =8F=B8 Coralart Industrial Company Limited =E5=9C=B0=E5=9D=80 : =E9=A6=99= =E6=B8=AF=E4=B9=9D=E9=BE=8D=E8=A7=80=E5=A1=98=E9=96=8B=E6=BA=90=E9=81=9349= =E8=99=9F=E5=89=B5=E8=B2=BF=E5=BB=A3=E5=A0=B42305=E5=AE=A4 Address : Unit 2= 305, Apec Plaza, 49 Hoi Yuen Road, Kwun Tong, Kong Kong. =E9=A6=99=E6=B8=AF= =E7=B6=B2=E7=AB=99=C2=A0/ Website :=C2=A0www.coralartcn.simplesite.com =E6= =9C=80=E6=96=B0=E7=94=A2=E5=93=81 / New Product :=C2=A0www.coralartcn.net/m= obile If unsubscribe please an email with UNSUBSCRIBE entered on the subjec= t and quote your email address. =E5=A6=82=E9=96=A3=E4=B8=8B=E4=B8=8D=E6=AC= =B2=E6=94=B6=E5=88=B0=E7=94=B1=E6=9C=AC=E5=85=AC=E5=8F=B8=E7=99=BC=E5=87=BA= =E7=9A=84=E9=9B=BB=E9=83=B5, =E8=AB=8B=E5=9B=9E=E9=83=B5=E9=80=9A=E7=9F=A5= =E9=96=A3=E4=B8=8B=E7=9A=84=E9=9B=BB=E9=83=B5=E5=9C=B0=E5=9D=80=E4=B8=A6=E6= =96=BC=E4=B8=BB=E6=97=A8=E4=B8=8A=E5=8A=A0=E5=85=A5=E3=80=8C=E6=8B=92=E6=94= =B6=E3=80=8D=20 =E5=A6=82=E8=A6=81=E5=8F=96=E6=B6=88=E8=A8=82=E9=96=B1=EF=BC=8C=E8=AB=8B=E5= =88=B0=E6=AD=A4=E8=99=95=E3=80=82 If you don=E2=80=99t wish to receive our Newsletter, please click here. From owner-freebsd-arch@freebsd.org Wed Oct 2 15:42:47 2019 Return-Path: Delivered-To: freebsd-arch@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 05EE3131FE7 for ; Wed, 2 Oct 2019 15:42:47 +0000 (UTC) (envelope-from kenneth@divingroups.com) Received: from divingroups.com (divingroups.com [46.161.39.198]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 46k0l96NVkz4Zsk for ; Wed, 2 Oct 2019 15:42:45 +0000 (UTC) (envelope-from kenneth@divingroups.com) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=divingroups.com; s=default; h=Content-Type:List-Unsubscribe:Message-ID: Sender:From:Date:MIME-Version:Subject:To:Reply-To:Cc: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To: References:List-Id:List-Help:List-Subscribe:List-Post:List-Owner:List-Archive ; bh=dLDippsF3NE3oqeDz85cGBMXMDXHQatdfHA4wWqJu/Y=; b=J8hVyynvMDAhRYzpfJrtBBsi u/of5MrD3IHq9SusEqfbfKkuFK+TcS8y0xF1/l51ae2E7Bufy3WUhO9zC6dmWxqkNezhQorTwSGXQ E3eZ2o+nlcAtVvLnmP4/GVhF2TW+94EH1Vteett7b/5BJ4bWDUGYDJ7vTSQJpjpGQUUAgk=; To: freebsd-arch@freebsd.org Subject: Your request is being processed MIME-Version: 1.0 Date: Wed, 2 Oct 2019 18:42:42 +0300 From: Long William Sender: kenneth@divingroups.com Message-ID: <19779620030.481168@divingroups.com> X-Priority: 3 X-Rspamd-Queue-Id: 46k0l96NVkz4Zsk X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=divingroups.com header.s=default header.b=J8hVyynv; dmarc=pass (policy=none) header.from=divingroups.com; spf=pass (mx1.freebsd.org: domain of kenneth@divingroups.com designates 46.161.39.198 as permitted sender) smtp.mailfrom=kenneth@divingroups.com X-Spamd-Result: default: False [-2.48 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-0.995,0]; R_DKIM_ALLOW(-0.20)[divingroups.com:s=default]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+a]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; TO_DN_NONE(0.00)[]; NEURAL_HAM_LONG(-1.00)[-0.999,0]; HAS_LIST_UNSUB(-0.01)[]; RCPT_COUNT_ONE(0.00)[1]; MANY_INVISIBLE_PARTS(0.05)[1]; DKIM_TRACE(0.00)[divingroups.com:+]; MIME_BASE64_TEXT(0.10)[]; HAS_X_PRIO_THREE(0.00)[3]; DMARC_POLICY_ALLOW(-0.50)[divingroups.com,none]; RCVD_COUNT_ZERO(0.00)[0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; IP_SCORE(0.37)[ipnet: 46.161.39.0/24(0.28), asn: 50340(1.59), country: RU(0.01)]; ASN(0.00)[asn:50340, ipnet:46.161.39.0/24, country:RU]; MID_RHS_MATCH_FROM(0.00)[]; RWL_MAILSPIKE_POSSIBLE(0.00)[198.39.161.46.rep.mailspike.net : 127.0.0.17] Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: base64 X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Oct 2019 15:42:47 -0000 RGVhciBDdXN0b21lcg0KDQpZb3UgY2FuIGdldCB0aGUgbGFzdCBwYXltZW50IGluIHlvdXIgcGVy c29uYWwgYWNjb3VudC4gWW91IG5lZWQgdG8gYWRkcmVzcyB0aGlzIHJpZ2h0IGF3YXkgb3IgaXQg d2lsbCBiZSBkZWxldGVkLg0KDQpDbGljayBIZXJlIFRvIENvbmZpcm0gWW91ciBQYXltZW50IElu Zm9ybWF0aW9uIElzIENvcnJlY3QuIA0KDQrCoA0KDQpSZWdpc3RlcmVkIGVtYWlsOiBmcmVlYnNk LWFyY2hAZnJlZWJzZC5vcmcNCg0KVXNlciBJRDogVVBDUDVQV0U2UQ0KDQoNCkVuam95ICYgcGxl YXNlIGxldCBtZSBrbm93IGhvdyB5b3UgZG8uDQoNCkhhdmUgYSBnb29kIGRheSANCg0KSm9lDQoN CsKgDQoNCkUgTWFya2V0ZXINCjIwMiBMb3dlciBIaWdoIFN0cmVldA0KV2F0Zm9yZA0KV0QxNyAy RUggVW5pdGVkIEtpbmdkb20NCg0KWW91IHJlY2VpdmVkIHRoaXMgZW1haWwgYmVjYXVzZSB5b3Ug YXJlIHJlZ2lzdGVyZWQgd2l0aCBOIE1hcmtldGVyLiBVbnN1YnNjcmliZSBoZXJlDQoNCm1lZXQg Y2FuZGxl From owner-freebsd-arch@freebsd.org Thu Oct 3 21:22:09 2019 Return-Path: Delivered-To: freebsd-arch@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 C877E141302 for ; Thu, 3 Oct 2019 21:22:09 +0000 (UTC) (envelope-from mugrel@mhcsitebuilder.org) Received: from mhcsitebuilder.org (li1980-99.members.linode.com [172.105.25.99]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 46kmDJ3FSxz4lBb for ; Thu, 3 Oct 2019 21:22:08 +0000 (UTC) (envelope-from mugrel@mhcsitebuilder.org) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=mhcsitebuilder.org; s=default; h=Content-Type:List-Unsubscribe:Message-ID: Sender:From:Date:MIME-Version:Subject:To:Reply-To:Cc: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To: References:List-Id:List-Help:List-Subscribe:List-Post:List-Owner:List-Archive ; bh=FKdCZ+h0VYUh/vVCeMWumET0qnopotb7MrE4etfP+74=; b=bzLUJAoLH8JNkywvN7KCAeXi L6TDgbfAdlWZJJXrH4IPKY8efg59KVji+PTCPpr6mCnxS6KtHMqgTF6lujBtkM5wAP/AxJjlCK9CI HWmy+gB6E7pRq8c2RcQQX5SDFn+JXvFBqmhLMemr5NdYAC1CSXde0CDrDs41MIslpBVTvU=; To: freebsd-arch@freebsd.org Subject: =?UTF-8?Q?=E2=9C=8E_Why_you_respond_so_long_my_writing=3F?= MIME-Version: 1.0 Date: Thu, 3 Oct 2019 21:22:00 +0000 From: Dominique Sender: mugrel@mhcsitebuilder.org Message-ID: <19801988117.481663@mhcsitebuilder.org> X-Priority: 3 X-Rspamd-Queue-Id: 46kmDJ3FSxz4lBb X-Spamd-Bar: ++++ Authentication-Results: mx1.freebsd.org; dkim=pass header.d=mhcsitebuilder.org header.s=default header.b=bzLUJAoL; dmarc=pass (policy=none) header.from=mhcsitebuilder.org; spf=pass (mx1.freebsd.org: domain of mugrel@mhcsitebuilder.org designates 172.105.25.99 as permitted sender) smtp.mailfrom=mugrel@mhcsitebuilder.org X-Spamd-Result: default: False [4.07 / 15.00]; ARC_NA(0.00)[]; NEURAL_SPAM_LONG(0.55)[0.550,0]; R_DKIM_ALLOW(-0.20)[mhcsitebuilder.org:s=default]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+a]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; TO_DN_NONE(0.00)[]; HAS_LIST_UNSUB(-0.01)[]; URI_COUNT_ODD(1.00)[1]; RCPT_COUNT_ONE(0.00)[1]; MANY_INVISIBLE_PARTS(0.10)[2]; R_WHITE_ON_WHITE(1.19)[span color #ffffff bgcolor #ffffff]; DKIM_TRACE(0.00)[mhcsitebuilder.org:+]; MIME_BASE64_TEXT(0.10)[]; HAS_X_PRIO_THREE(0.00)[3]; NEURAL_SPAM_MEDIUM(0.84)[0.836,0]; DMARC_POLICY_ALLOW(-0.50)[mhcsitebuilder.org,none]; IP_SCORE(0.30)[ipnet: 172.105.0.0/19(2.55), asn: 63949(-1.00), country: US(-0.05)]; RCVD_COUNT_ZERO(0.00)[0]; FROM_EQ_ENVFROM(0.00)[]; SUBJECT_ENDS_QUESTION(1.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; ASN(0.00)[asn:63949, ipnet:172.105.0.0/19, country:US]; MID_RHS_MATCH_FROM(0.00)[] Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: base64 X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Oct 2019 21:22:09 -0000 RG8geW91IHdhbnQgYSBvbmUtdGltZSBzZXggd2l0aG91dCBjb21taXRtZW50Pw0KDQpUaG91c2Fu ZHMgZ2lybHMgYW5kIGJveXMgZnJvbSB5b3VyIGFyZWHCoHdhbnQgdGhlIHNhbWUhISENCg0KTWVl dCB0aGVtIGF0IHRoaXMgc2l0ZS4uDQoNCkdvb2QgTHVjay4uLg0KDQpKWV4jcSINCg0KL0xxQWkw I0FScFEmMDVXcTdZZitUIzZ4SeKAi0NAMmRzdDIoL0BWZGQzaGlhNSxieHV4diNiaT5vNDtx From owner-freebsd-arch@freebsd.org Fri Oct 4 02:10:08 2019 Return-Path: Delivered-To: freebsd-arch@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 AC1BC146CB3 for ; Fri, 4 Oct 2019 02:10:08 +0000 (UTC) (envelope-from mike@karels.net) Received: from mail.karels.net (mail.karels.net [216.160.39.52]) by mx1.freebsd.org (Postfix) with ESMTP id 46ktcb5k6Cz3JSD; Fri, 4 Oct 2019 02:10:07 +0000 (UTC) (envelope-from mike@karels.net) Received: from mail.karels.net (localhost [127.0.0.1]) by mail.karels.net (8.15.2/8.15.2) with ESMTP id x942A1pu029152; Thu, 3 Oct 2019 21:10:01 -0500 (CDT) (envelope-from mike@karels.net) Message-Id: <201910040210.x942A1pu029152@mail.karels.net> To: cem@freebsd.org cc: "freebsd-arch@freebsd.org" From: Mike Karels Reply-to: mike@karels.net Subject: Re: Dropping the type argument from the mtod macro In-reply-to: Your message of Sat, 28 Sep 2019 08:11:24 -0700. MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <29150.1570155001.1@mail.karels.net> Date: Thu, 03 Oct 2019 21:10:01 -0500 X-Rspamd-Queue-Id: 46ktcb5k6Cz3JSD X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of mike@karels.net designates 216.160.39.52 as permitted sender) smtp.mailfrom=mike@karels.net X-Spamd-Result: default: False [-3.51 / 15.00]; ARC_NA(0.00)[]; TO_DN_EQ_ADDR_SOME(0.00)[]; HAS_REPLYTO(0.00)[mike@karels.net]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:216.160.39.52]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[karels.net]; REPLYTO_ADDR_EQ_FROM(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; IP_SCORE(-1.31)[ip: (-4.74), ipnet: 216.160.0.0/15(-1.69), asn: 209(-0.08), country: US(-0.05)]; RCPT_COUNT_TWO(0.00)[2]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; RCVD_NO_TLS_LAST(0.10)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:209, ipnet:216.160.0.0/15, country:US]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Oct 2019 02:10:08 -0000 > Hi all, > (net@ is BCC'd to keep discussion on arch@.) > In the past we've moved away from macros with explicit types as > parameters, in favor of casting void* results as needed (e.g., > MALLOC()). > I'd like to do the same with mtod. The refactoring is easy enough to > do safely with a Coccinelle semantic patch. The semantic patch > converts instances of "mtod(m, t)" to "(t)mtod(m)". > markj@ and rrs@ both point out that the network stack uses the type > argument as a visual tool in large functions where the declaration of > the lvariable isn't necessarily nearby its use. I think the > "(t)mtod(m)" preserves that utility as a visual tool; I may be > mistaken. > Currently, the semantic patch drops the explicit "(t)" in two limited > cases: "t" is "void *", or the "mtod()" invocation is used during > initial variable declaration and assignment. The reasoning is that in > both cases, the "t" isn't giving you any additional information. > Neither of these exceptions is core to the idea, and either could be > removed. > What do you think? A rough draft of the proposal is sketched out > here: https://reviews.freebsd.org/D21669 > Best, > Conrad > P.S., On an earlier version of this revision, markj@ and emaste@ both > expressed concern for downstream consumers. There are two aspects of > the current differential that should smooth that experience. First, a > backwards-compatible two-argument mtod(m, t) is retained using an ugly > macro hack. (Existing code compiles without modification.) Second, > the coccinelle semantic patch will be checked in to the tree somewhere > for use by downstream consumers that want to convert their code. I was surprised not to see responses on the list, but I see that there was already a fair amount of discussion on the phabricator review up to the time of this message. I'll reply on the list in hopes of getting more feedback. I like the proposed usage better than the original mtod(); I never liked the use of a type as a parameter. However, I think it is questionable whether the cleanup is worth the cost, both for upstream and downstream. I think the biggest issue is that it makes FreeBSD code harder to use in other contexts; for example, Michael Tuexen pointed out the issue of sharing SCTP sources with other BSD-like platforms. We'll end up with two or more different styles. He asks, given the price to be paid, what do we gain? On the other hand, mtod() in its old form is ubiquitous and easy to understand. Mike From owner-freebsd-arch@freebsd.org Fri Oct 4 02:44:07 2019 Return-Path: Delivered-To: freebsd-arch@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 EE402F84F9 for ; Fri, 4 Oct 2019 02:44:07 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-qk1-x72f.google.com (mail-qk1-x72f.google.com [IPv6:2607:f8b0:4864:20::72f]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46kvMq048Tz3MRc for ; Fri, 4 Oct 2019 02:44:06 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-qk1-x72f.google.com with SMTP id f16so4459257qkl.9 for ; Thu, 03 Oct 2019 19:44:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=MGgQlz0zUoHXFrrA4Mg+GSC256tg3x23Zz0W6bb/Rps=; b=ISYGWEqAmCVJhU+0ohBIseuoH/N3Z2m2G9V3AwmBApXIZ8Ir1n5gsMk7WZTXytmzuM 89XkyE9oh1tHJWfBoLT84i9ifvd+xUQlOqtxM1ZvdjTyIb9ZxGUnA9PC5r+i6TctWtBZ Z6pnDQWtVMvaEYG3oRPxcV8EnrBzo1Rr42KsC8o0778XDA0IlZw4uQkUuKtPB7Vx3Uve ceOkbGf88vY468VPEhECP9yluls42WAO4bh6IsTDl5+2sHZxS1GpQ15aKzAo7ERly7T2 NxxGGXQ164BNK8H+T2bQ18+sMMtmMrx254eaAnrjrDC+dfQGqVJwkdnvYAk4rWV/YHrQ PlCw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=MGgQlz0zUoHXFrrA4Mg+GSC256tg3x23Zz0W6bb/Rps=; b=GbyhICyunirPj3wkkCbWbnztR/KIuwukJ3XBEnln9nWIouoLKP9WuBC4KZWoRvZvAA mtQEZf4Ouzg82vqWBuTqrlBCqqq4JfPwTXl1s2p9xDv9uA4G+b/xzWN5n+s5JBTdm4Ot bz+Y/C1JgzUUEztps25Z8gvHAG45ZSiJQOjYu8mq07hx7xoOtW5gHRuet/pFgWNGtCaB 7WrDZnNRUi6daDRXRNz9qYAiG9TLJOLSmKPSoPZVkAXt7OJ/6fffdIXCMZT1fR2gRsan 2Nysoqtk+YV7MQg4AjQU9xbViUZpijwsJyl5qs/aXZXGyfR76Z1NUUc0O93M/IADjgKD yl3w== X-Gm-Message-State: APjAAAU+QLgBpx5nVfSMM4Hi3hEhhzRAHddVoCjK8GB/ehImXKWAh0QT MoajB2uBaz6ZL0K7BUn5I5tUWLvj1of3/+w5aR4SrZ6r X-Google-Smtp-Source: APXvYqz4GtzPyaHpdrHCjvN9WgJ+fBszVYGkGlwqf7dvsUMVz4XtERK2h7HfuWEXuVcgCqe0THeY8z/eESHxozmrRsU= X-Received: by 2002:a05:620a:6af:: with SMTP id i15mr7795239qkh.380.1570157045443; Thu, 03 Oct 2019 19:44:05 -0700 (PDT) MIME-Version: 1.0 References: <201910040210.x942A1pu029152@mail.karels.net> In-Reply-To: <201910040210.x942A1pu029152@mail.karels.net> From: Warner Losh Date: Thu, 3 Oct 2019 20:43:53 -0600 Message-ID: Subject: Re: Dropping the type argument from the mtod macro To: Mike Karels Cc: "Conrad E. Meyer" , freebsd-arch@freebsd.org X-Rspamd-Queue-Id: 46kvMq048Tz3MRc X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=bsdimp-com.20150623.gappssmtp.com header.s=20150623 header.b=ISYGWEqA; dmarc=none; spf=none (mx1.freebsd.org: domain of wlosh@bsdimp.com has no SPF policy when checking 2607:f8b0:4864:20::72f) smtp.mailfrom=wlosh@bsdimp.com X-Spamd-Result: default: False [-4.84 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[bsdimp-com.20150623.gappssmtp.com:s=20150623]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; TO_DN_SOME(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arch@freebsd.org]; DMARC_NA(0.00)[bsdimp.com]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[bsdimp-com.20150623.gappssmtp.com:+]; RCVD_IN_DNSWL_NONE(0.00)[f.2.7.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org : 127.0.5.0]; R_SPF_NA(0.00)[]; FORGED_SENDER(0.30)[imp@bsdimp.com,wlosh@bsdimp.com]; MIME_TRACE(0.00)[0:+,1:+,2:~]; IP_SCORE(-2.84)[ip: (-9.44), ipnet: 2607:f8b0::/32(-2.57), asn: 15169(-2.16), country: US(-0.05)]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; FROM_NEQ_ENVFROM(0.00)[imp@bsdimp.com,wlosh@bsdimp.com]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Oct 2019 02:44:08 -0000 On Thu, Oct 3, 2019, 8:10 PM Mike Karels wrote: > > Hi all, > > > (net@ is BCC'd to keep discussion on arch@.) > > > In the past we've moved away from macros with explicit types as > > parameters, in favor of casting void* results as needed (e.g., > > MALLOC()). > > > I'd like to do the same with mtod. The refactoring is easy enough to > > do safely with a Coccinelle semantic patch. The semantic patch > > converts instances of "mtod(m, t)" to "(t)mtod(m)". > > > markj@ and rrs@ both point out that the network stack uses the type > > argument as a visual tool in large functions where the declaration of > > the lvariable isn't necessarily nearby its use. I think the > > "(t)mtod(m)" preserves that utility as a visual tool; I may be > > mistaken. > > > Currently, the semantic patch drops the explicit "(t)" in two limited > > cases: "t" is "void *", or the "mtod()" invocation is used during > > initial variable declaration and assignment. The reasoning is that in > > both cases, the "t" isn't giving you any additional information. > > Neither of these exceptions is core to the idea, and either could be > > removed. > > > What do you think? A rough draft of the proposal is sketched out > > here: https://reviews.freebsd.org/D21669 > > > Best, > > Conrad > > > P.S., On an earlier version of this revision, markj@ and emaste@ both > > expressed concern for downstream consumers. There are two aspects of > > the current differential that should smooth that experience. First, a > > backwards-compatible two-argument mtod(m, t) is retained using an ugly > > macro hack. (Existing code compiles without modification.) Second, > > the coccinelle semantic patch will be checked in to the tree somewhere > > for use by downstream consumers that want to convert their code. > > I was surprised not to see responses on the list, but I see that there > was already a fair amount of discussion on the phabricator review up > to the time of this message. I'll reply on the list in hopes of getting > more feedback. > > I like the proposed usage better than the original mtod(); I never liked > the use of a type as a parameter. However, I think it is questionable > whether the cleanup is worth the cost, both for upstream and downstream. > I think the biggest issue is that it makes FreeBSD code harder to use > in other contexts; for example, Michael Tuexen pointed out the issue > of sharing SCTP sources with other BSD-like platforms. We'll end up > with two or more different styles. He asks, given the price to be paid, > what do we gain? On the other hand, mtod() in its old form is ubiquitous > and easy to understand. > Clearly we need m2d() instead. A more modern name for a more modern API. In all seriousness, though, I'm more drawn to the too little gain, too much pain arguments more than the purity arguments. Warner Mike > _______________________________________________ > freebsd-arch@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arch > To unsubscribe, send any mail to "freebsd-arch-unsubscribe@freebsd.org" > From owner-freebsd-arch@freebsd.org Fri Oct 4 11:46:15 2019 Return-Path: Delivered-To: freebsd-arch@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 A430F12C0DF for ; Fri, 4 Oct 2019 11:46:15 +0000 (UTC) (envelope-from sathis@prettybypost.org) Received: from prettybypost.org (li1158-175.members.linode.com [45.79.59.175]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 46l7PM0jTkz4HWt for ; Fri, 4 Oct 2019 11:46:14 +0000 (UTC) (envelope-from sathis@prettybypost.org) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=prettybypost.org; s=default; h=Content-Type:List-Unsubscribe:Message-ID: Sender:From:Date:MIME-Version:Subject:To:Reply-To:Cc: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To: References:List-Id:List-Help:List-Subscribe:List-Post:List-Owner:List-Archive ; bh=lMi1YOdRIQCs59SFq5DI5g1ADy3yKvBnf/4zxfhtzGc=; b=Ifslp4RsmUnyeWkLRPcYsDLr XadR8CL4FhUCWSCYW2Km2e3tChenvu3KpTbeturqM5KwMRuHaEipEJ2r6p6ADh6CSmjXdDjK+NCHp aCRhtidcj5/l8fYvXWVbr6lYv83ji+/+AkLqbSkC2m5ogt5F6ts+OMI40zutiSHTB4oQ54=; To: freebsd-arch@freebsd.org Subject: =?UTF-8?Q?Get_started_and_discover_how_to_isolate_=E2=80=9Cresting_trends?= =?UTF-8?Q?=E2=80=9D, _buy_them, _and_watch_them_snap_back_to_life.?= MIME-Version: 1.0 Date: Fri, 4 Oct 2019 11:36:31 +0000 From: Josephine Sender: sathis@prettybypost.org Message-ID: <19813051969.481939@prettybypost.org> X-Priority: 3 X-Rspamd-Queue-Id: 46l7PM0jTkz4HWt X-Spamd-Bar: +++++++ Authentication-Results: mx1.freebsd.org; dkim=pass header.d=prettybypost.org header.s=default header.b=Ifslp4Rs; dmarc=pass (policy=none) header.from=prettybypost.org; spf=pass (mx1.freebsd.org: domain of sathis@prettybypost.org designates 45.79.59.175 as permitted sender) smtp.mailfrom=sathis@prettybypost.org X-Spamd-Result: default: False [7.27 / 15.00]; ARC_NA(0.00)[]; RSPAMD_URIBL(4.50)[prettybypost.org]; R_DKIM_ALLOW(0.00)[prettybypost.org:s=default]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(0.00)[+a:c]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; TO_DN_NONE(0.00)[]; HAS_LIST_UNSUB(-0.01)[]; RCPT_COUNT_ONE(0.00)[1]; BAD_REP_POLICIES(0.10)[]; NEURAL_SPAM_LONG(1.00)[1.000,0]; NEURAL_SPAM_MEDIUM(1.00)[1.000,0]; DKIM_TRACE(0.00)[prettybypost.org:+]; MIME_BASE64_TEXT(0.10)[]; HAS_X_PRIO_THREE(0.00)[3]; DMARC_POLICY_ALLOW(0.00)[prettybypost.org,none]; RCVD_COUNT_ZERO(0.00)[0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; IP_SCORE(0.68)[ipnet: 45.79.32.0/19(4.46), asn: 63949(-1.00), country: US(-0.05)]; ASN(0.00)[asn:63949, ipnet:45.79.32.0/19, country:US]; MID_RHS_MATCH_FROM(0.00)[]; GREYLIST(0.00)[pass,body] X-Spam: Yes Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: base64 X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Oct 2019 11:46:15 -0000 RGVhciBTaXIvTWFkYW0hDQoNCk91ciBpbnRlcm5hdGlvbmFsIGNvbXBhbnkgY29uc2lzdHMgb2Yg YWJvdXQgNjAgSW50ZXJuZXQgcHJvamVjdHMgcmVsYXRlZA0KdG8gY3J5cHRvIGN1cnJlbmNpZXMg YW5kIElDTy4gTm93IHdlIHJlY3J1aXQgdGVhbSBmcm9tIGFsbCBvdmVyIHRoZSB3b3JsZC4NCg0K Q0xJQ0sgSEVSRSBUTyBTVEFSVCANCg0KUHJpbWFyeSBzYWxhcnkgJDc5OGsgeWVhcmx5IEUtd29y a2VycyBXQU5URUQuDQoNCi0gTm8gU2tpbGxzIE5lZWRlZA0KDQotIE5vIFByZXZpb3VzIEpvYiBF eHBlcmllbmNlIE5lZWRlZA0KDQotIE5vIENyeXB0byBUcmFkaW5nIEV4cGVyaWVuY2UgUmVxdWly ZWQNCg0KT3VyIFJlcXVpcmVtZW50czoNCg0KPj4gSW50ZXJuZXQgYWNjZXNzDQoNCj4+IENvbXB1 dGVyIGtub3dsZWRnZQ0KDQo+PiBBIDItNSBob3VycyBvZiBmcmVlIHRpbWUgZGFpbHkNCg0KPj4g U2hhcnAgTWluZA0KDQpBdmVyYWdlIGVhcm5pbmdzIGlzICQ5MjQgcGVyIGRheSwgcGFydC10aW1l LCBubyBzZXQgaG91cnMuDQoNCkF0IHRoaXMgbW9tZW50IHRoZXJlIGFyZSAyNyB2YWNhbmN5IGxl ZnQuDQoNCkNIRUNLIElUIE9VVCBIRVJFDQoNCiBBbGwgdGhlIEJlc3QsDQoNCkF1Z3VzdCBHb21l eg0KDQpIUiBEZXB0Lg0KDQpBcmNhTWF4IFB1Ymxpc2hpbmcsIEluYy4sIDcyOSBUaGltYmxlIFNo b2FscyBCbHZkLiwgU3VpdGUgMS1CLCBOZXdwb3J0IE5ld3MsIFZBIDIzNjA2 From owner-freebsd-arch@freebsd.org Fri Oct 4 14:31:13 2019 Return-Path: Delivered-To: freebsd-arch@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 D157213023A for ; Fri, 4 Oct 2019 14:31:13 +0000 (UTC) (envelope-from agapon@gmail.com) Received: from mail-lj1-f179.google.com (mail-lj1-f179.google.com [209.85.208.179]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46lC3h66wXz4R7v for ; Fri, 4 Oct 2019 14:31:12 +0000 (UTC) (envelope-from agapon@gmail.com) Received: by mail-lj1-f179.google.com with SMTP id y3so6743144ljj.6 for ; Fri, 04 Oct 2019 07:31:12 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:to:from:subject:openpgp:autocrypt:message-id :date:user-agent:mime-version:content-language :content-transfer-encoding; bh=EDNyQs6psxn2QVIfTxs6YMs0OekhLkO19LODwa9UF9o=; b=j74y0duPdwcIgeTLgiLr3UMmRg6TmuLOp5mHzmC/Gj5Ya1HCwGecRJZ5U80tCxua8q W+1erPYijRlUQgYxiHCfhFPCZIBMlVvXgjo6CNQa2DH9bZCLLmm3SI4yxKxIRKhDb5Ju 5HVC1MfSbv075qT1vsPx3DjP+eNkqrbb2/vZDYPiQkiOPUure+ubs47u4Wdc+z+NWO1Y 5ofO7evSs3fqFBRin/ItzQj8u5cQFMYuWxWBBmDLPLLwEhNUMV7DPhcEA9MCgdRNtf+y e+Af8oDNyBSSwTs6t+0xQ6VFfSzQpIKZlsMXwGh+jS+opEldGvaY4cpHWXnI1h5Pca9A RfdA== X-Gm-Message-State: APjAAAXvh5IcIkGStJguuOmXh4HqMdtnI1bvaSz86L6UWg5s6j0VGs6h mUAufndKgt8c15v+owDzU59jkaT3GBQ= X-Google-Smtp-Source: APXvYqyk5Ke0H2yN5jDsRZtB6ZinGg99VZeFbBN9zY69DRroCTQlbQC4l34L4lQhdTdmpKOksN4A4w== X-Received: by 2002:a2e:744:: with SMTP id i4mr9838627ljd.64.1570199470622; Fri, 04 Oct 2019 07:31:10 -0700 (PDT) Received: from [192.168.0.88] (east.meadow.volia.net. [93.72.151.96]) by smtp.googlemail.com with ESMTPSA id j7sm1178897lfc.16.2019.10.04.07.31.09 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 04 Oct 2019 07:31:09 -0700 (PDT) To: freebsd-arch@FreeBSD.ORG From: Andriy Gapon Subject: atomic_cmpset_64 vs atomic_cas_64 Openpgp: preference=signencrypt Autocrypt: addr=avg@FreeBSD.org; prefer-encrypt=mutual; keydata= mQINBFm4LIgBEADNB/3lT7f15UKeQ52xCFQx/GqHkSxEdVyLFZTmY3KyNPQGBtyvVyBfprJ7 mAeXZWfhat6cKNRAGZcL5EmewdQuUfQfBdYmKjbw3a9GFDsDNuhDA2QwFt8BmkiVMRYyvI7l N0eVzszWCUgdc3qqM6qqcgBaqsVmJluwpvwp4ZBXmch5BgDDDb1MPO8AZ2QZfIQmplkj8Y6Z AiNMknkmgaekIINSJX8IzRzKD5WwMsin70psE8dpL/iBsA2cpJGzWMObVTtCxeDKlBCNqM1i gTXta1ukdUT7JgLEFZk9ceYQQMJJtUwzWu1UHfZn0Fs29HTqawfWPSZVbulbrnu5q55R4PlQ /xURkWQUTyDpqUvb4JK371zhepXiXDwrrpnyyZABm3SFLkk2bHlheeKU6Yql4pcmSVym1AS4 dV8y0oHAfdlSCF6tpOPf2+K9nW1CFA8b/tw4oJBTtfZ1kxXOMdyZU5fiG7xb1qDgpQKgHUX8 7Rd2T1UVLVeuhYlXNw2F+a2ucY+cMoqz3LtpksUiBppJhw099gEXehcN2JbUZ2TueJdt1FdS ztnZmsHUXLxrRBtGwqnFL7GSd6snpGIKuuL305iaOGODbb9c7ne1JqBbkw1wh8ci6vvwGlzx rexzimRaBzJxlkjNfMx8WpCvYebGMydNoeEtkWldtjTNVsUAtQARAQABtB5BbmRyaXkgR2Fw b24gPGF2Z0BGcmVlQlNELm9yZz6JAlQEEwEIAD4WIQS+LEO7ngQnXA4Bjr538m7TUc1yjwUC WbgsiAIbIwUJBaOagAULCQgHAgYVCAkKCwIEFgIDAQIeAQIXgAAKCRB38m7TUc1yj+JAEACV l9AK/nOWAt/9cufV2fRj0hdOqB1aCshtSrwHk/exXsDa4/FkmegxXQGY+3GWX3deIyesbVRL rYdtdK0dqJyT1SBqXK1h3/at9rxr9GQA6KWOxTjUFURsU7ok/6SIlm8uLRPNKO+yq0GDjgaO LzN+xykuBA0FlhQAXJnpZLcVfPJdWv7sSHGedL5ln8P8rxR+XnmsA5TUaaPcbhTB+mG+iKFj GghASDSfGqLWFPBlX/fpXikBDZ1gvOr8nyMY9nXhgfXpq3B6QCRYKPy58ChrZ5weeJZ29b7/ QdEO8NFNWHjSD9meiLdWQaqo9Y7uUxN3wySc/YUZxtS0bhAd8zJdNPsJYG8sXgKjeBQMVGuT eCAJFEYJqbwWvIXMfVWop4+O4xB+z2YE3jAbG/9tB/GSnQdVSj3G8MS80iLS58frnt+RSEw/ psahrfh0dh6SFHttE049xYiC+cM8J27Aaf0i9RflyITq57NuJm+AHJoU9SQUkIF0nc6lfA+o JRiyRlHZHKoRQkIg4aiKaZSWjQYRl5Txl0IZUP1dSWMX4s3XTMurC/pnja45dge/4ESOtJ9R 8XuIWg45Oq6MeIWdjKddGhRj3OohsltKgkEU3eLKYtB6qRTQypHHUawCXz88uYt5e3w4V16H lCpSTZV/EVHnNe45FVBlvK7k7HFfDDkryLkCDQRZuCyIARAAlq0slcsVboY/+IUJdcbEiJRW be9HKVz4SUchq0z9MZPX/0dcnvz/gkyYA+OuM78dNS7Mbby5dTvOqfpLJfCuhaNYOhlE0wY+ 1T6Tf1f4c/uA3U/YiadukQ3+6TJuYGAdRZD5EqYFIkreARTVWg87N9g0fT9BEqLw9lJtEGDY EWUE7L++B8o4uu3LQFEYxcrb4K/WKmgtmFcm77s0IKDrfcX4doV92QTIpLiRxcOmCC/OCYuO jB1oaaqXQzZrCutXRK0L5XN1Y1PYjIrEzHMIXmCDlLYnpFkK+itlXwlE2ZQxkfMruCWdQXye syl2fynAe8hvp7Mms9qU2r2K9EcJiR5N1t1C2/kTKNUhcRv7Yd/vwusK7BqJbhlng5ZgRx0m WxdntU/JLEntz3QBsBsWM9Y9wf2V4tLv6/DuDBta781RsCB/UrU2zNuOEkSixlUiHxw1dccI 6CVlaWkkJBxmHX22GdDFrcjvwMNIbbyfQLuBq6IOh8nvu9vuItup7qemDG3Ms6TVwA7BD3j+ 3fGprtyW8Fd/RR2bW2+LWkMrqHffAr6Y6V3h5kd2G9Q8ZWpEJk+LG6Mk3fhZhmCnHhDu6CwN MeUvxXDVO+fqc3JjFm5OxhmfVeJKrbCEUJyM8ESWLoNHLqjywdZga4Q7P12g8DUQ1mRxYg/L HgZY3zfKOqcAEQEAAYkCPAQYAQgAJhYhBL4sQ7ueBCdcDgGOvnfybtNRzXKPBQJZuCyIAhsM BQkFo5qAAAoJEHfybtNRzXKPBVwQAKfFy9P7N3OsLDMB56A4Kf+ZT+d5cIx0Yiaf4n6w7m3i ImHHHk9FIetI4Xe54a2IXh4Bq5UkAGY0667eIs+Z1Ea6I2i27Sdo7DxGwq09Qnm/Y65ADvXs 3aBvokCcm7FsM1wky395m8xUos1681oV5oxgqeRI8/76qy0hD9WR65UW+HQgZRIcIjSel9vR XDaD2HLGPTTGr7u4v00UeTMs6qvPsa2PJagogrKY8RXdFtXvweQFz78NbXhluwix2Tb9ETPk LIpDrtzV73CaE2aqBG/KrboXT2C67BgFtnk7T7Y7iKq4/XvEdDWscz2wws91BOXuMMd4c/c4 OmGW9m3RBLufFrOag1q5yUS9QbFfyqL6dftJP3Zq/xe+mr7sbWbhPVCQFrH3r26mpmy841ym dwQnNcsbIGiBASBSKksOvIDYKa2Wy8htPmWFTEOPRpFXdGQ27awcjjnB42nngyCK5ukZDHi6 w0qK5DNQQCkiweevCIC6wc3p67jl1EMFY5+z+zdTPb3h7LeVnGqW0qBQl99vVFgzLxchKcl0 R/paSFgwqXCZhAKMuUHncJuynDOP7z5LirUeFI8qsBAJi1rXpQoLJTVcW72swZ42IdPiboqx NbTMiNOiE36GqMcTPfKylCbF45JNX4nF9ElM0E+Y8gi4cizJYBRr2FBJgay0b9Cp Message-ID: <0a330e4a-9b8b-7678-cb54-a379f1e4b0bc@FreeBSD.org> Date: Fri, 4 Oct 2019 17:31:08 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 46lC3h66wXz4R7v X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of agapon@gmail.com designates 209.85.208.179 as permitted sender) smtp.mailfrom=agapon@gmail.com X-Spamd-Result: default: False [-3.20 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17:c]; TO_DN_NONE(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; FORGED_SENDER(0.30)[avg@FreeBSD.org,agapon@gmail.com]; RECEIVED_SPAMHAUS_PBL(0.00)[96.151.72.93.khpj7ygk5idzvmvt5x4ziurxhy.zen.dq.spamhaus.net : 127.0.0.10]; MIME_TRACE(0.00)[0:+]; R_DKIM_NA(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; FROM_NEQ_ENVFROM(0.00)[avg@FreeBSD.org,agapon@gmail.com]; TO_DOM_EQ_FROM_DOM(0.00)[]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arch@freebsd.org]; DMARC_NA(0.00)[FreeBSD.org]; RCPT_COUNT_ONE(0.00)[1]; IP_SCORE(-1.20)[ip: (-0.52), ipnet: 209.85.128.0/17(-3.27), asn: 15169(-2.16), country: US(-0.05)]; RCVD_IN_DNSWL_NONE(0.00)[179.208.85.209.list.dnswl.org : 127.0.5.0]; RWL_MAILSPIKE_POSSIBLE(0.00)[179.208.85.209.rep.mailspike.net : 127.0.0.17]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Oct 2019 14:31:13 -0000 I see that almost all 64-bit platforms provide atomic_cmpset_64, but sparc64 provides atomic_cas_64 (instead?). I think that the meanings of "cas" and "cmpset" are really the same, but I am not sure if there are any differences in that the functions do. Could anyone who knows that stuff (sparc64 assembly) please shed some light? Thanks! #define atomic_cas_64(p, e, s) casxa((p), (e), (s), __ASI_ATOMIC) -- Andriy Gapon From owner-freebsd-arch@freebsd.org Fri Oct 4 14:35:48 2019 Return-Path: Delivered-To: freebsd-arch@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 0AEDD130474 for ; Fri, 4 Oct 2019 14:35:48 +0000 (UTC) (envelope-from mjguzik@gmail.com) Received: from mail-ot1-x332.google.com (mail-ot1-x332.google.com [IPv6:2607:f8b0:4864:20::332]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46lC8z6RrVz4RQl; Fri, 4 Oct 2019 14:35:47 +0000 (UTC) (envelope-from mjguzik@gmail.com) Received: by mail-ot1-x332.google.com with SMTP id 21so5431361otj.11; Fri, 04 Oct 2019 07:35:47 -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=s0PZXeeRQYmC65cZZEwBi/cIKv1rcJ/mgpXasGajJIc=; b=XX/0EMnm5etkBztGhC80Iy2uH50u1ADd/NT/sqQ/L61NgOYNls/H5a2sL4HOiuSIbb FwNTvaG2Qrvo7DxDzaTv3VYGJ7MJBAXZUTNsXQlhfpIoHo/mc0V5/W/l+mPxmOGTm0hR T7Am59YeUS8aQMl5x5UHCMNYP0qmY/BvXHDGMzCkZo1QO+vvCDqD/XpLRoLuGpmmh80O rkHd4DC/jMCVnA9qxd/KlSruX9lNDDnsw7RRV/pjrK0S/VrQ/pye66x7mwliXuqwK2OP 59QO5WbwnoaBa8DeeKHPcV/krwbmTijMQ+Y0cOONU5ssbfncoHCh2I7bZEvhe3gKEYvB Sphg== 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=s0PZXeeRQYmC65cZZEwBi/cIKv1rcJ/mgpXasGajJIc=; b=IB9ANe5/mBb7lqC6y+SMkGpYT0SmBLU3kaLI8bGAi6vaLZWdJzRkYE9qRlGZc5TDUU FGGqQ7symBQ+aN410KkzIFS8jGurKLtWXYn107A+10nGVXT4mLMNE9yxY1A3PfVn5xi3 tPxkVj3jzZQ/SRsJpsQ/RTlfHu6Os3JeAbgIuZ4jL1LoSYIww2od9REIBi3iEGnLz0yD gpaaf9EfFV3e+g/0DuQNiukn20x6RonwY/WlL0/HMuxFzTLA6q4Ju5r+aWuKTj4aN7kJ zFGURAew4MrNyCmYLRprIcFUZ6k0fljk49z/S0SdVe4iUMqEVd7mK/+cQixyaqbkWBPc SXyA== X-Gm-Message-State: APjAAAVWw8AmuqGy+DcWBkIwBOAuCn0/wrK3He/v87tPA5lVZSUHmLbf 9vQmU4L/MM/W8GOI0NaBsF2fFwW2OHS8Ng3vlPkBWw== X-Google-Smtp-Source: APXvYqwpCJZNMUXcCBa1DqCDUjeT++auW28uh1mAsgK+IW0jnqKdNO15/SCYS26Gz9MJz5SMZ5vR+6MXBhU2CUwCdbY= X-Received: by 2002:a05:6830:1e31:: with SMTP id t17mr10254849otr.201.1570199746180; Fri, 04 Oct 2019 07:35:46 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a4a:458d:0:0:0:0:0 with HTTP; Fri, 4 Oct 2019 07:35:45 -0700 (PDT) In-Reply-To: <0a330e4a-9b8b-7678-cb54-a379f1e4b0bc@FreeBSD.org> References: <0a330e4a-9b8b-7678-cb54-a379f1e4b0bc@FreeBSD.org> From: Mateusz Guzik Date: Fri, 4 Oct 2019 16:35:45 +0200 Message-ID: Subject: Re: atomic_cmpset_64 vs atomic_cas_64 To: Andriy Gapon Cc: freebsd-arch@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 46lC8z6RrVz4RQl X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-6.00 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; REPLY(-4.00)[] X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Oct 2019 14:35:48 -0000 On 10/4/19, Andriy Gapon wrote: > > I see that almost all 64-bit platforms provide atomic_cmpset_64, but > sparc64 > provides atomic_cas_64 (instead?). > I think that the meanings of "cas" and "cmpset" are really the same, but I > am > not sure if there are any differences in that the functions do. > Could anyone who knows that stuff (sparc64 assembly) please shed some > light? > Thanks! > > #define atomic_cas_64(p, e, s) casxa((p), (e), (s), __ASI_ATOMIC) > cas returns the found value, while cmpset throws it away. static __inline int \ atomic_cmpset_ ## name(volatile ptype p, vtype e, vtype s) \ { \ return (((vtype)atomic_cas((p), (e), (s), sz)) == (e)); \ } Just use fcmpset instead. -- Mateusz Guzik From owner-freebsd-arch@freebsd.org Fri Oct 4 14:37:41 2019 Return-Path: Delivered-To: freebsd-arch@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 2042E130518 for ; Fri, 4 Oct 2019 14:37:41 +0000 (UTC) (envelope-from agapon@gmail.com) Received: from mail-lj1-f170.google.com (mail-lj1-f170.google.com [209.85.208.170]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46lCC829bDz4RX6 for ; Fri, 4 Oct 2019 14:37:40 +0000 (UTC) (envelope-from agapon@gmail.com) Received: by mail-lj1-f170.google.com with SMTP id a22so6798474ljd.0 for ; Fri, 04 Oct 2019 07:37:39 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:openpgp:autocrypt :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=OV7uAFc6v8bpzGh7U4lVobpkQ/K6fgDMyEDE/xRGRgw=; b=ZqgYBSvuZfGT0ShdEiT7roLzTi/4bmoWh+xvjcEakaT91+/ZRkbkY8+06l6DRCEgnR 11MS8OK/AHyr3ql2clg/AbP+VPjkosOB9uNgRbF5KsB0D/39YVJbJclKTBz8umkJM66D MIibBuayEGSk5MUcjp5PbGQxzwXwTcMbiyqt7KawoALSw97o82JJnUGZEFbUqjGDyC5S vE07PF4MjU7VOcY1IuXdB+iuFl0XdS553F/UFedKjG6qPJF4ggEv0wyhCcofySXwHMvy upR29ybCtyxb63ytszF3ax/6PEzJ7d+5KuSbXsmSK96W75d8pjmd0J7WC4vufMiB9Cvq yYqg== X-Gm-Message-State: APjAAAXBcUFPOPsm/18qwEwwb5aJtrAihvSnNmcoCWtNGCOAUDTuW+06 Hy6A6FMLnThlUljSVYDDgzxEc4oxU5w= X-Google-Smtp-Source: APXvYqyrxKe2Rto+GA2LMFPArXjxYO1l7pLNrmOAIDpY4guXotlieStZQsods4ByAc8C3Uq4bZf7mg== X-Received: by 2002:a2e:8603:: with SMTP id a3mr9766098lji.98.1570199857799; Fri, 04 Oct 2019 07:37:37 -0700 (PDT) Received: from [192.168.0.88] (east.meadow.volia.net. [93.72.151.96]) by smtp.googlemail.com with ESMTPSA id w27sm1313145ljd.55.2019.10.04.07.37.37 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 04 Oct 2019 07:37:37 -0700 (PDT) Subject: Re: atomic_cmpset_64 vs atomic_cas_64 To: Mateusz Guzik Cc: freebsd-arch@freebsd.org References: <0a330e4a-9b8b-7678-cb54-a379f1e4b0bc@FreeBSD.org> From: Andriy Gapon Openpgp: preference=signencrypt Autocrypt: addr=avg@FreeBSD.org; prefer-encrypt=mutual; keydata= mQINBFm4LIgBEADNB/3lT7f15UKeQ52xCFQx/GqHkSxEdVyLFZTmY3KyNPQGBtyvVyBfprJ7 mAeXZWfhat6cKNRAGZcL5EmewdQuUfQfBdYmKjbw3a9GFDsDNuhDA2QwFt8BmkiVMRYyvI7l N0eVzszWCUgdc3qqM6qqcgBaqsVmJluwpvwp4ZBXmch5BgDDDb1MPO8AZ2QZfIQmplkj8Y6Z AiNMknkmgaekIINSJX8IzRzKD5WwMsin70psE8dpL/iBsA2cpJGzWMObVTtCxeDKlBCNqM1i gTXta1ukdUT7JgLEFZk9ceYQQMJJtUwzWu1UHfZn0Fs29HTqawfWPSZVbulbrnu5q55R4PlQ /xURkWQUTyDpqUvb4JK371zhepXiXDwrrpnyyZABm3SFLkk2bHlheeKU6Yql4pcmSVym1AS4 dV8y0oHAfdlSCF6tpOPf2+K9nW1CFA8b/tw4oJBTtfZ1kxXOMdyZU5fiG7xb1qDgpQKgHUX8 7Rd2T1UVLVeuhYlXNw2F+a2ucY+cMoqz3LtpksUiBppJhw099gEXehcN2JbUZ2TueJdt1FdS ztnZmsHUXLxrRBtGwqnFL7GSd6snpGIKuuL305iaOGODbb9c7ne1JqBbkw1wh8ci6vvwGlzx rexzimRaBzJxlkjNfMx8WpCvYebGMydNoeEtkWldtjTNVsUAtQARAQABtB5BbmRyaXkgR2Fw b24gPGF2Z0BGcmVlQlNELm9yZz6JAlQEEwEIAD4WIQS+LEO7ngQnXA4Bjr538m7TUc1yjwUC WbgsiAIbIwUJBaOagAULCQgHAgYVCAkKCwIEFgIDAQIeAQIXgAAKCRB38m7TUc1yj+JAEACV l9AK/nOWAt/9cufV2fRj0hdOqB1aCshtSrwHk/exXsDa4/FkmegxXQGY+3GWX3deIyesbVRL rYdtdK0dqJyT1SBqXK1h3/at9rxr9GQA6KWOxTjUFURsU7ok/6SIlm8uLRPNKO+yq0GDjgaO LzN+xykuBA0FlhQAXJnpZLcVfPJdWv7sSHGedL5ln8P8rxR+XnmsA5TUaaPcbhTB+mG+iKFj GghASDSfGqLWFPBlX/fpXikBDZ1gvOr8nyMY9nXhgfXpq3B6QCRYKPy58ChrZ5weeJZ29b7/ QdEO8NFNWHjSD9meiLdWQaqo9Y7uUxN3wySc/YUZxtS0bhAd8zJdNPsJYG8sXgKjeBQMVGuT eCAJFEYJqbwWvIXMfVWop4+O4xB+z2YE3jAbG/9tB/GSnQdVSj3G8MS80iLS58frnt+RSEw/ psahrfh0dh6SFHttE049xYiC+cM8J27Aaf0i9RflyITq57NuJm+AHJoU9SQUkIF0nc6lfA+o JRiyRlHZHKoRQkIg4aiKaZSWjQYRl5Txl0IZUP1dSWMX4s3XTMurC/pnja45dge/4ESOtJ9R 8XuIWg45Oq6MeIWdjKddGhRj3OohsltKgkEU3eLKYtB6qRTQypHHUawCXz88uYt5e3w4V16H lCpSTZV/EVHnNe45FVBlvK7k7HFfDDkryLkCDQRZuCyIARAAlq0slcsVboY/+IUJdcbEiJRW be9HKVz4SUchq0z9MZPX/0dcnvz/gkyYA+OuM78dNS7Mbby5dTvOqfpLJfCuhaNYOhlE0wY+ 1T6Tf1f4c/uA3U/YiadukQ3+6TJuYGAdRZD5EqYFIkreARTVWg87N9g0fT9BEqLw9lJtEGDY EWUE7L++B8o4uu3LQFEYxcrb4K/WKmgtmFcm77s0IKDrfcX4doV92QTIpLiRxcOmCC/OCYuO jB1oaaqXQzZrCutXRK0L5XN1Y1PYjIrEzHMIXmCDlLYnpFkK+itlXwlE2ZQxkfMruCWdQXye syl2fynAe8hvp7Mms9qU2r2K9EcJiR5N1t1C2/kTKNUhcRv7Yd/vwusK7BqJbhlng5ZgRx0m WxdntU/JLEntz3QBsBsWM9Y9wf2V4tLv6/DuDBta781RsCB/UrU2zNuOEkSixlUiHxw1dccI 6CVlaWkkJBxmHX22GdDFrcjvwMNIbbyfQLuBq6IOh8nvu9vuItup7qemDG3Ms6TVwA7BD3j+ 3fGprtyW8Fd/RR2bW2+LWkMrqHffAr6Y6V3h5kd2G9Q8ZWpEJk+LG6Mk3fhZhmCnHhDu6CwN MeUvxXDVO+fqc3JjFm5OxhmfVeJKrbCEUJyM8ESWLoNHLqjywdZga4Q7P12g8DUQ1mRxYg/L HgZY3zfKOqcAEQEAAYkCPAQYAQgAJhYhBL4sQ7ueBCdcDgGOvnfybtNRzXKPBQJZuCyIAhsM BQkFo5qAAAoJEHfybtNRzXKPBVwQAKfFy9P7N3OsLDMB56A4Kf+ZT+d5cIx0Yiaf4n6w7m3i ImHHHk9FIetI4Xe54a2IXh4Bq5UkAGY0667eIs+Z1Ea6I2i27Sdo7DxGwq09Qnm/Y65ADvXs 3aBvokCcm7FsM1wky395m8xUos1681oV5oxgqeRI8/76qy0hD9WR65UW+HQgZRIcIjSel9vR XDaD2HLGPTTGr7u4v00UeTMs6qvPsa2PJagogrKY8RXdFtXvweQFz78NbXhluwix2Tb9ETPk LIpDrtzV73CaE2aqBG/KrboXT2C67BgFtnk7T7Y7iKq4/XvEdDWscz2wws91BOXuMMd4c/c4 OmGW9m3RBLufFrOag1q5yUS9QbFfyqL6dftJP3Zq/xe+mr7sbWbhPVCQFrH3r26mpmy841ym dwQnNcsbIGiBASBSKksOvIDYKa2Wy8htPmWFTEOPRpFXdGQ27awcjjnB42nngyCK5ukZDHi6 w0qK5DNQQCkiweevCIC6wc3p67jl1EMFY5+z+zdTPb3h7LeVnGqW0qBQl99vVFgzLxchKcl0 R/paSFgwqXCZhAKMuUHncJuynDOP7z5LirUeFI8qsBAJi1rXpQoLJTVcW72swZ42IdPiboqx NbTMiNOiE36GqMcTPfKylCbF45JNX4nF9ElM0E+Y8gi4cizJYBRr2FBJgay0b9Cp Message-ID: Date: Fri, 4 Oct 2019 17:37:36 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 46lCC829bDz4RX6 X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of agapon@gmail.com designates 209.85.208.170 as permitted sender) smtp.mailfrom=agapon@gmail.com X-Spamd-Result: default: False [-3.19 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17]; RCVD_COUNT_THREE(0.00)[3]; RCPT_COUNT_TWO(0.00)[2]; FORGED_SENDER(0.30)[avg@FreeBSD.org,agapon@gmail.com]; FREEMAIL_TO(0.00)[gmail.com]; RECEIVED_SPAMHAUS_PBL(0.00)[96.151.72.93.khpj7ygk5idzvmvt5x4ziurxhy.zen.dq.spamhaus.net : 127.0.0.10]; MIME_TRACE(0.00)[0:+]; R_DKIM_NA(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; FROM_NEQ_ENVFROM(0.00)[avg@FreeBSD.org,agapon@gmail.com]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arch@freebsd.org]; DMARC_NA(0.00)[FreeBSD.org]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[170.208.85.209.list.dnswl.org : 127.0.5.0]; IP_SCORE(-1.19)[ip: (-0.48), ipnet: 209.85.128.0/17(-3.27), asn: 15169(-2.16), country: US(-0.05)]; RWL_MAILSPIKE_POSSIBLE(0.00)[170.208.85.209.rep.mailspike.net : 127.0.0.17]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Oct 2019 14:37:41 -0000 On 04/10/2019 17:35, Mateusz Guzik wrote: > On 10/4/19, Andriy Gapon wrote: >> >> I see that almost all 64-bit platforms provide atomic_cmpset_64, but >> sparc64 >> provides atomic_cas_64 (instead?). >> I think that the meanings of "cas" and "cmpset" are really the same, but I >> am >> not sure if there are any differences in that the functions do. >> Could anyone who knows that stuff (sparc64 assembly) please shed some >> light? >> Thanks! >> >> #define atomic_cas_64(p, e, s) casxa((p), (e), (s), __ASI_ATOMIC) >> > > cas returns the found value, while cmpset throws it away. Ah, now it's obvious. Thank you! > static __inline int \ > atomic_cmpset_ ## name(volatile ptype p, vtype e, vtype s) \ > { \ > return (((vtype)atomic_cas((p), (e), (s), sz)) == (e)); \ > } > > > Just use fcmpset instead. fcmpset really beats both in its convenience. -- Andriy Gapon From owner-freebsd-arch@freebsd.org Sat Oct 5 15:29:08 2019 Return-Path: Delivered-To: freebsd-arch@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 8B635135BC9 for ; Sat, 5 Oct 2019 15:29:08 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-qk1-x734.google.com (mail-qk1-x734.google.com [IPv6:2607:f8b0:4864:20::734]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46lrJ31CWLz3L9F for ; Sat, 5 Oct 2019 15:29:06 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-qk1-x734.google.com with SMTP id x134so8732024qkb.0 for ; Sat, 05 Oct 2019 08:29:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to; bh=l9IOvZSZAedAv4HRcrZFTCHQc0C6UTjkCnUpcKy6DRE=; b=S4qg4F2J5Ths/3sPXXEppfCP3c5KejKWnP0gnqzVPuCOz3M4+ZqVeLQssZHeyo0SN5 FBItsptx/SsuhJ3EHoDYStylVtYhS5BUUF0vJSkYLf4hrxbyGEm9SQe2J1N4WZR7fH19 +32X6oxURuB5o4eRrFZU57Kt9yLFoLz1ss6Ogtkmpmcv4R6mc/YHVHlQNN1akjoNSdUd GUifIIQYLP4LEq7BcSLr8fDOfC8Cc+rp1lvQVySIbigUpuZdys5KePYDABQ6BPWoQZA6 8arvMRDZLp2e6GOUwGNJKzJGYwdkiuVhGXy2CGVrFiEMwReGi+NXDd0hJstelW5mRaj+ 9EUQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=l9IOvZSZAedAv4HRcrZFTCHQc0C6UTjkCnUpcKy6DRE=; b=Hw6x5QmeDQe24Veqdt6p/IZ1jjSIfb73Ms1Bf4WnwIwViSK/E79yppfqU1JJkyUohR 0Kdjmd5rOwviaiZi55ovgv+R1zPwMAP2cbwPrJQe5v36KkuuNf2vj/MeB/2hTM4YELvV 151FkF+Gvo6bBJe6SkE4EpqdlM55gqpDLhlpqMptkfeN/tYXxc9NHUQBcGAJycm7uq/u 40VQ58yKtOMjnzCRsfS1fn/c3uBRHuV4+lOOYMJAqoaj5o5c7TUCgaUgsTiHZL1iHhZb w9zt+ZK8bs2dF6r4SK/u8AHKyn+S6xB+esupvZkgNdyaza9knusBzG95vWw/TMnQIiQF RBqg== X-Gm-Message-State: APjAAAV8FpoqOmFO9h2G6KCUEvbE8lTps+SNx42mtx+bFMUrI8Nw5T8D JqH398mRW/JxO9K7sApb6iM80QxROCUcrEPdkt0NfQ2+ X-Google-Smtp-Source: APXvYqxi4MeIu3vCjoPVjNt1Q9VKV0oOqCRFIft0X/zmdGvV6PmsRvp07UPyX0NvNfngrIQmLQk2UrKip6n9gNPOeLw= X-Received: by 2002:a37:6787:: with SMTP id b129mr16103302qkc.60.1570289345418; Sat, 05 Oct 2019 08:29:05 -0700 (PDT) MIME-Version: 1.0 From: Warner Losh Date: Sat, 5 Oct 2019 09:28:53 -0600 Message-ID: Subject: New CPUTYPE default for i386 port To: freebsd-arch@freebsd.org X-Rspamd-Queue-Id: 46lrJ31CWLz3L9F X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=bsdimp-com.20150623.gappssmtp.com header.s=20150623 header.b=S4qg4F2J; dmarc=none; spf=none (mx1.freebsd.org: domain of wlosh@bsdimp.com has no SPF policy when checking 2607:f8b0:4864:20::734) smtp.mailfrom=wlosh@bsdimp.com X-Spamd-Result: default: False [-4.83 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[bsdimp-com.20150623.gappssmtp.com:s=20150623]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arch@freebsd.org]; TO_DN_NONE(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; DMARC_NA(0.00)[bsdimp.com]; DKIM_TRACE(0.00)[bsdimp-com.20150623.gappssmtp.com:+]; RCVD_IN_DNSWL_NONE(0.00)[4.3.7.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org : 127.0.5.0]; R_SPF_NA(0.00)[]; FORGED_SENDER(0.30)[imp@bsdimp.com,wlosh@bsdimp.com]; MIME_TRACE(0.00)[0:+,1:+,2:~]; IP_SCORE(-2.83)[ip: (-9.36), ipnet: 2607:f8b0::/32(-2.56), asn: 15169(-2.15), country: US(-0.05)]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; FROM_NEQ_ENVFROM(0.00)[imp@bsdimp.com,wlosh@bsdimp.com]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Oct 2019 15:29:08 -0000 For a variety of reasons, the time has come to change the default code generation arch from i486 to i686 on our i386 port. No actual code removal is planned as part of this effort. Only the default is doing changed for clang. The practical upshot of this for our i386 users will be zero for almost everybody. For the tiny sliver of people planning to deploy FreeBSD on a i486 or i586 core, a simple addition of CPUTYPE=xxxx to /etc/make.conf is all that is needed for the src side of things. They will need to setup their own poudriere instance and create their own pkg repo to build whatever packages are required for their deployment. It's my belief that even in the trailing edge long tail embedded deployment segment of our user base this will cause no issues. All deployments there I'm aware of have moved of i486 class CPUs and the one 586 class core deployment I know of has no plans to update that to FreeBSD 11, let alone newer. There are a number of advantages to doing this which have been articulated at length in other discussions. Briefly we get better code generation for CPUs people use and we avoid some test failures in llvm 9.0 because i486 doesn't have 64-bot atomics. Comments? Warner From owner-freebsd-arch@freebsd.org Sat Oct 5 17:03:58 2019 Return-Path: Delivered-To: freebsd-arch@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 775091380E4 for ; Sat, 5 Oct 2019 17:03:58 +0000 (UTC) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: from gndrsh.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 46ltPT2Bz9z3R0H for ; Sat, 5 Oct 2019 17:03:56 +0000 (UTC) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: from gndrsh.dnsmgr.net (localhost [127.0.0.1]) by gndrsh.dnsmgr.net (8.13.3/8.13.3) with ESMTP id x95H3r5q063999; Sat, 5 Oct 2019 10:03:53 -0700 (PDT) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: (from freebsd-rwg@localhost) by gndrsh.dnsmgr.net (8.13.3/8.13.3/Submit) id x95H3rsN063998; Sat, 5 Oct 2019 10:03:53 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201910051703.x95H3rsN063998@gndrsh.dnsmgr.net> Subject: Re: New CPUTYPE default for i386 port In-Reply-To: To: Warner Losh Date: Sat, 5 Oct 2019 10:03:53 -0700 (PDT) CC: freebsd-arch@freebsd.org X-Mailer: ELM [version 2.4ME+ PL121h (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Rspamd-Queue-Id: 46ltPT2Bz9z3R0H X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of freebsd-rwg@gndrsh.dnsmgr.net has no SPF policy when checking 69.59.192.140) smtp.mailfrom=freebsd-rwg@gndrsh.dnsmgr.net X-Spamd-Result: default: False [0.83 / 15.00]; ARC_NA(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; NEURAL_HAM_LONG(-0.76)[-0.761,0]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; DMARC_NA(0.00)[dnsmgr.net]; AUTH_NA(1.00)[]; NEURAL_SPAM_MEDIUM(0.65)[0.648,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; R_SPF_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:13868, ipnet:69.59.192.0/19, country:US]; MID_RHS_MATCH_FROM(0.00)[]; IP_SCORE(0.04)[ip: (0.15), ipnet: 69.59.192.0/19(0.07), asn: 13868(0.04), country: US(-0.05)]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Oct 2019 17:03:58 -0000 > For a variety of reasons, the time has come to change the default code > generation arch from i486 to i686 on our i386 port. No actual code removal > is planned as part of this effort. Only the default is doing changed for > clang. > > The practical upshot of this for our i386 users will be zero for almost > everybody. For the tiny sliver of people planning to deploy FreeBSD on a > i486 or i586 core, a simple addition of CPUTYPE=xxxx to /etc/make.conf is > all that is needed for the src side of things. They will need to setup > their own poudriere instance and create their own pkg repo to build > whatever packages are required for their deployment. > > It's my belief that even in the trailing edge long tail embedded deployment > segment of our user base this will cause no issues. All deployments there > I'm aware of have moved of i486 class CPUs and the one 586 class core > deployment I know of has no plans to update that to FreeBSD 11, let alone > newer. > > There are a number of advantages to doing this which have been articulated > at length in other discussions. Briefly we get better code generation for > CPUs people use and we avoid some test failures in llvm 9.0 because i486 > doesn't have 64-bot atomics. > > Comments? Please provide some type of eol statement in the next release cycle release notes that base and packages are no longer usable on the class of i386 lower than i686, with the above rationale and work around. >From the above it does sound as if you plan to MFC this back as far as 11? What is the error condition one sees if you try to boot release media built i686 on a i386/i486 system? It needs to be something sinceable and preferable some direction to work around, not just some random illegal instruction panic, PLEASE! Other than those 2 issues and 1 question I have no objection to doing this. Regards, -- Rod Grimes rgrimes@freebsd.org From owner-freebsd-arch@freebsd.org Sat Oct 5 17:30:03 2019 Return-Path: Delivered-To: freebsd-arch@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 79A6513889A for ; Sat, 5 Oct 2019 17:30:03 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-qk1-x730.google.com (mail-qk1-x730.google.com [IPv6:2607:f8b0:4864:20::730]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46ltzY6gxNz3xNq for ; Sat, 5 Oct 2019 17:30:01 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-qk1-x730.google.com with SMTP id u22so8840124qkk.11 for ; Sat, 05 Oct 2019 10:30:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=/7RheVxT7cEr+Dr/0V2Tr922j+2F8iT0una6BEElrdU=; b=aDZFKbtokOGCswN3zX3RxhbAnYl5RjyeagwEIp6cG5jbTgj8OgBfT7yho+Smq3Xs5Z MHiQOh5T3EasUAxjocTlzcG3beal7/qEvXelHcpEOr9RCgT8OM8hRYILdMCJq0/+B1rI 9As1QsueoCXrO5pfoVrZr/qNQN4uSHBU7U+JMNRnvjJllNOHb+Bw7mYenvr6Cl1hi+H/ axEKKsjB4h0RudHWpxHf6vTg5Ftik95tDpa7WRrS+lgL3erEgYslaDyLSpV8w/X7GS+T WjqaZzJ4YPnpDpM8woZUQ00fy4LJZnP5C4LclrO9IbyAGN3DuxH8GRb0+w+TAjD1MdFo Zp9g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=/7RheVxT7cEr+Dr/0V2Tr922j+2F8iT0una6BEElrdU=; b=Hyv8CdcLbKh9HLq503YoOkAgTWIWVyHoWy8N+3lZte8AzIAUVSoVrC2DNThW2kTlGG zjC6fWjHMEYZftNlymteA8CHhZ2ThAKNnHZ4hmxq3yl4Mei70CPs5Zs9Dj4udbexRIaZ ATBeycWTsYvebpVbiuJjy8pOAz1NMej61w9vbbpEdAc0AK9ccXe+/mpcV9NJd/yejosR lgjfOUuDNCPyIkbWQ8w+1fLR71eYw/6i+0n9I/FiwkkRvtrj6QDxp6Y6IboZxGtdqDYN WflcN8ZxbRtuFdJxdIIssJ+dK12I17vBGdLK2zpZJHPw9QvI3HwY8L3xB9eQUkIUUdTB iKyw== X-Gm-Message-State: APjAAAWFYujNraHr4ZKq1Gx5uEJcHD7FwGVa3JZkWSkGQlYnSSnIQi55 W7oOa+DXFE731uQH05EUZqUKLeeh/IIQiDeE/K0ubw== X-Google-Smtp-Source: APXvYqws5mrQydz8MTMDkxjtdj3Rd0oDhcKVrP+s3pyY8HaP+tTqCZo1/8gvbbPw2Sy2qEDDNoNH4QlgvL7PDQatLuA= X-Received: by 2002:a05:620a:12b6:: with SMTP id x22mr16003669qki.495.1570296599710; Sat, 05 Oct 2019 10:29:59 -0700 (PDT) MIME-Version: 1.0 References: <201910051703.x95H3rsN063998@gndrsh.dnsmgr.net> In-Reply-To: <201910051703.x95H3rsN063998@gndrsh.dnsmgr.net> From: Warner Losh Date: Sat, 5 Oct 2019 11:29:47 -0600 Message-ID: Subject: Re: New CPUTYPE default for i386 port To: "Rodney W. Grimes" Cc: freebsd-arch@freebsd.org X-Rspamd-Queue-Id: 46ltzY6gxNz3xNq X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=bsdimp-com.20150623.gappssmtp.com header.s=20150623 header.b=aDZFKbto; dmarc=none; spf=none (mx1.freebsd.org: domain of wlosh@bsdimp.com has no SPF policy when checking 2607:f8b0:4864:20::730) smtp.mailfrom=wlosh@bsdimp.com X-Spamd-Result: default: False [-4.83 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[bsdimp-com.20150623.gappssmtp.com:s=20150623]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arch@freebsd.org]; DMARC_NA(0.00)[bsdimp.com]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[bsdimp-com.20150623.gappssmtp.com:+]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[0.3.7.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org : 127.0.5.0]; R_SPF_NA(0.00)[]; FORGED_SENDER(0.30)[imp@bsdimp.com,wlosh@bsdimp.com]; MIME_TRACE(0.00)[0:+,1:+,2:~]; IP_SCORE(-2.83)[ip: (-9.37), ipnet: 2607:f8b0::/32(-2.56), asn: 15169(-2.15), country: US(-0.05)]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; FROM_NEQ_ENVFROM(0.00)[imp@bsdimp.com,wlosh@bsdimp.com]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Oct 2019 17:30:03 -0000 On Sat, Oct 5, 2019, 11:03 AM Rodney W. Grimes < freebsd-rwg@gndrsh.dnsmgr.net> wrote: > > For a variety of reasons, the time has come to change the default code > > generation arch from i486 to i686 on our i386 port. No actual code > removal > > is planned as part of this effort. Only the default is doing changed for > > clang. > > > > The practical upshot of this for our i386 users will be zero for almost > > everybody. For the tiny sliver of people planning to deploy FreeBSD on a > > i486 or i586 core, a simple addition of CPUTYPE=xxxx to /etc/make.conf is > > all that is needed for the src side of things. They will need to setup > > their own poudriere instance and create their own pkg repo to build > > whatever packages are required for their deployment. > > > > It's my belief that even in the trailing edge long tail embedded > deployment > > segment of our user base this will cause no issues. All deployments there > > I'm aware of have moved of i486 class CPUs and the one 586 class core > > deployment I know of has no plans to update that to FreeBSD 11, let alone > > newer. > > > > There are a number of advantages to doing this which have been > articulated > > at length in other discussions. Briefly we get better code generation for > > CPUs people use and we avoid some test failures in llvm 9.0 because i486 > > doesn't have 64-bot atomics. > > > > Comments? > > Please provide some type of eol statement in the next release cycle release > notes that base and packages are no longer usable on the class of i386 > lower > than i686, with the above rationale and work around. > Sure. Of course. >From the above it does sound as if you plan to MFC this back as far as 11? > No plans to MFC. What is the error condition one sees if you try to boot release media > built i686 on a i386/i486 system? It needs to be something sinceable > and preferable some direction to work around, not just some random illegal > instruction panic, PLEASE! > We should remove 486 and 586 CPU support from GENERIC and then the kernel would say the CPU was unsupported. But only if there were no illegal instructions. However, GENERIC already requires 128MB or 256MB or more to boot, which is beyond what 486 and 586 could have on them so it may be a moot point. Other than those 2 issues and 1 question I have no objection to doing this. > Regards, > -- > Rod Grimes > rgrimes@freebsd.org > From owner-freebsd-arch@freebsd.org Sat Oct 5 17:34:15 2019 Return-Path: Delivered-To: freebsd-arch@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 C8CEE138A9C for ; Sat, 5 Oct 2019 17:34:15 +0000 (UTC) (envelope-from shawn.webb@hardenedbsd.org) Received: from mail-qt1-x836.google.com (mail-qt1-x836.google.com [IPv6:2607:f8b0:4864:20::836]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46lv4Q3jfWz3xm5 for ; Sat, 5 Oct 2019 17:34:14 +0000 (UTC) (envelope-from shawn.webb@hardenedbsd.org) Received: by mail-qt1-x836.google.com with SMTP id u40so13251897qth.11 for ; Sat, 05 Oct 2019 10:34:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hardenedbsd.org; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=JKJE8CSbdL1kbtlIRlCTpounZIQkBNKNvy979si0qBM=; b=gsqPU698zO1GYlrQX2M5r9R+qNnGFdRneMDJeyUhE3GPQmuKhtLXteVAv0NJXcop0X A8CX992NUquRq1+MYFTmbfJPxyl3/J9viw4Ez13NLjtxUqvjKkvwEJlBJ3Nkwp+EsGUr sswy95YgjwBGlkqTQ6vYZBQTDL3CRx9bVWEIrATDal+T1Cjb3RIrIyA/Xb7nuzXxENYu 66Wfw8LxpT8c4ZsxUIAEkBYsRSCjXFGYo1oh/pQOomqeP9opMxTTV1QC5by4y3Cuo5Uv 9Y9o9cgUawuFgAmf8KMnNETlpcIeQP9M6zRr2dx574cODRAwMdJN9FzH2BIAg88KSbR/ D7bw== 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=JKJE8CSbdL1kbtlIRlCTpounZIQkBNKNvy979si0qBM=; b=m0c7H8/SuymWOo3LOVLBIB9LXSTsMiU7EwvbiHmFQ0ntzjkpdxkx5wDcwuylp9vtfG 7JAbnOGciL9o0M5IC4F0Vm8cIfSwIn46Q5nBBDF4/XbgKxR1RUi/jL3sMPMTEAZqUu+P 612shfa/594r8ZPONWyHZHMe37IxgYWLrD96gcXo+USSY6f6VOAqq3big+4tSWRyg8NJ C1505lYiaIvfQQtoGypygvoRAvaOJYqcOZK47KhbIJ/XWDD7Mm/F3N8hDFRZHZ8454B8 hfFZQsErxPE+iFP+WdjyE8GiEdZzsOmecnNksd5Q93J8gHUk91zecY2tIqS1badXhhtJ bqOA== X-Gm-Message-State: APjAAAW5Iu634o8yIfYJ7y0uHWyIryPkJUW30Lx2VScNFymcOuhMPbiA gvnwmsnpRDpY0ALu9+VppzeAWA== X-Google-Smtp-Source: APXvYqyWOzJXfeUbNS17gbPEsJ5q+C48S8jW9NCiucNw1/Y3ufUKZ6Eu5HT0mYYO+djR+eTskCptdA== X-Received: by 2002:ac8:6696:: with SMTP id d22mr22492396qtp.21.1570296852938; Sat, 05 Oct 2019 10:34:12 -0700 (PDT) Received: from mutt-hbsd (pool-100-16-231-224.bltmmd.fios.verizon.net. [100.16.231.224]) by smtp.gmail.com with ESMTPSA id b1sm3989136qtr.17.2019.10.05.10.34.12 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sat, 05 Oct 2019 10:34:12 -0700 (PDT) Date: Sat, 5 Oct 2019 13:34:11 -0400 From: Shawn Webb To: Warner Losh Cc: freebsd-arch@freebsd.org Subject: Re: New CPUTYPE default for i386 port Message-ID: <20191005173411.l6gs3kszs7zcgfey@mutt-hbsd> References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="22iic2qs5ebepwwt" Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD mutt-hbsd 13.0-CURRENT-HBSD FreeBSD 13.0-CURRENT-HBSD r352488+2a20025064d4-c272097(hardened/current/master) HARDENEDBSD-13-CURRENT amd64 X-PGP-Key: http://pgp.mit.edu/pks/lookup?op=vindex&search=0xFF2E67A277F8E1FA User-Agent: NeoMutt/20180716 X-Rspamd-Queue-Id: 46lv4Q3jfWz3xm5 X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org; dkim=pass header.d=hardenedbsd.org header.s=google header.b=gsqPU698; dmarc=none; spf=pass (mx1.freebsd.org: domain of shawn.webb@hardenedbsd.org designates 2607:f8b0:4864:20::836 as permitted sender) smtp.mailfrom=shawn.webb@hardenedbsd.org X-Spamd-Result: default: False [-6.91 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[hardenedbsd.org:s=google]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.20)[multipart/signed,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arch@freebsd.org]; DMARC_NA(0.00)[hardenedbsd.org]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[hardenedbsd.org:+]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[6.3.8.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org : 127.0.5.0]; SIGNED_PGP(-2.00)[]; FROM_EQ_ENVFROM(0.00)[]; MID_RHS_NOT_FQDN(0.50)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; RCVD_TLS_ALL(0.00)[]; IP_SCORE(-2.81)[ip: (-9.26), ipnet: 2607:f8b0::/32(-2.56), asn: 15169(-2.15), country: US(-0.05)]; RECEIVED_SPAMHAUS_PBL(0.00)[224.231.16.100.khpj7ygk5idzvmvt5x4ziurxhy.zen.dq.spamhaus.net : 127.0.0.10] X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Oct 2019 17:34:15 -0000 --22iic2qs5ebepwwt Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Oct 05, 2019 at 09:28:53AM -0600, Warner Losh wrote: > For a variety of reasons, the time has come to change the default code > generation arch from i486 to i686 on our i386 port. No actual code removal > is planned as part of this effort. Only the default is doing changed for > clang. >=20 > The practical upshot of this for our i386 users will be zero for almost > everybody. For the tiny sliver of people planning to deploy FreeBSD on a > i486 or i586 core, a simple addition of CPUTYPE=3Dxxxx to /etc/make.conf = is > all that is needed for the src side of things. They will need to setup > their own poudriere instance and create their own pkg repo to build > whatever packages are required for their deployment. >=20 > It's my belief that even in the trailing edge long tail embedded deployme= nt > segment of our user base this will cause no issues. All deployments there > I'm aware of have moved of i486 class CPUs and the one 586 class core > deployment I know of has no plans to update that to FreeBSD 11, let alone > newer. >=20 > There are a number of advantages to doing this which have been articulated > at length in other discussions. Briefly we get better code generation for > CPUs people use and we avoid some test failures in llvm 9.0 because i486 > doesn't have 64-bot atomics. >=20 > Comments? Full disclosure: I personally don't care about 32-bit architectures. Feel free to ignore me based on that. ;-) I'm curious about the possibilities regarding 64-bit time_t on 32-bit Intel systems. Thanks, --=20 Shawn Webb Cofounder / Security Engineer HardenedBSD Tor-ified Signal: +1 443-546-8752 Tor+XMPP+OTR: lattera@is.a.hacker.sx GPG Key ID: 0xFF2E67A277F8E1FA GPG Key Fingerprint: D206 BB45 15E0 9C49 0CF9 3633 C85B 0AF8 AB23 0FB2 --22iic2qs5ebepwwt Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEA6TL67gupaZ9nzhT/y5nonf44foFAl2Y1AoACgkQ/y5nonf4 4forYg//bYjJ3YcFYG18R+ZAWCVNXYOxf0N6GJTZoilAbosgRU9JWRQFgiyxc9gy C38BTcG8ydZh38pls9fJQF5htqokFxu2xhK8Nw4XGhmyScK/XdiUcUMXIDSFRygA DxEQsr5Um5d+rEIt7pqBBN4fiVBHT95h6MnhI0hVcoxSubDK2sO0OPT1GvoLcq+E /m3koORJOEWbGlNKjb9NuvUgqLAQiH3GxgC5vmlVZQlZmEFC4p7HYhHow4NWi7SX HNCEXE5M7hzMVbdXvQRc/5uAF5KU5dsj51CU0rzuDZ/uAzluZX46S5TI69R1dp2B fE3T84CxTEAb34hcGIZOcKgEnHPCYdA1fpBfCbvjIZRQ/3stzERCcLRiJCdjOAXY RWU24agyNoS6rjiCvGho2TbU6jpY+tSo+kuTbvCGWgSYto3Zb0X90nUYCLK8Vp9r cLEIanN/5C5y9GAjfkdTH4FwnlEWHl9pthZ0w9GacpaAE5lxIQKez3SSWrGb1zT7 vYKaOygOb4KU4cECxwDJdTBCWcWqLJQa0K82Qf+FONrzGbfJoPXeoyalCEcB5Jjq poaaMOtyelW4N1rfrsyXAt6AslWx2Ezv7RFFyI+I/p2JkESGp3Zn888dk0naqm4C nTEZcbREHzS6ORNOBVS9A76HtbjUDvoSafvORExflCGHeJ/VeyA= =niQ1 -----END PGP SIGNATURE----- --22iic2qs5ebepwwt-- From owner-freebsd-arch@freebsd.org Sat Oct 5 18:19:55 2019 Return-Path: Delivered-To: freebsd-arch@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 B06B41398EF for ; Sat, 5 Oct 2019 18:19:55 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-qt1-x830.google.com (mail-qt1-x830.google.com [IPv6:2607:f8b0:4864:20::830]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46lw565XwTz40ld for ; Sat, 5 Oct 2019 18:19:54 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-qt1-x830.google.com with SMTP id u40so13348730qth.11 for ; Sat, 05 Oct 2019 11:19:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=bckf7Pgf1HT6Kc5mhZ7mPGUE+8ARSsf7cl5GGoRqvBo=; b=OMoSfAalUbL8ntaM0PSSsYXOMxCzTqJr4WiWcbLFMMcRaG1SHWEO4fAwxR9LGqfYYk qjMf5+RfZ65RnWMz5GapdJHKKcCE4cDFOz05A4DBob+o9DESxDcf/l12ubOuql4YZp0n DeT0JKaaMVRLmh2XMsX4xAJpAIXKQZU5/r872+ZrSftkS70ci2p/xXznnt5CaQNTnEAg LmqeBS2KVhMhU/mlqAbXawLDoTv8a/kXVpEbZElI1rZ8dpVdha87qSReLedvbUZQwHjW HV0HzuEWMspgfVbfxmvfBBWYJmTRHqIpWO/GLDaelPJ8eYwgXFywazVJCc3QcjHsDKnI yaRw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=bckf7Pgf1HT6Kc5mhZ7mPGUE+8ARSsf7cl5GGoRqvBo=; b=jeYGPciIPPdbbQkK3xEpqdr7/HNMg9oU9X9BSHdxC6tAhzKlyfDhtX5O3xUWbFLxjl nIV7tN+IlGgb7AWaBFcbre1d4stw2imguFSGBdYAYCo3BZ5TMDntlaH+JflP28wPR80d trZMPvNLFiPIkjKNvNU5yerumrswwIOTfqNxCBYd8gs2o/i3K/bJsWz/PMbsNGq1jXE4 OteSIyv9Lt9V4J1mBdjO6kFbjgw0TMq6l0WneOmTCgVrU6V9TBsSMOac4wiFXlS1pFSX LuUwsTbBvIs11uEePw8u5gqXyp8lTL23MGQXFObQlT3I2cm1suK0g213JKEuQ74abW8w BuiA== X-Gm-Message-State: APjAAAWCpArR1cVhwzrZY1ixgDX+BfGyij/kUkGF4h2s0m+X+TpR39Vt c2ZTDZyS7SEyNbzDVUNwo9SZNELj0ZUxzQFZTtJ6IgOF X-Google-Smtp-Source: APXvYqxpxnWNJ/Vzasu2bxWqx29jdlabgTfuGxB3yct6crmE7PtFcVJlHYh3aOsulffnCXYKLYIQ7gSJnR5y6y/nC1k= X-Received: by 2002:ac8:3364:: with SMTP id u33mr22418997qta.187.1570299593461; Sat, 05 Oct 2019 11:19:53 -0700 (PDT) MIME-Version: 1.0 References: <20191005173411.l6gs3kszs7zcgfey@mutt-hbsd> In-Reply-To: <20191005173411.l6gs3kszs7zcgfey@mutt-hbsd> From: Warner Losh Date: Sat, 5 Oct 2019 12:19:41 -0600 Message-ID: Subject: Re: New CPUTYPE default for i386 port To: Shawn Webb Cc: freebsd-arch@freebsd.org X-Rspamd-Queue-Id: 46lw565XwTz40ld X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=bsdimp-com.20150623.gappssmtp.com header.s=20150623 header.b=OMoSfAal; dmarc=none; spf=none (mx1.freebsd.org: domain of wlosh@bsdimp.com has no SPF policy when checking 2607:f8b0:4864:20::830) smtp.mailfrom=wlosh@bsdimp.com X-Spamd-Result: default: False [-4.82 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[bsdimp-com.20150623.gappssmtp.com:s=20150623]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arch@freebsd.org]; DMARC_NA(0.00)[bsdimp.com]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[bsdimp-com.20150623.gappssmtp.com:+]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[0.3.8.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org : 127.0.5.0]; R_SPF_NA(0.00)[]; FORGED_SENDER(0.30)[imp@bsdimp.com,wlosh@bsdimp.com]; MIME_TRACE(0.00)[0:+,1:+,2:~]; IP_SCORE(-2.82)[ip: (-9.33), ipnet: 2607:f8b0::/32(-2.56), asn: 15169(-2.15), country: US(-0.05)]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; FROM_NEQ_ENVFROM(0.00)[imp@bsdimp.com,wlosh@bsdimp.com]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Oct 2019 18:19:55 -0000 On Sat, Oct 5, 2019, 11:34 AM Shawn Webb wrote: > On Sat, Oct 05, 2019 at 09:28:53AM -0600, Warner Losh wrote: > > For a variety of reasons, the time has come to change the default code > > generation arch from i486 to i686 on our i386 port. No actual code > removal > > is planned as part of this effort. Only the default is doing changed for > > clang. > > > > The practical upshot of this for our i386 users will be zero for almost > > everybody. For the tiny sliver of people planning to deploy FreeBSD on a > > i486 or i586 core, a simple addition of CPUTYPE=xxxx to /etc/make.conf is > > all that is needed for the src side of things. They will need to setup > > their own poudriere instance and create their own pkg repo to build > > whatever packages are required for their deployment. > > > > It's my belief that even in the trailing edge long tail embedded > deployment > > segment of our user base this will cause no issues. All deployments there > > I'm aware of have moved of i486 class CPUs and the one 586 class core > > deployment I know of has no plans to update that to FreeBSD 11, let alone > > newer. > > > > There are a number of advantages to doing this which have been > articulated > > at length in other discussions. Briefly we get better code generation for > > CPUs people use and we avoid some test failures in llvm 9.0 because i486 > > doesn't have 64-bot atomics. > > > > Comments? > > Full disclosure: I personally don't care about 32-bit architectures. > Feel free to ignore me based on that. ;-) > > I'm curious about the possibilities regarding 64-bit time_t on 32-bit > Intel systems. > Beyond the scope of this discussion. However, feel free to start a thread on this. It's quite difficult to switch if you want binary compat. It would affect system calls on the upgrade path and is among the hardest types to change if you have any kind of legacy to support... Warner Thanks, > > -- > Shawn Webb > Cofounder / Security Engineer > HardenedBSD > > Tor-ified Signal: +1 443-546-8752 > Tor+XMPP+OTR: lattera@is.a.hacker.sx > GPG Key ID: 0xFF2E67A277F8E1FA > GPG Key Fingerprint: D206 BB45 15E0 9C49 0CF9 3633 C85B 0AF8 AB23 0FB2 > From owner-freebsd-arch@freebsd.org Sat Oct 5 21:35:11 2019 Return-Path: Delivered-To: freebsd-arch@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 ECBAA13D576 for ; Sat, 5 Oct 2019 21:35:11 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from smtp-out-no.shaw.ca (smtp-out-no.shaw.ca [64.59.134.13]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "Client", Issuer "CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 46m0QQ5s4xz48bG for ; Sat, 5 Oct 2019 21:35:10 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from spqr.komquats.com ([70.67.125.17]) by shaw.ca with ESMTPA id Grhhi6DW0sAGkGrhiit5A0; Sat, 05 Oct 2019 15:35:08 -0600 X-Authority-Analysis: v=2.3 cv=WeVylHpX c=1 sm=1 tr=0 a=VFtTW3WuZNDh6VkGe7fA3g==:117 a=VFtTW3WuZNDh6VkGe7fA3g==:17 a=jpOVt7BSZ2e4Z31A5e1TngXxSK0=:19 a=XobE76Q3jBoA:10 a=7Qk2ozbKAAAA:8 a=ypVJL4-jAAAA:8 a=6I5d2MoRAAAA:8 a=YxBL1-UpAAAA:8 a=st1zzsJnYtNkjXh1kTcA:9 a=QEGh1riJdWpyoXNT:21 a=CytSffgvPVAsuE_M:21 a=QEXdDO2ut3YA:10 a=LazV5FRf0DQA:10 a=Or-HH45x8Z1dTZfaAicA:9 a=MjwXqzzD1TXnYA4o:21 a=ucoOmJ7csNkOScG1:21 a=iZLixMikwBFTzMH9:21 a=_W_S_7VecoQA:10 a=1lyxoWkJIXJV6VJUPhuM:22 a=khIbc0fXALFIcTpOSxgJ:22 a=IjZwj45LgO3ly-622nXo:22 a=Ia-lj3WSrqcvXOmTRaiG:22 Received: from [192.168.1.103] (S0106002401cb186f.gv.shawcable.net [70.67.125.17]) by spqr.komquats.com (Postfix) with ESMTPSA id A029C3D4; Sat, 5 Oct 2019 14:35:04 -0700 (PDT) Date: Sat, 05 Oct 2019 14:20:24 -0700 User-Agent: K-9 Mail for Android In-Reply-To: References: <20191005173411.l6gs3kszs7zcgfey@mutt-hbsd> MIME-Version: 1.0 Subject: Re: New CPUTYPE default for i386 port To: freebsd-arch@freebsd.org, Warner Losh , Shawn Webb From: Cy Schubert Message-ID: <06E29438-732D-4045-8FB3-5F2A082E9B98@cschubert.com> X-CMAE-Envelope: MS4wfIWM2wptK+aph+QNdDp7GZ4L7T/prFkNuiudHZUSo9N6NARmcVdCFsfx4gG/FQvqeREZPFRB+AP21evKa7TXFpDjLCV07kEBt1PN1J2Ts0e7Ym8NagFh hERkJE+B+DZX2U/LfGl6KfzILiPS7cia4GXROu7l3pECvqBPxW7SL2ZQ02HUmiKHWmFJUUBVArK2HG1X8H3INsWmFEaBZLyhrMVr08fadqXysptccYPzU3Yy PWPU8WTIPGv5Ngz3h1Vwtg== X-Rspamd-Queue-Id: 46m0QQ5s4xz48bG X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; dkim=none; spf=none (mx1.freebsd.org: domain of cy.schubert@cschubert.com has no SPF policy when checking 64.59.134.13) smtp.mailfrom=cy.schubert@cschubert.com X-Spamd-Result: default: False [-4.52 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; TO_DN_SOME(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; RCVD_TLS_LAST(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[13.134.59.64.list.dnswl.org : 127.0.5.0]; R_SPF_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; ASN(0.00)[asn:6327, ipnet:64.59.128.0/20, country:CA]; MID_RHS_MATCH_FROM(0.00)[]; IP_SCORE(-2.42)[ip: (-6.54), ipnet: 64.59.128.0/20(-3.07), asn: 6327(-2.39), country: CA(-0.09)]; RECEIVED_SPAMHAUS_PBL(0.00)[17.125.67.70.khpj7ygk5idzvmvt5x4ziurxhy.zen.dq.spamhaus.net : 127.0.0.11] Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Oct 2019 21:35:12 -0000 On October 5, 2019 11:19:41 AM PDT, Warner Losh wrote: >On Sat, Oct 5, 2019, 11:34 AM Shawn Webb >wrote: > >> On Sat, Oct 05, 2019 at 09:28:53AM -0600, Warner Losh wrote: >> > For a variety of reasons, the time has come to change the default >code >> > generation arch from i486 to i686 on our i386 port=2E No actual code >> removal >> > is planned as part of this effort=2E Only the default is doing >changed for >> > clang=2E >> > >> > The practical upshot of this for our i386 users will be zero for >almost >> > everybody=2E For the tiny sliver of people planning to deploy FreeBSD >on a >> > i486 or i586 core, a simple addition of CPUTYPE=3Dxxxx to >/etc/make=2Econf is >> > all that is needed for the src side of things=2E They will need to >setup >> > their own poudriere instance and create their own pkg repo to build >> > whatever packages are required for their deployment=2E >> > >> > It's my belief that even in the trailing edge long tail embedded >> deployment >> > segment of our user base this will cause no issues=2E All deployments >there >> > I'm aware of have moved of i486 class CPUs and the one 586 class >core >> > deployment I know of has no plans to update that to FreeBSD 11, let >alone >> > newer=2E >> > >> > There are a number of advantages to doing this which have been >> articulated >> > at length in other discussions=2E Briefly we get better code >generation for >> > CPUs people use and we avoid some test failures in llvm 9=2E0 because >i486 >> > doesn't have 64-bot atomics=2E >> > >> > Comments? >> >> Full disclosure: I personally don't care about 32-bit architectures=2E >> Feel free to ignore me based on that=2E ;-) >> >> I'm curious about the possibilities regarding 64-bit time_t on 32-bit >> Intel systems=2E >> > >Beyond the scope of this discussion=2E However, feel free to start a >thread >on this=2E It's quite difficult to switch if you want binary compat=2E It >would >affect system calls on the upgrade path and is among the hardest types >to >change if you have any kind of legacy to support=2E=2E=2E > >Warner > > >Thanks, >> >> -- >> Shawn Webb >> Cofounder / Security Engineer >> HardenedBSD >> >> Tor-ified Signal: +1 443-546-8752 >> Tor+XMPP+OTR: lattera@is=2Ea=2Ehacker=2Esx >> GPG Key ID: 0xFF2E67A277F8E1FA >> GPG Key Fingerprint: D206 BB45 15E0 9C49 0CF9 3633 C85B 0AF8 AB23 >0FB2 >> >_______________________________________________ >freebsd-arch@freebsd=2Eorg mailing list >https://lists=2Efreebsd=2Eorg/mailman/listinfo/freebsd-arch >To unsubscribe, send any mail to "freebsd-arch-unsubscribe@freebsd=2Eorg" This is one of the two reasons I believe we should deprecate 32-bit=2E Eve= n supporting 32-bit compatibility long term is unsustainable=2E It is not w= orth the effort=2E Putting a stake in the ground to say we no longer support 32-bit after 203= 8 would be desirable=2E (Sooner the better though=2E) --=20 Pardon the typos and autocorrect, small keyboard in use=2E=20 Cy Schubert FreeBSD UNIX: Web: https://www=2EFreeBSD=2Eorg The need of the many outweighs the greed of the few=2E Sent from my Android device with K-9 Mail=2E Please excuse my brevity=2E From owner-freebsd-arch@freebsd.org Sat Oct 5 22:50:38 2019 Return-Path: Delivered-To: freebsd-arch@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 B51D113E9A0 for ; Sat, 5 Oct 2019 22:50:38 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound3d.ore.mailhop.org (outbound3d.ore.mailhop.org [54.186.57.195]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 46m25V0xMgz4DDn for ; Sat, 5 Oct 2019 22:50:37 +0000 (UTC) (envelope-from ian@freebsd.org) ARC-Seal: i=1; a=rsa-sha256; t=1570315836; cv=none; d=outbound.mailhop.org; s=arc-outbound20181012; b=L6fkPqz3COyWs6y0Ha1DLAiJqiP48+thEbPWukrWH1dLgtxOI9xRDY4eMTsGi6nPOlObd5MBYqk5M gEg5tD+YiSQWpplrmonxsbOqtMqaNyM26BwS0U/olpZqudxBHkUAc07f9kBeL4l+dA1BoxX6B6kQXv gi2Y9FX3A5dbG1opurXLnBUhDkJc5upjNMbL98BH9c1oCtYAIBwhLpsjECV/yYNZvgqUe1DgfuWJ77 nRG1Zt9acPBDQyzW6mNQQkNuSe6g/E/kCERcm3yxFBjDfzY3h2x+GDAPIXcnKcNsLInrmriTzfNZxy 2vrXjf28IVfHYU/jmfHD/QaEnpR+MaQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=arc-outbound20181012; h=content-transfer-encoding:mime-version:content-type:references:in-reply-to: date:to:from:subject:message-id:dkim-signature:from; bh=9XtkUVKsPlMwl+oOmEOHQSRn02jPyXs7RhEDFwPnPF8=; b=BOMWbChfJAa1EIrCE6zvI1ag5bnjKFi32Irrf9IPWnswSNj7ULKuhuMeGvHWCSz9je0NTPqh46SnD fF/ZIu4+Q5Eb+Zgnp0cWX1xaVryuqO+/IVTGSO0YmXWV7GyjTsMKsebzVVqGWbXHcvaREg55dbyqlf E9phUSAfXOV9EYwsISrqHrc2Th+CRybcJ8bRXLpvtQzJ5bnJJNNRnr2TuVta8atSF6ZRqWMMi/ZXJu ExbqNxAz21/C60lr8Ifb30EgYDEDl32O4n5QAeIDLFNeWGSManQrWRdmtg1sIuWwwRMKPMebDa0/R5 KeSwUjxgPIer2YFoRKdnZgMmYK2zhdA== ARC-Authentication-Results: i=1; outbound3.ore.mailhop.org; spf=softfail smtp.mailfrom=freebsd.org smtp.remote-ip=67.177.211.60; dmarc=none header.from=freebsd.org; arc=none header.oldest-pass=0; DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=dkim-high; h=content-transfer-encoding:mime-version:content-type:references:in-reply-to: date:to:from:subject:message-id:from; bh=9XtkUVKsPlMwl+oOmEOHQSRn02jPyXs7RhEDFwPnPF8=; b=FdZZlZvclcrExB4f7V3yYN8N+Rqy74UzlX6SAx7/3KGlfIRbAyFfqddiI929PxHsBLMVdxlEAJcra DN+XL/8jaslKWLbwy/IaCMRR7vYAC8jFgT9+iuif+zKAVu1lpD261GKQ0gAKtu5ySfTggFpJNmE8Pj ZQbmwuOMkTSbge4kA97yJqP2rNThnhXE078c3Eb+Xw8XFJ0VlfjayBnS3x97zakuijJagvrvfRQ4mo 5L6Vy1n7PQ15D2oELiSKY5aGvSzu9grMGRjoSN1QBC5bpY7f+k1BJi2VucGqhPoJjwQQinwXTQLRjS JNN9U9X9UzHsINK5NnsBZQ6E9XpsytQ== X-MHO-RoutePath: aGlwcGll X-MHO-User: 8953bd45-e7c2-11e9-955f-dfabc1efb494 X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 67.177.211.60 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [67.177.211.60]) by outbound3.ore.mailhop.org (Halon) with ESMTPSA id 8953bd45-e7c2-11e9-955f-dfabc1efb494; Sat, 05 Oct 2019 22:50:34 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id x95MoWM5072982; Sat, 5 Oct 2019 16:50:32 -0600 (MDT) (envelope-from ian@freebsd.org) Message-ID: <20f9896361c341736c5154c010cedf3fdcffc235.camel@freebsd.org> Subject: Re: New CPUTYPE default for i386 port From: Ian Lepore To: Cy Schubert , freebsd-arch@freebsd.org, Warner Losh , Shawn Webb Date: Sat, 05 Oct 2019 16:50:32 -0600 In-Reply-To: <06E29438-732D-4045-8FB3-5F2A082E9B98@cschubert.com> References: <20191005173411.l6gs3kszs7zcgfey@mutt-hbsd> <06E29438-732D-4045-8FB3-5F2A082E9B98@cschubert.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.28.5 FreeBSD GNOME Team Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 46m25V0xMgz4DDn X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-1.97 / 15.00]; local_wl_from(0.00)[freebsd.org]; NEURAL_HAM_MEDIUM(-0.97)[-0.966,0]; ASN(0.00)[asn:16509, ipnet:54.186.0.0/15, country:US]; NEURAL_HAM_LONG(-1.00)[-1.000,0] X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Oct 2019 22:50:38 -0000 On Sat, 2019-10-05 at 14:20 -0700, Cy Schubert wrote: > On October 5, 2019 11:19:41 AM PDT, Warner Losh > wrote: > > On Sat, Oct 5, 2019, 11:34 AM Shawn Webb < > > shawn.webb@hardenedbsd.org> > > wrote: > > > > > On Sat, Oct 05, 2019 at 09:28:53AM -0600, Warner Losh wrote: > > > > [...] > > > I'm curious about the possibilities regarding 64-bit time_t on > > > 32-bit > > > Intel systems. > > > > > > > Beyond the scope of this discussion. However, feel free to start a > > thread on this. It's quite difficult to switch if you want binary > > compat. It would affect system calls on the upgrade path and is > > among the hardest types to change if you have any kind of legacy to > > support... > > > > Warner > > > > > > This is one of the two reasons I believe we should deprecate 32-bit. > Even supporting 32-bit compatibility long term is unsustainable. It > is not worth the effort. > > Putting a stake in the ground to say we no longer support 32-bit > after 2038 would be desirable. (Sooner the better though.) > > Only i386 has a 32-bit time_t. Other 32-bit arches either began life with 64-bit time_t or have been switched to it. For i386, if its current users (and I am one, for $work) have a choice between "As of date X there will be no more i386" and "As of date X we switch time_t to 64 bits and you will not be able to run old binaries after that" I suspect people would choose the latter. -- Ian