--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
Target Milestone|--- |4.1.0
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24541
--- Comment #9 from pinskia at gcc dot gnu dot org 2005-12-30 18:25 ---
(In reply to comment #8)
> Could we get a gcc-admin script to change the library's version everyday with
> version numbers like 0.0.20051115 and so on?
That seems like a bad idea. Anyways this is fixed already.
-
--- Comment #8 from fxcoudert at gcc dot gnu dot org 2005-11-15 12:14
---
(In reply to comment #7)
> We should bump the library file's version number.
Could we get a gcc-admin script to change the library's version everyday with
version numbers like 0.0.20051115 and so on?
--
http
--- Comment #7 from tobi at gcc dot gnu dot org 2005-10-27 17:21 ---
We should bump the library file's version number.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24541
--- Comment #6 from steven at gcc dot gnu dot org 2005-10-26 17:46 ---
Re. comment #5, yes other library ABIs change too, but libgfortran is special
in that what shipped with GCC 4.0 was highly experimental and never intended to
be a stable interface. The decision at the time was that b
--- Comment #5 from hjl at lucon dot org 2005-10-26 16:19 ---
So what? ABI of glibc changes. ABI of libstdc++ changes. When the ABI changes,
we should manage it in such a way that it won't cause problems for existing
executables and shared libraries.
--
http://gcc.gnu.org/bugzilla/s
--- Comment #4 from pinskia at gcc dot gnu dot org 2005-10-26 16:07 ---
This is still minor as the ABI was expected to change and really you should not
be doing this.
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
--
--- Comment #3 from hjl at lucon dot org 2005-10-26 16:06 ---
Then rename _gfortran_ioparm to something like _gfortran_version_4.1_ioparm
and change soname of libgfortran from libgfortran.so.0 to something like
libgfortran.so.0.1. When libgfortran's ABI is changed, we should update
its s
--- Comment #2 from pinskia at gcc dot gnu dot org 2005-10-26 15:56 ---
This is actually the issue is that 4.0.x's gfortran is experimental and really
should not be thought about be used in normal use, even to compile and then
link with a newer version. This has been discussed before.
--- Comment #1 from hjl at lucon dot org 2005-10-26 15:01 ---
I built SPEC CPU 2K with gcc 4.0 and ran with libgfortran.so in gcc 4.1. I
got
Specinvoke: /export/spec/src/2000/spec/bin/specinvoke -E -d
/export/spec/src/2000/spec/benchspec/CFP2000/172.mgrid/run/0002 -c 1 -e
compare.er
10 matches
Mail list logo
