From: "Alexei A. Frounze" Newsgroups: comp.os.msdos.djgpp Subject: GCC bugs Date: 17 Jan 2000 18:36:47 GMT Organization: MTU-Intel ISP Lines: 32 Message-ID: <01bf611a$9c6e9500$LocalHost@alex> NNTP-Posting-Host: dial56250.mtu-net.ru X-Trace: gavrilo.mtu.ru 948134207 26009 195.34.56.250 (17 Jan 2000 18:36:47 GMT) X-Complaints-To: usenet-abuse AT mtu DOT ru NNTP-Posting-Date: 17 Jan 2000 18:36:47 GMT X-Newsreader: Microsoft Internet News 4.70.1155 To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com Hi guys! I've found a very strange thing. When I run GCC from a command line: c:\kernel\!flat\>gcc -c kernel.c and I run a batch file (make-c.bat): @echo off gcc -c kernel.c I get different output coff files (kernel.o). For example, the first method generates a kernel.o that contains 4 sections (.text, .data, .bss and .eh_fram), but the second generates only 3 standard sections (.text, .data and .bss). What does it mean? The second thing that I wonder is how the GCC works itself. Sometimes it terminates with internal error (GPF I think), but if you run it again immediately after the crash, it may work normally. What does it mean? Both these bugs are present on different computers where I use DJGPP. Your comments... Thanks in advance. Alexei A. Frounze -- P.S. In order to reply via e-mail, remove the "n-o-s-p-a-m." substring out of the e-mail address.