From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1GbuzK-0007xW-JH
	for qemu-devel@nongnu.org; Mon, 23 Oct 2006 04:16:50 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1GbuzI-0007uh-C1
	for qemu-devel@nongnu.org; Mon, 23 Oct 2006 04:16:49 -0400
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1GbuzI-0007uF-6k
	for qemu-devel@nongnu.org; Mon, 23 Oct 2006 04:16:48 -0400
Received: from [64.233.166.181] (helo=py-out-1112.google.com)
	by monty-python.gnu.org with esmtp (Exim 4.52) id 1GbuzI-00012D-58
	for qemu-devel@nongnu.org; Mon, 23 Oct 2006 04:16:48 -0400
Received: by py-out-1112.google.com with SMTP id c63so89749pyc
	for <qemu-devel@nongnu.org>; Mon, 23 Oct 2006 01:16:14 -0700 (PDT)
Message-ID: <56d259a00610230116p33e13e32i9b82f1e8f0871f27@mail.gmail.com>
Date: Mon, 23 Oct 2006 09:16:14 +0100
From: "Martin Guy" <martinwguy@yahoo.it>
Sender: martinwguy@gmail.com
Subject: Re: [Qemu-devel] qemu vs gcc4
In-Reply-To: <Pine.LNX.4.63.0610230000050.14200@wbgn013.biozentrum.uni-wuerzburg.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <45391B22.1050608@palmsource.com>
	<Pine.LNX.4.63.0610230000050.14200@wbgn013.biozentrum.uni-wuerzburg.de>
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org

> Now, gcc4 can produce code with several return instructions (with no
> option to turn that of, as far as I understand). You cannot cut them out,
> and therefore you cannot chain the simple functions.

...unless you also map return instructions within the generated
functions into branches to the soon-to-be-dropped final "return"? Not
that I know anything about qemu internals mind u...

    M