Re: toolchain/60317: build.sh distribution sets fails with -pipe -O2 in CPUFLAGS

["Valery Ushakov via gnats" <gnats-admin%NetBSD.org@localhost>]

The following reply was made to PR toolchain/60317; it has been noted by GNATS.

From: Valery Ushakov <uwe%stderr.spb.ru@localhost>
To: gnats-bugs%netbsd.org@localhost
Cc: 
Subject: Re: toolchain/60317: build.sh distribution sets fails with -pipe -O2
 in CPUFLAGS
Date: Tue, 9 Jun 2026 11:52:26 +0300

 On a tangent...  Adding flags like -pipe and/or -O2 to CPUFLAGS is a
 bad idea.  It's already a bit messy with the way COPTS is treated
 differently by the kernel and by the userland build machinery.  I'm
 pretty sure _some_ botloader builds massage build flags and you might
 get strange results when these two find each other.
 
 As far as I can tell the best way to express what you want is to set
 
   # should be COPTS in an ideal world, but that breaks the kernel makefile
   DBG = -pipe -O2
 
 and only set cpu-related flags in CPUFLAGS (that is passed e.g. to
 as(1) invocations)
 
   CPUFLAGS = -mtune=native -march=native
 
 -uwe