Re: [Fink-devel] Re: Bug in as from Dec2002gccUpdater.pkg

2003-07-27 Thread Andrew Pinski
Just to keep you guys up to date on this problem, this is fixed in the 
FSF's CVS version of gcc
by: <http://gcc.gnu.org/ml/gcc-patches/2003-07/msg02565.html>.

Thanks,
Andrew Pinski


On Tuesday, Jul 1, 2003, at 10:25 US/Eastern, Andrew Pinski wrote:

A workaround is to use -mdynamic-no-pic (that even speeds up your 
programs).
Note -mdynamic-no-pic should not be used with shared libraries, also 
it is not
in the FSF's gcc until 3.4 (aka it is in the cvs).
I have filed a bug with the FSF, http://gcc.gnu.org/PR11387  because I 
still think this is a gcc bug
(and not an apple specific one, I can reproduce it with the mainline 
of the FSF's gcc) and not an as bug either.

Thanks,
Andrew Pinski


---
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01/01
___
Fink-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-devel


Re: [Fink-devel] Re: Bug in as from Dec2002gccUpdater.pkg

2003-07-01 Thread Andrew Pinski
A workaround is to use -mdynamic-no-pic (that even speeds up your 
programs).
Note -mdynamic-no-pic should not be used with shared libraries, also it 
is not
in the FSF's gcc until 3.4 (aka it is in the cvs).
I have filed a bug with the FSF, http://gcc.gnu.org/PR11387  because I 
still think this is a gcc bug
(and not an apple specific one, I can reproduce it with the mainline of 
the FSF's gcc) and not an as bug either.

Thanks,
Andrew Pinski
On Tuesday, Jul 1, 2003, at 08:27 US/Eastern, Max Horn wrote:

Am Dienstag, 01.07.03 um 10:04 Uhr schrieb Martin Costabel:

Andrew Pinski wrote:

OK, I hunted it down. It is really too silly: The code produced by 
a fortran STOP statement (without optional stop-code) is treated as 
an error by the new assembler. Definitely a bug in as.
No because gcc should produce something at that symbol but it is 
not, so the bug still is in gcc, not as.
Actually, the situation is worse: g77 is doing this in many other 
situations. The simple "Hello World" program

 PRINT*,'Hello World'
 END
produces this error, and even the minimal program

	 END

does it. All versions of g77 I could get my hands on produce a label 
without data in this case. No other assembler than the new Apple one 
considers this an error.

What are the chances that we will see a fix of this bug in gcc-3.3 so 
that we will be able to use g77 again with Apple's new assembler?

From what you are saying and given Apple's repeatedly demonstrated 
lack of interest in g77, I fear that the user will be left out in the 
cold on this.

Lack of interest? Just because they don't ship it doesn't mean they 
lack interest in it. I think Apple is well aware that a noticable 
share of its users are coming from science, and Fortran (that includes 
G77) is vital there.Don't give up to early. File bug reports with 
Apple's bug reporter, and get everybody else to file the bug, too 
(yeah this time I am advocating multiple bug reports. If many people 
complain, maybe they notice that it's not just an oddball weirdo user 
experiencing the problem).

My real concern here isn't whether they'll fix it; rather, *if* they 
fix it: maybe you have to wait again half a year before they release a 
dev tools bug fix update *grmbl*.

Max





---
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa0016ave/direct;at.asp_061203_01/01
___
Fink-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-devel


[Fink-devel] Re: Bug in as from Dec2002gccUpdater.pkg

2003-06-30 Thread Andrew Pinski
On Monday, Jun 30, 2003, at 19:14 US/Eastern, Martin Costabel wrote:

Andrew Pinski wrote:

The as error is right here, the problem is gcc is producing wrong 
asm, I will look into it.
OK, I hunted it down. It is really too silly: The code produced by a 
fortran STOP statement (without optional stop-code) is treated as an 
error by the new assembler. Definitely a bug in as.
No because gcc should produce something at that symbol but it is not, 
so the bug still is in gcc, not as.
The following program shows the error

PROGRAM DUMB
STOP
END
This program gives no error:

PROGRAM SILLY
STOP 'silly'
END
Which means the bug is in gcc, not as.


--
Martin





---
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa0016ave/direct;at.asp_061203_01/01
___
Fink-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-devel