From owner-freebsd-current Mon Nov 8 12:23:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id 0E6CD150CD for ; Mon, 8 Nov 1999 12:23:25 -0800 (PST) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <40325>; Tue, 9 Nov 1999 07:17:29 +1100 Content-return: prohibited Date: Tue, 9 Nov 1999 07:23:15 +1100 From: Peter Jeremy Subject: Re: show stopper for Gcc 2.95.2 conversion In-reply-to: <199911081801.NAA29633@lor.watermarkgroup.com> To: Luoqi Chen Cc: freebsd-current@FreeBSD.ORG Reply-To: peter.jeremy@alcatel.com.au Message-Id: <99Nov9.071729est.40325@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0pre3i Content-type: text/plain; charset=us-ascii References: <199911081801.NAA29633@lor.watermarkgroup.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 1999-Nov-09 05:01:43 +1100, Luoqi Chen wrote: >> + "=D" (addr), "=c" (count) : >> + "r" (bsh + offset), "0" (addr), "1" (count) : >> + "%eax", "memory"); >You may use "+D" and "+c" for the in-out operands, > "+D" (addr), "+c" (count) : > "r" (bsh + offset) : > Just as a word of caution: "+" isn't supported prior to gcc 2.8.x, so you can't use it for code that might be MFC to 3.x. And just to make it more of a pain, I've found code similar to the original patch also fails on gcc 2.7 when the operands are volatile :-(. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message