delorie.com/archives/browse.cgi | search |
X-Authentication-Warning: | delorie.com: mail set sender to djgpp-workers-bounces using -f |
X-Recipient: | djgpp-workers AT delorie DOT com |
Date: | Mon, 21 Sep 2009 06:14:04 +0300 |
From: | Eli Zaretskii <eliz AT gnu DOT org> |
Subject: | Re: [brobecker AT adacore DOT com: GDB 6.8.91 available for testing] |
In-reply-to: | <200909210135.n8L1Zn0r016634@envy.delorie.com> |
X-012-Sender: | halo1 AT inter DOT net DOT il |
To: | djgpp-workers AT delorie DOT com |
Message-id: | <83k4ztugzn.fsf@gnu.org> |
References: | <833a6jwd5d DOT fsf AT gnu DOT org> <200909192120 DOT 52643 DOT juan DOT guerrero AT gmx DOT de> <83vdjevfzt DOT fsf AT gnu DOT org> <200909192333 DOT 50394 DOT juan DOT guerrero AT gmx DOT de> <83skeiuqt9 DOT fsf AT gnu DOT org> <200909210135 DOT n8L1Zn0r016634 AT envy DOT delorie DOT com> |
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 |
> Date: Sun, 20 Sep 2009 21:35:49 -0400 > From: DJ Delorie <dj AT delorie DOT com> > > I'm willing to re-visit the NULL problem again (perhaps gcc can handle > the problem better now), although for DJGPP it won't matter. Any specific GCC features that would allow it to handle this better? Also, do I understand correctly that you are suggesting to re-open the GCC bug? Or are you saying we should redefine NULL in DJGPP headers?
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |