From: Franck Bui-Huu <vagabon.xyz@gmail.com>
To: Daniel Jacobowitz <dan@debian.org>
Cc: linux-mips@linux-mips.org
Subject: Re: [PATCH 1/3] Remove '-mno-explicit-relocs' option when CONFIG_BUILD_ELF64
Date: Thu, 09 Aug 2007 21:39:24 +0200 [thread overview]
Message-ID: <46BB6D6C.2050601@gmail.com> (raw)
In-Reply-To: <20070809151812.GA28142@caradoc.them.org>
Daniel Jacobowitz wrote:
> On Thu, Feb 15, 2007 at 02:04:18PM +0100, Franck Bui-Huu wrote:
>> From: Franck Bui-Huu <fbuihuu@gmail.com>
>>
>> This patch removes '-mno-explicit-relocs' usage when
>> CONFIG_BUILD_ELF64 is set since this option was only required
>> with the old hack to truncate addresses at the assembly level
>> where "-mabi=64 -Wa,-mabi=32" was used.
>>
>> This should yield a small code size improvement for inline
>> assembly, where the R constraint is used.
>>
>> The idea is coming from Maciej <macro@linux-mips.org>.
>
> It looks like nothing ever came of these patches?
yes it seems a common rule which is applied to the patches I send to
this mailing list ;)
> I tried to boot my
> Sentosa again today, and needed a slightly updated version of them.
>
What do you mean by "slightly updated version" ? Did you rebase them
on top the current linux-mips tree, or something ? If not, what's your
kernel version ?
> I'm not positive I did the update correctly, though, since the board
> panics in swapper after jumping to a bogus pointer.
>
Sorry I don't understand this. Do you mean:
a) My kernel crashed, so I gave your patchset a try but it's still
crahshing
b) My kernel crashed, so I gave your patchset a try and it makes my
kernel running fine.
I assume you're saying a).
Can you give a try to 2.6.23-rc2 because it includes commit
b1c65b3988c6e29ac371ab1cbbf6c4f8fb7092f8 which might fix your
issue. That would be a side effect but it gives us a hint on your
problem.
Also your .config, dmesg files are welcome.
Franck
next prev parent reply other threads:[~2007-08-09 19:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-15 13:04 [PATCH 1/3] Remove '-mno-explicit-relocs' option when CONFIG_BUILD_ELF64 Franck Bui-Huu
2007-02-15 13:04 ` [PATCH 2/3] Automatically set CONFIG_BUILD_ELF64 Franck Bui-Huu
2007-02-15 13:04 ` [PATCH 3/3] Rename CONFIG_BUILD_ELF64 into KBUILD_64BIT_SYM32 Franck Bui-Huu
2007-02-15 13:14 ` Franck Bui-Huu
2007-02-15 13:21 ` Franck Bui-Huu
2007-08-09 15:18 ` [PATCH 1/3] Remove '-mno-explicit-relocs' option when CONFIG_BUILD_ELF64 Daniel Jacobowitz
2007-08-09 19:39 ` Franck Bui-Huu [this message]
2007-08-13 19:30 ` Daniel Jacobowitz
2007-08-14 16:22 ` Franck Bui-Huu
-- strict thread matches above, loose matches on Subject: below --
2007-02-13 9:18 [RFC] Kill CONFIG_BUILD_ELF64 from Kconfig Franck Bui-Huu
2007-02-13 9:18 ` [PATCH 1/3] Remove '-mno-explicit-relocs' option when CONFIG_BUILD_ELF64 Franck Bui-Huu
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=46BB6D6C.2050601@gmail.com \
--to=vagabon.xyz@gmail.com \
--cc=dan@debian.org \
--cc=linux-mips@linux-mips.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox