On Thu, 25 Oct 2007, Ralf Baechle wrote:
> > Somebody wants to mix up read-only and read/write data in the same
> > section and GCC quite legitimately complains about it. You cannot have
> > both at a time.
>
> My interpretation is that it would be perfectly ok for a C compiler to
> do minimal handling of const by only throwing errors for attempted
> assignments to const objects but otherwise treating them as if they
> were non-const, that is for example putting them into an r/w section.
That would probably be valid (any C standard expert please correct me if
I am wrong), but the approach looks like: since we have the capability in
the hardware and the OS, then why not actually enforce the rule at the run
time as well?
Maciej
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
