From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Anders Blomdell <anders.blomdell@domain.hid>
Cc: "xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: Re: [Xenomai-core] Problem with gcc-4.5.1
Date: Tue, 07 Dec 2010 13:09:02 +0100 [thread overview]
Message-ID: <4CFE23DE.8050906@domain.hid> (raw)
In-Reply-To: <4CFE217A.1010609@domain.hid>
Anders Blomdell wrote:
> On 12/07/2010 12:51 PM, Gilles Chanteperdrix wrote:
>> Anders Blomdell wrote:
>>> When compiling Xenomai on Fedora-14 with gcc-4.5.1 [version 4.5.1
>>> 20100924 (Red Hat 4.5.1-4)], the loading of xeno_nucleus fails with the
>>> attached kernel OOPS, a notable difference between the 4.5.1 compiled
>>> version and a working one built with gcc-4.4.4 on the same system with
>>> the same configuration, sis tthat __rthal_x86_nodiv_ullimd is not
>>> inlined, is this anybody has seen before?
>> No, that is new, we need to see the disassembly of __rthal_x86_nodiv_ullimd
>
> objdump -S:
>
> static inline __attribute__((const)) unsigned long long
> __rthal_x86_nodiv_ullimd(const unsigned long long op,
> const unsigned long long frac,
> unsigned integ)
> {
> e7a8: 55 push %ebp
> e7a9: 89 e5 mov %esp,%ebp
> e7ab: 57 push %edi
> e7ac: 56 push %esi
> e7ad: 53 push %ebx
> e7ae: 83 ec 10 sub $0x10,%esp
> e7b1: 8d 7d 08 lea 0x8(%ebp),%edi
> e7b4: e8 fc ff ff ff call e7b5 <__rthal_x86_nodiv_ullimd+0xd>
> e7b9: 8b 1f mov (%edi),%ebx
> e7bb: 8b 4f 04 mov 0x4(%edi),%ecx
> register unsigned rm __asm__("esi");
> register unsigned rh __asm__("edi");
> unsigned fracl, frach, opl, oph;
> register unsigned long long t;
>
> __rthal_u64tou32(op, oph, opl);
> e7be: 89 45 e8 mov %eax,-0x18(%ebp)
> __rthal_u64tou32(frac, frach, fracl);
> e7c1: 89 5d f0 mov %ebx,-0x10(%ebp)
> register unsigned rm __asm__("esi");
> register unsigned rh __asm__("edi");
> unsigned fracl, frach, opl, oph;
> register unsigned long long t;
>
> __rthal_u64tou32(op, oph, opl);
> e7c4: 89 55 e4 mov %edx,-0x1c(%ebp)
> __rthal_u64tou32(frac, frach, fracl);
> e7c7: 89 4d ec mov %ecx,-0x14(%ebp)
>
> __asm__ ("mov %[oph], %%eax\n\t"
> e7ca: 8b 45 e4 mov -0x1c(%ebp),%eax
> e7cd: f7 65 ec mull -0x14(%ebp)
> e7d0: 89 c6 mov %eax,%esi
> e7d2: 89 d7 mov %edx,%edi
> e7d4: 8b 45 e8 mov -0x18(%ebp),%eax
> e7d7: f7 65 f0 mull -0x10(%ebp)
> e7da: 89 d1 mov %edx,%ecx
> e7dc: d1 e0 shl %eax
> e7de: 83 d1 00 adc $0x0,%ecx
> e7e1: 83 d6 00 adc $0x0,%esi
> e7e4: 83 d7 00 adc $0x0,%edi
> e7e7: 8b 45 e4 mov -0x1c(%ebp),%eax
> e7ea: f7 65 f0 mull -0x10(%ebp)
> e7ed: 01 c1 add %eax,%ecx
> e7ef: 11 d6 adc %edx,%esi
> e7f1: 83 d7 00 adc $0x0,%edi
> e7f4: 8b 45 e8 mov -0x18(%ebp),%eax
> e7f7: f7 65 ec mull -0x14(%ebp)
> e7fa: 01 c1 add %eax,%ecx
> e7fc: 11 d6 adc %edx,%esi
> e7fe: 83 d7 00 adc $0x0,%edi
> e801: 8b 45 e8 mov -0x18(%ebp),%eax
> e804: f7 67 08 mull 0x8(%edi)
Problem is here: edi is used by gcc as if it contained an address
whereas it is used by the assembly for the computation. Should be marked
"early clobber". So,
in include/asm-x86/arith_32.h, replace:
: [rl]"=c"(rl), [rm]"=S"(rm), [rh]"=D"(rh), "=A"(t)
with:
: [rl]"=&c"(rl), [rm]"=&S"(rm), [rh]"=&D"(rh), "=&A"(t)
> But us I said, in the working version, the code seems to be inlined
> everywhere. Should I send the two object modules as well (probably as a
> private message?).
The code should work the same whatever gcc decides regarding inlining.
Whether we like gcc decision is a different issue. Note that there is an
option to get gcc to go back to the old behaviour (inlining as the
source command).
--
Gilles.
next prev parent reply other threads:[~2010-12-07 12:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-07 11:44 [Xenomai-core] Problem with gcc-4.5.1 Anders Blomdell
2010-12-07 11:51 ` Gilles Chanteperdrix
2010-12-07 11:57 ` Gilles Chanteperdrix
2010-12-07 11:58 ` Anders Blomdell
2010-12-07 12:09 ` Gilles Chanteperdrix [this message]
2010-12-07 14:14 ` Anders Blomdell
2010-12-07 16:20 ` Anders Blomdell
2010-12-07 20:21 ` Gilles Chanteperdrix
2010-12-08 7:33 ` Anders Blomdell
2010-12-08 8:50 ` Gilles Chanteperdrix
2010-12-08 9:15 ` Anders Blomdell
2010-12-08 9:34 ` Gilles Chanteperdrix
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=4CFE23DE.8050906@domain.hid \
--to=gilles.chanteperdrix@xenomai.org \
--cc=anders.blomdell@domain.hid \
--cc=xenomai@xenomai.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.