Date: Sat, 07 Dec 1996 08:36:46 -0800 From: Paul Traina <pst@shockwave.com> To: Peter Wemm <peter@spinner.dialix.com> Cc: dyson@freebsd.org, bde@zeta.org.au (Bruce Evans), cvs-all@freefall.freebsd.org, CVS-committers@freefall.freebsd.org, cvs-sys@freefall.freebsd.org, dyson@freefall.freebsd.org Subject: Re: cvs commit: src/sys/i386/include endian.h Message-ID: <199612071636.IAA13365@precipice.shockwave.com> In-Reply-To: Your message of "Sat, 07 Dec 1996 13:11:47 %2B0800." <199612070511.NAA27272@spinner.DIALix.COM>
next in thread | previous in thread | raw e-mail | index | archive | help
From: Peter Wemm <peter@spinner.dialix.com> Subject: Re: cvs commit: src/sys/i386/include endian.h "John S. Dyson" wrote: > > > > Most of the kernel doesn't pick up the CPU options. > > > Why not? That seems to be unwise, shouldn't anything with any > cpu specific inlines also pick-up the CPU options? Anything > that uses endian.h (or cpufunc.h) are perfect examples of where > there might be some value in that. > > John Perhaps we should seriously consider using 'cc -include opt_global.h' and moving things like Ix86_CPU etc into there? It has the benefits of having every file know about the settings, but without having to modify every file. We would have to tweak the .depend generation in the Makefile though, since cc -M doesn't seem to list files from -include. It should be a simple case of a simple sed script. Dependencies could still work. Yeah, and then you have to remake the entire universe? I don't think so. :-( I'd rather split out the CPU specific parts of endian.h. In fact, isn't there a pretty simple test that can be done with #if's to determine endian?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199612071636.IAA13365>