From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23500 invoked by alias); 13 Aug 2008 08:43:13 -0000 Received: (qmail 23487 invoked by uid 22791); 13 Aug 2008 08:43:12 -0000 X-Spam-Check-By: sourceware.org Received: from kuber.nabble.com (HELO kuber.nabble.com) (216.139.236.158) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 13 Aug 2008 08:42:05 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1KTBvf-0002x8-5k for gcc-help@gcc.gnu.org; Wed, 13 Aug 2008 01:42:03 -0700 Message-ID: <18959097.post@talk.nabble.com> Date: Wed, 13 Aug 2008 17:27:00 -0000 From: Robin-Vossen To: gcc-help@gcc.gnu.org Subject: Re: GNU C++ Inline Assembler In-Reply-To: <1218508063.5985.7.camel@bob-desktop> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: robin-vossen@hotmail.com References: <18912389.post@talk.nabble.com> <1218415637.5988.10.camel@bob-desktop> <18929255.post@talk.nabble.com> <48A08513.6050103@redhat.com> <1218489833.5989.6.camel@bob-desktop> <48A0E23F.EE8BC28C@dessent.net> <1218508063.5985.7.camel@bob-desktop> X-IsSubscribed: yes Mailing-List: contact gcc-help-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-help-owner@gcc.gnu.org X-SW-Source: 2008-08/txt/msg00130.txt.bz2 Thanks ALL, I think I can continue doing my work soon now. I understand that I'd lose a lot of preformance doing it the MS way. But, well I dont need speed =) Since I am a RCE I need it to check if I was sure the code did that I thought it would do. ^^ But, yea this will help me. I'll read the three links I've got from you guys and then Ill continue asking Quesitons if something is still not clear to me. Thanks for everything. Cheers, Robin Bob Plantz wrote: > > On Mon, 2008-08-11 at 18:07 -0700, Brian Dessent wrote: > >> Because the MSVC style of inline assembler doesn't allow for specifying >> any constraints such as which registers or stack slots are clobbered. >> This means that compiler can't assume anything about the state before >> and after the block, it must just throw away all dataflow information it >> had before the block and assume everything was clobbered, leading to >> tons of useless redundant loads/stores. The GNU style inline asm works >> within the framework of the optimizing compiler, rather than outside it >> by totally going behind it's back. >> >> Read the long thread that starts here: >> . > > Thank you for the explanation and the link. I've never been a Microsoft > programmer, and I haven't used CodeWarrior (Mac PowerPC) for a long > time. I had forgotten about that technique of inline assembly. > > Bob > > > > -- View this message in context: http://www.nabble.com/GNU-C%2B%2B-Inline-Assembler-tp18912389p18959097.html Sent from the gcc - Help mailing list archive at Nabble.com.