From: Ivan Kokshaysky <ink@jurassic.park.msu.ru>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: dl8bcu@dl8bcu.de, rth@twiddle.net, linux-scsi@vger.kernel.org,
linux-alpha@vger.kernel.org
Subject: Re: Build error: `.exit.text' referenced in section `.rodata'
Date: Wed, 14 May 2008 00:06:50 +0400 [thread overview]
Message-ID: <20080513200649.GA23202@jurassic.park.msu.ru> (raw)
In-Reply-To: <1210690758.3077.23.camel@localhost.localdomain>
On Tue, May 13, 2008 at 09:59:17AM -0500, James Bottomley wrote:
> But if that's true then the whole basis for our section based discards
> is bogus, because the statement generating the jump table could be
> inside the actual function body instead of being inlined, so if it's
> failing on x86 as well, we likely need it fixed there too.
Correct.
> > It would be good, but in the meantime the 'noinline' fix seems to be
> > a most sensible option...
>
> We can certainly add it as a short term option. However, given the push
> in certain quarters to make even more use of sections as a means of
> discarding code, we're going to have to ask someone to fix the compiler.
Then maybe building with -fno-jump-tables option would be better solution.
I don't think that it will have a noticeable impact on code size or
performance, especially on x86.
So we need something like this (assuming gcc eventually gets fixed,
say gcc 4.5 ;)
KBUILD_CFLAGS += $(call cc-ifversion, -lt, 0405, \
$(call cc-option, -fno-jump-tables))
Ivan.
next prev parent reply other threads:[~2008-05-13 20:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-11 15:19 Build error: `.exit.text' referenced in section `.rodata' Thorsten Kranzkowski
2008-05-11 16:55 ` James Bottomley
2008-05-11 19:20 ` Thorsten Kranzkowski
2008-05-12 11:52 ` Thorsten Kranzkowski
2008-05-12 14:01 ` James Bottomley
2008-05-13 14:31 ` Ivan Kokshaysky
2008-05-13 14:59 ` James Bottomley
2008-05-13 20:06 ` Ivan Kokshaysky [this message]
2008-05-13 20:51 ` James Bottomley
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=20080513200649.GA23202@jurassic.park.msu.ru \
--to=ink@jurassic.park.msu.ru \
--cc=James.Bottomley@HansenPartnership.com \
--cc=dl8bcu@dl8bcu.de \
--cc=linux-alpha@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=rth@twiddle.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).