From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.34) id 1BTY4I-0001FD-T6 for qemu-devel@nongnu.org; Thu, 27 May 2004 23:30:03 -0400 Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.34) id 1BTWfM-0000ac-9r for qemu-devel@nongnu.org; Thu, 27 May 2004 22:00:44 -0400 Received: from [194.226.236.116] (helo=ums.usu.ru) by monty-python.gnu.org with esmtp (TLSv1:DES-CBC3-SHA:168) (Exim 4.34) id 1BTW0u-0000Zd-PW for qemu-devel@nongnu.org; Thu, 27 May 2004 21:18:25 -0400 Message-ID: <40B693A7.9050006@ums.usu.ru> Date: Fri, 28 May 2004 07:19:35 +0600 From: "Alexander E. Patrakov" MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] Overoptimization Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org The CFLAGS in Makefile.target are bad for gcc 3.3.2. This is not a my problem with my gcc, because it passes the "make check" testsuite except some known errors in libstdc++, which cannot affect qemu. The victim is the tcp_input function in slirp. When compiling with the decault CFLAGS, for some reason all packets are dropped as having a wrong TCP checksum. I tried debugging this by placing some debug printfs in tcp_input.c file, but the problem disappeared after I inserted them. I concluded that it is very strange and compiled this tcp_input.c file without my debug statements, but with -O1 instead of -O2. The problem went away. Will this workaround (use of -O1 instead of -O2 for tcp_input.c) enter the qemu CVS? -- Alexander E. Patrakov