This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Linux and aliasing?
- To: davem at redhat dot com (David S. Miller)
- Subject: Re: Linux and aliasing?
- From: Joern Rennecke <amylaar at cygnus dot co dot uk>
- Date: Mon, 7 Jun 1999 14:01:08 +0100 (BST)
- Cc: mark at codesourcery dot com, ak at muc dot de, toon at moene dot indiv dot nluug dot nl, law at cygnus dot com, jbuck at Synopsys dot COM, torvalds at transmeta dot com, craig at jcb-sc dot com, chip at perlsupport dot com, egcs at egcs dot cygnus dot com
> Also some of the datastructures one would need to change are included
> by userspace applications, especially for some of the networking
> instances, and thus one would have ABI issues to concern themselves
> about if they were to go and perform these transformations. Much more
> is it than a tedious chore. One could certainly create another header
> file, leave the old one alone with the same name, and use only the new
> one inside the kernel, but does it make sense to have two copies and
> maintain them?
No. You could still have a single header file, and control the variant
portions with #ifdef __KERNEL__ / #else / #endif .
Or if you have some recurring common type mix, you could use some macros
in the declarations that are definied differently for kernel and user space.