[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20071025160529.GB24621@linux-mips.org>
Date: Thu, 25 Oct 2007 17:05:29 +0100
From: Ralf Baechle <ralf@...ux-mips.org>
To: "Maciej W. Rozycki" <macro@...ux-mips.org>
Cc: Sam Ravnborg <sam@...nborg.org>,
Bartlomiej Zolnierkiewicz <bzolnier@...il.com>,
Andrew Morton <akpm@...ux-foundation.org>,
linux-kernel@...r.kernel.org, linux-ide@...r.kernel.org,
linux-mips@...ux-mips.org
Subject: Re: [IDE] Fix build bug
On Thu, Oct 25, 2007 at 03:47:16PM +0100, Maciej W. Rozycki wrote:
> > So we can avoid this if we invent a __constinitdata tag that uses
> > a new section?
>
> That would do.
>
> > I ask mainly to understand this error - not that I am that found
> > of the idea.
>
> 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.
Ralf
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists