From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: In-Reply-To: <4E44FBAA.1010301@domain.hid> References: <4E43B5FE.4040402@domain.hid> <4E43B7E8.5000302@domain.hid> <4E43C056.9040007@domain.hid> <4E43EBC6.10808@domain.hid> <4E440FAC.5020107@domain.hid> <4E4411DB.80009@domain.hid> <4E444102.10206@domain.hid> <4E446345.9060705@domain.hid> <4E44E1C2.50800@domain.hid> <4E44FBAA.1010301@domain.hid> Date: Fri, 12 Aug 2011 12:11:14 +0200 (CEST) From: "Gilles Chanteperdrix" MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit Subject: Re: [Xenomai-core] gcc-4.6 issue List-Id: Xenomai life and development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Daniele Nicolodi Cc: xenomai@xenomai.org 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.