From owner-freebsd-arch@freebsd.org Thu Oct 24 14:07: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 7755E16DE6C for ; Thu, 24 Oct 2019 14:07:19 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: from mail-io1-f51.google.com (mail-io1-f51.google.com [209.85.166.51]) (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 46zTZt4m6sz3JY1; Thu, 24 Oct 2019 14:07:18 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: by mail-io1-f51.google.com with SMTP id h9so1830462ioh.2; Thu, 24 Oct 2019 07:07:18 -0700 (PDT) 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=CcHAQFyquYZIihuu6Ogswkg+Sz5vo9sGKxp0mygnRgk=; b=i1l9wJhOM75qvFGuP5EgS63r+ntbhtvWjMOetSVFVU9lUz2bq4GdDuLTbMgkCF9v24 OOYa3xynZ+/zUCMG9Ra8LPq+7dP+e0rzHduSJgKoSDO0nl3pdQ1nIG+S5lWP0axWU8Xl kMe/Str3Z2qFh9uncPyGmh6bWnjRJXW8nRYtS8cdVRSalYQv4SwM1vXCkGzW22zfWjpR ZsBCGeOhPMo+/UsW5xAsgz41gxkkUM1Zu53fkpu4PIjOVrljOB7SF6tjg99jszycn7Ex WXw6DZ6/JEiPsuGXuainEnWjNULXU1bL8JlqBkb75UX+wDRp4yCoB4gDWijKRCfYNeHB tYAg== X-Gm-Message-State: APjAAAWtvK+bqWTn0Lt7RAw0suSozy4m/i+9Qr9ief7BmSTsnZXYvIaK odt+LfEkIHbuLqeON/VMPT7dkROh821jPUwibZl4HA0z X-Google-Smtp-Source: APXvYqwcW4nW+EOCcg+E9KGns8yavaU4N/BTKEnSzImWry6TeyV/TGDjCclOmN3TaP4RRicFpfcq/zXWuItzhJc8K4I= X-Received: by 2002:a6b:6418:: with SMTP id t24mr9089804iog.185.1571926036887; Thu, 24 Oct 2019 07:07:16 -0700 (PDT) MIME-Version: 1.0 References: <201910060322.x963Mwo1065732@gndrsh.dnsmgr.net> <89501a69-ea37-7016-5ccb-286ff65b2e2a@FreeBSD.org> <18250.1570457337@critter.freebsd.dk> In-Reply-To: From: Ed Maste Date: Thu, 24 Oct 2019 08:33:57 -0400 Message-ID: Subject: Re: New CPUTYPE default for i386 port To: Julian Elischer Cc: Warner Losh , Poul-Henning Kamp , "Rodney W. Grimes" , Lev Serebryakov , "freebsd-arch@freebsd.org" Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 46zTZt4m6sz3JY1 X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of carpeddiem@gmail.com designates 209.85.166.51 as permitted sender) smtp.mailfrom=carpeddiem@gmail.com X-Spamd-Result: default: False [-4.34 / 15.00]; ARC_NA(0.00)[]; TO_DN_EQ_ADDR_SOME(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17:c]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; MIME_TRACE(0.00)[0:+]; DMARC_NA(0.00)[freebsd.org]; RCPT_COUNT_FIVE(0.00)[6]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[51.166.85.209.list.dnswl.org : 127.0.5.0]; IP_SCORE(-2.34)[ip: (-6.35), ipnet: 209.85.128.0/17(-3.23), asn: 15169(-2.06), country: US(-0.05)]; FORGED_SENDER(0.30)[emaste@freebsd.org,carpeddiem@gmail.com]; RWL_MAILSPIKE_POSSIBLE(0.00)[51.166.85.209.rep.mailspike.net : 127.0.0.17]; 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)[emaste@freebsd.org,carpeddiem@gmail.com]; RCVD_TLS_ALL(0.00)[]; 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: Thu, 24 Oct 2019 14:07:19 -0000 On Mon, 7 Oct 2019 at 14:10, Julian Elischer wrote: > > SO we'd be "demoting" [i586 and below] to the same situation as the ARM64 port > > where one has to build it yourself. This is not the case, we produce arm64 install images and have for quite some time - since FreeBSD 11.0, there's no need to build it yourself. We don't yet have FreeBSD-update builds for arm64 but that will be addressed one way or another. If folks do want to ensure i586 continues to work (and i486 continues to sort-of work) in FreeBSD 13 we need to make sure that there's CI coverage for these. I'm happy to host physical devices in the hardware CI lab for this purpose if we want to test on real hardware, but perhaps QEMU is sufficient.