Mailing List ArchiveSupport open source code!
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]Re: tlug: gcc bug in SlackWare 3.3
- To: tlug@example.com
- Subject: Re: tlug: gcc bug in SlackWare 3.3
- From: "Stephen J. Turnbull" <turnbull@example.com>
- Date: Fri, 21 Nov 1997 14:10:23 +0900 (JST)
- Content-Transfer-Encoding: 7bit
- Content-Type: text/plain; charset=us-ascii
- In-Reply-To: <Pine.LNX.3.96.971121133050.14843C-100000@example.com>
- References: <m0xYjmf-00000LC@example.com><Pine.LNX.3.96.971121133050.14843C-100000@example.com>
- Reply-To: tlug@example.com
- Sender: owner-tlug@example.com
>>>>> "Christopher" == Christopher Wiles <wileyc@example.com> writes: Christopher> On Fri, 21 Nov 1997, Stephen J. Turnbull wrote: >> Well, GCC is up to 2.7.2.3 _specifically_ to fix problems on >> Intel platforms. I don't know what the problems are though. Christopher> Uh, not exactly ... code-wise, 2.7.2.1 was the last Christopher> real fix (the strength-reduce bug ... Jason, correct Christopher> me if I'm wrong). 2.7.2.[23] just enabled glibc Christopher> support. This is probably true ... That's why I have 2.7.2.3. Of course, there's no mention of exactly what was done in ChangeLog or NEWS :-( >> GCC may be using its own malloc. Slackware may have decided to >> use the Doug Lea malloc which is much faster but not as >> well-tested as GNU malloc. Try installing a different >> distribution's GCC (Debian or RedHat) or download binaries from >> a Sunsite mirror. Christopher> If Slackware is using a libc newer than ... hmmm, Christopher> 5.3.19 (whatever was current as of January 1996) then Christopher> it's using Doug's malloc. If you say so. I just downloaded HJL's source to 5.4.38 and it seems to say it defaults to GNU malloc. HJ is not the most accurate of documenters though. >> Look for a big regular expression. Christopher> ... also look for a pointer being freed multiple Christopher> times. Definitely not in mailindx.c. mailindx.c is not running when cc1 craps out. Something named "indx" probably uses regexps, and regexps are famous for stressing mamory allocation; it was just a shot in the dark. I really don't think poor David is quite up to finding bugs in cc1 ... we don't even have it localized to a file, let alone a function there. --------------------------------------------------------------- TLUG Meeting Dec. 13, 12:30 at Tokyo station Yaesu Chuo ticket gate 13:30 Starbuck's coffee. 13:45 HSBC | info: joem@example.com At least 3 functional Sparc IPC machines will be raffled out --------------------------------------------------------------- a word from the sponsor: TWICS - Japan's First Public-Access Internet System www.twics.com info@example.com Tel:03-3351-5977 Fax:03-3353-6096
- Follow-Ups:
- Re: tlug: gcc bug in SlackWare 3.3
- From: Christopher Wiles <wileyc@example.com>
- References:
- tlug: gcc bug in SlackWare 3.3
- From: "Stephen J. Turnbull" <turnbull@example.com>
- Re: tlug: gcc bug in SlackWare 3.3
- From: Christopher Wiles <wileyc@example.com>
Home | Main Index | Thread Index
- Prev by Date: Re: japanese pine patch [was Re: tlug: gcc bug in SlackWare 3.3]
- Next by Date: Re: japanese pine patch [was Re: tlug: gcc bug in SlackWare 3.3]
- Prev by thread: Re: tlug: gcc bug in SlackWare 3.3
- Next by thread: Re: tlug: gcc bug in SlackWare 3.3
- Index(es):
Home Page Mailing List Linux and Japan TLUG Members Links