From owner-freebsd-stable@freebsd.org Tue Apr 23 22:04:52 2019 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8A372158400E for ; Tue, 23 Apr 2019 22:04:52 +0000 (UTC) (envelope-from bob@rancor.immure.com) Received: from rancor.immure.com (108-84-10-9.lightspeed.austtx.sbcglobal.net [108.84.10.9]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "darth.immure.com", Issuer "darth.immure.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 7A9F58D434 for ; Tue, 23 Apr 2019 22:04:41 +0000 (UTC) (envelope-from bob@rancor.immure.com) Received: from rancor.immure.com (localhost [127.0.0.1]) by rancor.immure.com (8.15.2/8.15.2) with ESMTPS id x3NM4XuD037547 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 23 Apr 2019 17:04:33 -0500 (CDT) (envelope-from bob@rancor.immure.com) Received: (from bob@localhost) by rancor.immure.com (8.15.2/8.15.2/Submit) id x3NM4XPH037546; Tue, 23 Apr 2019 17:04:33 -0500 (CDT) (envelope-from bob) Date: Tue, 23 Apr 2019 17:04:33 -0500 From: Bob Willcox To: Lorenzo Salvadore Cc: "freebsd-stable@freebsd.org" Subject: Re: 12.0 installworld core dumping on me Message-ID: <20190423220433.GM6607@rancor.immure.com> Reply-To: Bob Willcox References: <20190423125133.GG3392@rancor.immure.com> <20190423183604.GL6607@rancor.immure.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) X-Rspamd-Queue-Id: 7A9F58D434 X-Spamd-Bar: +++++++ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [7.97 / 15.00]; TO_DN_EQ_ADDR_SOME(0.00)[]; HAS_REPLYTO(0.00)[bob@immure.com]; MX_INVALID(0.50)[greylisted]; TO_DN_SOME(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; RCPT_COUNT_TWO(0.00)[2]; FORGED_SENDER(0.30)[bob@immure.com,bob@rancor.immure.com]; RCVD_TLS_LAST(0.00)[]; R_DKIM_NA(0.00)[]; ASN(0.00)[asn:7018, ipnet:108.64.0.0/11, country:US]; MIME_TRACE(0.00)[0:+]; FROM_NEQ_ENVFROM(0.00)[bob@immure.com,bob@rancor.immure.com]; ARC_NA(0.00)[]; REPLYTO_EQ_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; NEURAL_SPAM_SHORT(0.61)[0.611,0]; MIME_GOOD(-0.10)[text/plain]; IP_SCORE(0.16)[ip: (0.49), ipnet: 108.64.0.0/11(0.24), asn: 7018(0.12), country: US(-0.06)]; DMARC_NA(0.00)[immure.com]; AUTH_NA(1.00)[]; NEURAL_SPAM_MEDIUM(1.00)[0.998,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MX_MISSING(3.50)[requested record is not found]; NEURAL_SPAM_LONG(1.00)[1.000,0]; R_SPF_NA(0.00)[]; GREYLIST(0.00)[pass,meta] X-Spam: Yes X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Apr 2019 22:04:52 -0000 On Tue, Apr 23, 2019 at 08:43:34PM +0000, Lorenzo Salvadore via freebsd-stable wrote: > ????????????????????? Original Message ????????????????????? > On Tuesday 23 April 2019 20:36, Bob Willcox wrote: > ... > > I am playing too with CPUTYPE in these days. I think I will soon write a wiki page > about that. Here is a short description of what I have found out. > > What I suggest you to do, if you still want to play with CPU_TYPE (I do not recommend it: > I cannot see any real improvement), is to set CPUTYPE?= native. Then look into > /usr/share/mk/bsd.cpu.mk what feature you can enable or disable for your processor: > avx, sse3 etc. Compare this list with the feature supported by your processor (run > "dmesg | head -n 25" to get them) and define MACHINE_CPU+= with what you need > (some features probably are already set: check them with "make -V MACHINE_CPU"). > > Reading /usr/share/mk/bsd.cpu.mk you will see some values you can give to CPUTYPE > that will set automatically MACHINE_CPU to the right value. However I discourage you > from using them: in my case, I should set CPU_TYPE?=ivybridge, however bsd.cpu.mk, > clang and gcc all believe that ivybridge support avx, but this is wrong at least for my > cpu, thus I get invalid instructions (even if I correct bsd.cpu.mk), while everything is > fine by setting CPU_TYPE?=native. > If, however, you still want to set your specific model instead of native into CPU_TYPE, > you can get the supposed right value running > "cc -v -x c -E -march=native /dev/null -o /dev/null" or "llvm-tblgen -version". > > If you happen to encounter some invalid instructions with some port, recompile it > with NO_CPU_CFLAGS=yes: this will avoid setting -march= in > your CFLAGS. > I had to do that with ports involving rust. > > Lorenzo Salvadore. Thanks for the info/insight Lorenzo. I think I will simply skip setting it from now on though. I burned/wasted way more time on this than I care to think about already. It sounds like (based on what you have said) there really isn't a big reward for using it anyway. Thanks again, Bob -- Bob Willcox | "Too often we enjoy the comfort of opinion bob@immure.com | without the discomfort of thought." Austin, TX | - John F. Kennedy