From: Ralf Baechle <ralf@linux-mips.org>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: Sam Ravnborg <sam@ravnborg.org>,
Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org,
linux-mips@linux-mips.org
Subject: Re: [IDE] Fix build bug
Date: Thu, 25 Oct 2007 17:05:29 +0100 [thread overview]
Message-ID: <20071025160529.GB24621@linux-mips.org> (raw)
In-Reply-To: <Pine.LNX.4.64N.0710251545300.24086@blysk.ds.pg.gda.pl>
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
next prev parent reply other threads:[~2007-10-25 16:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-25 13:53 [IDE] Fix build bug Ralf Baechle
2007-10-25 14:13 ` Sam Ravnborg
2007-10-25 14:13 ` Ralf Baechle
2007-10-25 14:47 ` Maciej W. Rozycki
2007-10-25 16:05 ` Ralf Baechle [this message]
2007-10-25 17:12 ` Maciej W. Rozycki
2007-10-25 21:52 ` Bartlomiej Zolnierkiewicz
2007-10-25 21:41 ` Bartlomiej Zolnierkiewicz
2007-10-30 11:34 ` Denys Vlasenko
2007-10-30 12:41 ` Ralf Baechle
2007-10-30 20:30 ` Bartlomiej Zolnierkiewicz
2007-11-01 18:43 ` Denys Vlasenko
2007-11-02 12:34 ` Ralf Baechle
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20071025160529.GB24621@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=akpm@linux-foundation.org \
--cc=bzolnier@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=macro@linux-mips.org \
--cc=sam@ravnborg.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.