From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Ivan Kokshaysky <ink@jurassic.park.msu.ru>
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: Tue, 13 May 2008 15:51:14 -0500 [thread overview]
Message-ID: <1210711874.3077.67.camel@localhost.localdomain> (raw)
In-Reply-To: <20080513200649.GA23202@jurassic.park.msu.ru>
On Wed, 2008-05-14 at 00:06 +0400, Ivan Kokshaysky wrote:
> 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))
This is way beyond a SCSI issue. Time to take it to linux-arch I
think ... do you want to do the honours?
James
prev parent reply other threads:[~2008-05-13 20:51 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
2008-05-13 20:51 ` James Bottomley [this message]
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=1210711874.3077.67.camel@localhost.localdomain \
--to=james.bottomley@hansenpartnership.com \
--cc=dl8bcu@dl8bcu.de \
--cc=ink@jurassic.park.msu.ru \
--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 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.