From owner-freebsd-stable Sun Sep 6 04:00:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA05344 for freebsd-stable-outgoing; Sun, 6 Sep 1998 04:00:24 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from kinetic.ki.informatik.uni-frankfurt.de (NAFp2-096.rz.uni-frankfurt.de [141.2.23.96]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA05338 for ; Sun, 6 Sep 1998 04:00:18 -0700 (PDT) (envelope-from marko@cs.uni-frankfurt.de) Received: from localhost (localhost [127.0.0.1]) by kinetic.ki.informatik.uni-frankfurt.de (8.8.8/8.8.7) with ESMTP id MAA02501 for ; Sun, 6 Sep 1998 12:51:27 +0200 (CEST) (envelope-from marko@cs.uni-frankfurt.de) To: freebsd-stable@FreeBSD.ORG Subject: gcc, global register variables and __sputc Reply-To: marko@cs.uni-frankfurt.de X-Mailer: Mew version 1.92.4 on Emacs 19.34 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19980906125125F.marko@cs.uni-frankfurt.de> Date: Sun, 06 Sep 1998 12:51:25 +0200 From: Marko Schuetz X-Dispatcher: imput version 971024 Lines: 12 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG __sputc is defined as an inline function in stdio.h if __GNUC__ and __STDC__ are defined. gcc complains when compiling source that tries to use global register variables that there is a function definition before the definition of the global register variable. I looked at stdio.h and found the alternative definition of __sputc to be defined as a macro. I added a !defined(__USE_GLOBAL_REGISTER_VARIABLES__) to the condition for using the function definition for __sputc. Should something like this be added to -stable or are there reasons against this that I do not see? Marko To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message