delorie.com/archives/browse.cgi | search |
From: | "Tim Van Holder" <tim DOT van DOT holder AT pandora DOT be> |
To: | <djgpp-workers AT delorie DOT com> |
Subject: | Re: Built-in bzero |
Date: | Sun, 4 Nov 2001 15:03:27 +0100 |
Message-ID: | <000e01c16539$7a056640$797c76d5@pandora.be> |
MIME-Version: | 1.0 |
X-Priority: | 3 (Normal) |
X-MSMail-Priority: | Normal |
X-Mailer: | Microsoft Outlook, Build 10.0.2627 |
X-MimeOLE: | Produced By Microsoft MimeOLE V5.50.4807.1700 |
In-Reply-To: | <Pine.SUN.3.91.1011104121135.18397K@is> |
Importance: | Normal |
Reply-To: | djgpp-workers AT delorie DOT com |
Errors-To: | nobody AT delorie DOT com |
X-Mailing-List: | djgpp-workers AT delorie DOT com |
X-Unsubscribes-To: | listserv AT delorie DOT com |
> On Sun, 4 Nov 2001, Tim Van Holder wrote: > > > In the case of bzero, it looks like it expects > > void bzero (<anything>); > > (i.e. only the return type (void) is 'hardcoded'). > > Then it sounds like a GCC bug that it complains, doesn't it? Yup - but as DJ said (I hadn't seen his reply when I wrote mine), they later build a prototype that apparently expects (char*, int). In any case, I guess it's worth reporting to gcc-bugs, with an optional feature-request for --dump-builtins.
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |