Date: Thu, 31 Jul 2003 00:15:37 +0300 From: Ruslan Ermilov <ru@FreeBSD.org> To: John Baldwin <jhb@FreeBSD.org> Cc: cvs-all@FreeBSD.org Subject: Re: cvs commit: src/release Makefile Message-ID: <20030730211537.GH33188@sunbay.com> In-Reply-To: <XFMail.20030730164835.jhb@FreeBSD.org> References: <3F2820F3.6020501@freebsd.org> <XFMail.20030730164835.jhb@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] On Wed, Jul 30, 2003 at 04:48:35PM -0400, John Baldwin wrote: > > On 30-Jul-2003 Scott Long wrote: > > John Baldwin wrote: > >> On 30-Jul-2003 Ruslan Ermilov wrote: > >> > >>>ru 2003/07/30 07:46:46 PDT > >>> > >>> FreeBSD src repository > >>> > >>> Modified files: > >>> release Makefile > >>> Log: > >>> The -Os kernel build with GCC 3.3.1 also requires -fno-strict-aliasing > >>> to survive. > >>> > >>> Discussed with: bde > >>> Tested on: i386 and pc98 > >> > >> > >> I thought Peter just committed a fix for this to the kernel. > >> > > > > Peter's fix to pcpu.h only fixed one symptom. The warning is generated > > in many other places too, and I think that Ruslan was trying to fix it > > at a top level rather than obfuscate a lot of kernel code to keep gcc > > quiet. My complaint is that -fno-strict-aliasing should be set in > > /sys/conf and not be a special case for just thre release scripts. > > Agreed. > My point was to re-enable snapshot building. Once this is in /sys/conf/*.mk, it can be removed from here. IMO, this is not an issue. Cheers, -- Ruslan Ermilov Sysadmin and DBA, ru@sunbay.com Sunbay Software Ltd, ru@FreeBSD.org FreeBSD committer [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE/KDV4Ukv4P6juNwoRAqQ0AJsFRWqs6MrfFS0TuTryzI4la1hh9QCcD5fq UjeWw9me822xd2Ewl3kkaB8= =P519 -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030730211537.GH33188>