RE: gcc bug, cygwin specific cygwin-1.3.10-1 gcc-2.95.3-5

2002-03-13 Thread Robinow, David
From: Alex Song [mailto:[EMAIL PROTECTED]] is end being a global variable specific to the C language (which i doubt) ? to gcc ? to cygwin ? to windows ? or is it ALWAYS the case ? It's not always the case. I was able to compile/run the test program on Solaris, with three different compilers,

RE: gcc bug, cygwin specific cygwin-1.3.10-1 gcc-2.95.3-5

2002-03-13 Thread Heribert Dahms
Song [SMTP:[EMAIL PROTECTED]] Sent: Wednesday, March 13, 2002 08:14 To: Michael A Chase; [EMAIL PROTECTED] Subject: RE: gcc bug, cygwin specific cygwin-1.3.10-1 gcc-2.95.3-5 hi, is end being a global variable specific to the C language (which i doubt) ? to gcc ? to cygwin

Re: gcc bug, cygwin specific cygwin-1.3.10-1 gcc-2.95.3-5

2002-03-12 Thread Alex Song
hi, i think i have found a bug, either that or i am very stupid. the bug is a gcc bug and it is cygwin specific (cygwin-1.3.10-1 gcc-2.95.3-5) and the following code causes a seg fault: --- int end; int main () { end = 1; return 0; }

RE: gcc bug, cygwin specific cygwin-1.3.10-1 gcc-2.95.3-5

2002-03-12 Thread Alex Song
The global 'end' is a reserved word. It refers to the end of the data area. That means you can't use it as a global variable in your program. is this reserved word cygwin specific ? or is it a reserved word for all gcc ? thanks for your help. cheers, alex

Re: gcc bug, cygwin specific cygwin-1.3.10-1 gcc-2.95.3-5

2002-03-12 Thread Michael A Chase
/smart-questions.html Give a hobbit a fish and he eats fish for a day. Give a hobbit a ring and he eats fish for an age. - Original Message - From: Alex Song [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, March 12, 2002 19:19 Subject: RE: gcc bug, cygwin specific cygwin-1.3.10-1 gcc

RE: gcc bug, cygwin specific cygwin-1.3.10-1 gcc-2.95.3-5

2002-03-12 Thread Alex Song
specific cygwin-1.3.10-1 gcc-2.95.3-5 The global 'end' is a reserved word. It refers to the end of the data area. That means you can't use it as a global variable in your program. is this reserved word cygwin specific ? or is it a reserved word for all gcc ? -- Unsubscribe info

Re: gcc bug, cygwin specific cygwin-1.3.10-1 gcc-2.95.3-5

2002-03-08 Thread Christopher Faylor
On Fri, Mar 08, 2002 at 05:03:26PM +1000, Alex Song wrote: hi, i think i have found a bug, either that or i am very stupid. the bug is a gcc bug and it is cygwin specific (cygwin-1.3.10-1 gcc-2.95.3-5) and the following code causes a seg fault: --- int