From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6807 invoked by alias); 29 Mar 2002 08:46:07 -0000 Mailing-List: contact gcc-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-prs-owner@gcc.gnu.org Received: (qmail 6783 invoked by uid 71); 29 Mar 2002 08:46:04 -0000 Date: Fri, 29 Mar 2002 00:46:00 -0000 Message-ID: <20020329084603.6779.qmail@sources.redhat.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, From: "Garrett D'Amore" Subject: Re: target/1538: cannot compile with #include Reply-To: "Garrett D'Amore" X-SW-Source: 2002-03/txt/msg01173.txt.bz2 List-Id: The following reply was made to PR target/1538; it has been noted by GNATS. From: "Garrett D'Amore" To: rth@gcc.gnu.org, garrett@damore.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org Cc: garrett@damore.org Subject: Re: target/1538: cannot compile with #include Date: Fri, 29 Mar 2002 00:37:30 -0800 The "standard" to which you refer is for *USERLAND* code only. When you compile kernel code for Solaris, you are not supposed to use this header since it might introduce other (conflicting) symbols. The Solaris DDI specifies the use of for builing devices drivers and other kernel code. It would be very nice if gcc knew that on Solaris is basically the same as and fixincludes automagically took care of this. Which is why I filed the request. I don't consider the item "closed" in the sense that it is resolved. It may be that the gcc team isn't interested in assisting Solaris kernel developers -- but the answer "use the standard" is wrong -- the "standard" simply doesn't apply here (i.e. to the Solaris kernel). -- Garrett > Synopsis: cannot compile with #include > > State-Changed-From-To: open->closed > State-Changed-By: rth > State-Changed-When: Thu Mar 28 23:59:24 2002 > State-Changed-Why: > Use which is what the standard specifies. > > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr > =1538