public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: "Garrett D'Amore" <garrett@damore.org> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: target/1538: cannot compile with #include <sys/varargs.h> Date: Fri, 29 Mar 2002 00:46:00 -0000 [thread overview] Message-ID: <20020329084603.6779.qmail@sources.redhat.com> (raw) The following reply was made to PR target/1538; it has been noted by GNATS. From: "Garrett D'Amore" <garrett@damore.org> 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 <sys/varargs.h> 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 <sys/varargs.h> for builing devices drivers and other kernel code. It would be very nice if gcc knew that on Solaris <sys/varargs.h> is basically the same as <stdarg.h> 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 <sys/varargs.h> > > State-Changed-From-To: open->closed > State-Changed-By: rth > State-Changed-When: Thu Mar 28 23:59:24 2002 > State-Changed-Why: > Use <stdarg.h> which is what the standard specifies. > > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr > =1538
next reply other threads:[~2002-03-29 8:46 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-03-29 0:46 Garrett D'Amore [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-04-01 17:47 rth 2002-03-29 1:06 rth 2002-03-29 1:06 Richard Henderson 2002-03-28 23:59 rth
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20020329084603.6779.qmail@sources.redhat.com \ --to=garrett@damore.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).