Re: [Xenomai-core] gcc-4.6 issue
On 12/08/11 01:18, Gilles Chanteperdrix wrote: > The following patch seems to do the trick. It makes the assumption that > when compiling with -fomit-frame-pointer, we have one more register, so > the "R" constraint will always be able to avoid choosing eax, and eax > will be free for the muxcode, so that the compiler will not choose the > "m" alternative. It works, indeed. Thank you Gilles. May this patch be backported to the stable branch? Cheers, -- Daniele ___ Xenomai-core mailing list Xenomai-core@gna.org https://mail.gna.org/listinfo/xenomai-core
Re: [Xenomai-core] Bug#637425: gcc-4.6 issue
Hi, On 08/12/2011 01:18 AM, Gilles Chanteperdrix wrote: > The following patch seems to do the trick. It makes the assumption that > when compiling with -fomit-frame-pointer, we have one more register, so > the "R" constraint will always be able to avoid choosing eax, and eax > will be free for the muxcode, so that the compiler will not choose the > "m" alternative. Thanks for the update! I can confirm that both the patch for xenomai-head and -fno-omit-frame-pointer fix the problem. For Debian's xenomai 2.5.6, I will just use -fno-omit-frame-pointer for now. bye, Roland ___ Xenomai-core mailing list Xenomai-core@gna.org https://mail.gna.org/listinfo/xenomai-core
Re: [Xenomai-core] gcc-4.6 issue
Daniele Nicolodi wrote: > On 12/08/11 01:18, Gilles Chanteperdrix wrote: >> The following patch seems to do the trick. It makes the assumption that >> when compiling with -fomit-frame-pointer, we have one more register, so >> the "R" constraint will always be able to avoid choosing eax, and eax >> will be free for the muxcode, so that the compiler will not choose the >> "m" alternative. > > It works, indeed. Thank you Gilles. > > May this patch be backported to the stable branch? I do not think so, simply compile with -fno-omit-frame-pointer. -- Gilles. ___ Xenomai-core mailing list Xenomai-core@gna.org https://mail.gna.org/listinfo/xenomai-core
Re: [Xenomai-core] gcc-4.6 issue
On 12/08/11 10:18, Daniele Nicolodi wrote: > On 12/08/11 01:18, Gilles Chanteperdrix wrote: >> The following patch seems to do the trick. It makes the assumption that >> when compiling with -fomit-frame-pointer, we have one more register, so >> the "R" constraint will always be able to avoid choosing eax, and eax >> will be free for the muxcode, so that the compiler will not choose the >> "m" alternative. > > It works, indeed. Thank you Gilles. I've spoken to early. The patch does not work for the posix skin. Posix skin services return "function not implemented" errors when xenomai user space is compiled with the patch and gcc-4.6, they work just fine when compiled with gcc-4.4 (without the patch). Cheers, -- Daniele ___ Xenomai-core mailing list Xenomai-core@gna.org https://mail.gna.org/listinfo/xenomai-core
Re: [Xenomai-core] gcc-4.6 issue
Daniele Nicolodi wrote: > On 12/08/11 10:18, Daniele Nicolodi wrote: >> On 12/08/11 01:18, Gilles Chanteperdrix wrote: >>> The following patch seems to do the trick. It makes the assumption that >>> when compiling with -fomit-frame-pointer, we have one more register, so >>> the "R" constraint will always be able to avoid choosing eax, and eax >>> will be free for the muxcode, so that the compiler will not choose the >>> "m" alternative. >> >> It works, indeed. Thank you Gilles. > > I've spoken to early. The patch does not work for the posix skin. > Posix skin services return "function not implemented" errors when > xenomai user space is compiled with the patch and gcc-4.6, they work > just fine when compiled with gcc-4.4 (without the patch). Not really surprising. Then just compile with -fno-omit-frame-pointer. -- Gilles. ___ Xenomai-core mailing list Xenomai-core@gna.org https://mail.gna.org/listinfo/xenomai-core
