Problem with gfortran or did I messsed up GMP installation?

Problem with gfortran or did I messsed up GMP installation?

[Aleksandar Milivojevic]

I've just recompiled GCC 4.0.2 for sparc-sun-solaris2.9 with fortran 
language enabled.  To test it, I found short hello world program on the 
net (included).

If I produce 32-bit binary by simply using "gfortran hello.f", it 
compiles, but the resulting binary exits immediatelly (no output).  If 
I produce 64-bit binary using "gfortran -m64 hello.f", the program 
prints hello world in an infinite loop.  Hmph...

The only "unusual" thing on my system was small manual fix to have both 
32-bit and 64-bit GMP installed with same prefix.  The fix was to 
compare gmp.h file from 32-bit and 64-bit build and merge them (so that 
I can use same gmp.h file for compiling both 32-bit and 64-bit 
programs) by changing lines that define __GMP_BITS_PER_MP_LIMB and 
GMP_LIMB_BITS like this:

#ifdef  _LP64
#define __GMP_BITS_PER_MP_LIMB             64
#else   /* _ILP32 */
#define __GMP_BITS_PER_MP_LIMB             32
#endif

#ifdef  _LP64
#define GMP_LIMB_BITS                      64
#else   /* _ILP32 */
#define GMP_LIMB_BITS                      32
#endif

This looked like the correct way to go.  The same ifdef construct is 
used throughout system include files (/usr/include) for the same 
purpose.

Of course, 32-bit and 64-bit libgmp and libmpfr libraries live each in 
its own directory (32-bit in /prefix/lib, 64-bit in 
/prefix/lib/sparcv9).

So, the question is, did I broke something by attempting to have both 
32-bit and 64-bit GMP library installed simultaniously?  Did I miss 
anything needed to have both 32-bit and 64-bit GMP available on the 
system?  Or is there something wrong with gfortran compiler?

The "hello world" program looks like this.  I haven't done anything 
fortran in a veeeeeeeery long time (last time like in 1992 or 
something).  Looks to me like it should just print hello world in 
endless loop.

c
c   Hello, world.
c
      Program Hello

      implicit none
      logical DONE

      DO while (.NOT. DONE)
        write(*,10)
      END DO
   10 format('Hello, world.')
      END


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

Re: Problem with gfortran or did I messsed up GMP installation?

[Eric Botcazou]

> So, the question is, did I broke something by attempting to have both
> 32-bit and 64-bit GMP library installed simultaniously?  Did I miss
> anything needed to have both 32-bit and 64-bit GMP available on the
> system?

Do not install both 32-bit and 64-bit GMP, you only need one of them:
sparc-sun-solaris2.* compiler -> 32-bit GMP
sparc64-sun-solaris2.* compiler -> 64-bit GMP.

-- 
Eric Botcazou

Re: Problem with gfortran or did I messsed up GMP installation?

[Aleksandar Milivojevic]

Quoting Eric Botcazou <ebotcazou@libertysurf.fr>:

>> So, the question is, did I broke something by attempting to have both
>> 32-bit and 64-bit GMP library installed simultaniously?  Did I miss
>> anything needed to have both 32-bit and 64-bit GMP available on the
>> system?
>
> Do not install both 32-bit and 64-bit GMP, you only need one of them:
> sparc-sun-solaris2.* compiler -> 32-bit GMP
> sparc64-sun-solaris2.* compiler -> 64-bit GMP.

OK.....  But what if I want sparc-sun-solaris2.* compiler, and later 
want to compile some 64-bit app that links with GMP too (or the other 
way around)?  I should be able to have both libs on system where 
multilib is supported option (such as sparc*-sun-solaris*).

Anyhow, if the problem was with multilib GMP installation, I would 
expect 64-bit binary to fail.  Not 32-bit.  When compiler was 
bootstrapped, it saw 32-bit definitions in gmp.h and was linked with 
matching 32-bit GMP library.  So I would expect it to produce correct 
32-bit code.  If there were any issues with having GMP installed 
"multilib", I would expect it to generate faulty 64-bit code in this 
configuration.


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

Re: Problem with gfortran or did I messsed up GMP installation?

[Eric Botcazou]

> OK.....  But what if I want sparc-sun-solaris2.* compiler, and later
> want to compile some 64-bit app that links with GMP too (or the other
> way around)?  I should be able to have both libs on system where
> multilib is supported option (such as sparc*-sun-solaris*).

The GMP developers are probably the best persons to ask about that.

-- 
Eric Botcazou

Re: Problem with gfortran or did I messsed up GMP installation?

[Janis Johnson]

On Fri, Jan 13, 2006 at 08:56:13PM +0100, Eric Botcazou wrote:
> > OK.....  But what if I want sparc-sun-solaris2.* compiler, and later
> > want to compile some 64-bit app that links with GMP too (or the other
> > way around)?  I should be able to have both libs on system where
> > multilib is supported option (such as sparc*-sun-solaris*).
> 
> The GMP developers are probably the best persons to ask about that.

GMP is used by the compiler, not by the application, so you only need
the version that the compiler will use.

Janis

Re: Problem with gfortran or did I messsed up GMP installation?

[Eric Botcazou]

> GMP is used by the compiler, not by the application, so you only need
> the version that the compiler will use.

Right, that's what I previously said. :-)  But Aleksandar apparently insists 
on having both versions installed.

-- 
Eric Botcazou

Re: Problem with gfortran or did I messsed up GMP installation?

[Aleksandar Milivojevic]

Quoting Eric Botcazou <ebotcazou@libertysurf.fr>:

>> GMP is used by the compiler, not by the application, so you only need
>> the version that the compiler will use.
>
> Right, that's what I previously said. :-)  But Aleksandar apparently insists
> on having both versions installed.

Well, I'm not insisting...  Simply asking.  Somehow it sounded natural 
to me that there might be two applications on the system installed 
under same tree (for example 32-bit gcc and 64-bit gcc64 compiler, 
lacking any other example of application that uses GMP) that need 
different versions of the library.


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

Re: Problem with gfortran or did I messsed up GMP installation?

[Nix]

On 13 Jan 2006, Eric Botcazou mused:
>> GMP is used by the compiler, not by the application, so you only need
>> the version that the compiler will use.
> 
> Right, that's what I previously said. :-)  But Aleksandar apparently insists 
> on having both versions installed.

Doesn't Solaris have an equivalent of /usr/lib64 where you could put the
64-bit-only version?

In any case this is an OS/shared library loader thing, not anything that
anyone here can reasonably solve, I'd think.

-- 
`I must caution that dipping fingers into molten lead
 presents several serious dangers.' --- Jearl Walker

Re: Problem with gfortran or did I messsed up GMP installation?

[Aleksandar Milivojevic]

Nix wrote:
> On 13 Jan 2006, Eric Botcazou mused:
> 
>>>GMP is used by the compiler, not by the application, so you only need
>>>the version that the compiler will use.
>>
>>Right, that's what I previously said. :-)  But Aleksandar apparently insists 
>>on having both versions installed.
> 
> 
> Doesn't Solaris have an equivalent of /usr/lib64 where you could put the
> 64-bit-only version?

It has.  It is sparcv9 subdirectory of lib.  That is exactly how I have 
it installed.  32-bit version in lib/libgmp.so*, 64-bit version in 
lib/sparcv9/libgmp.so*.  They don't clash with each other (or at least 
they shouldn't).  The ifdefs I inserted into gmp.h header will provide 
correct definitions depending on compilation mode (-m32 or -m64).

> In any case this is an OS/shared library loader thing, not anything that
> anyone here can reasonably solve, I'd think.

The ld.so loads correct version of shared library.  If it wasn't, 
executable (f951) would fail at runtime with "wrong ELF class".  So, the 
OS is OK, dynamic loader is OK.  It's something between GMP and GCC.

Re: Problem with gfortran or did I messsed up GMP installation?

[Aleksandar Milivojevic]

Eric Botcazou wrote:
>> So, the question is, did I broke something by attempting to have both
>> 32-bit and 64-bit GMP library installed simultaniously?  Did I miss
>> anything needed to have both 32-bit and 64-bit GMP available on the
>> system?
> 
> Do not install both 32-bit and 64-bit GMP, you only need one of them:
> sparc-sun-solaris2.* compiler -> 32-bit GMP
> sparc64-sun-solaris2.* compiler -> 64-bit GMP.

OK, so I reinstalled GMP.  Now I have only 32-bit GMP on the system. 
Stock gmp.h file.  Recompiled gcc (4.0.2), target sparc-sun-solaris2.9. 
  Got exactly same thing.  When I compile simple looping hello world 
program (source in my first post), it exits right away.  When I use 
-m64, it works OK (loops forever printing "hello world").

Now, the interesting part.  I also built gcc 4.0.2 on 
sparc-sun-solaris2.6.  If I compile the "hello world" program on it 
(obviously it will be 32-bit), it runs just fine (prints hello world in 
endless loop).  If I copy the executable to Solaris 2.9 system and run 
it, it exits immediately.

Hmph...  Interesting...  Looks like the problem is in libgfortran?

Should I file bug on bugzilla?

Re: Problem with gfortran or did I messsed up GMP installation?

[Eric Botcazou]

> Now, the interesting part.  I also built gcc 4.0.2 on
> sparc-sun-solaris2.6.  If I compile the "hello world" program on it
> (obviously it will be 32-bit), it runs just fine (prints hello world in
> endless loop).  If I copy the executable to Solaris 2.9 system and run
> it, it exits immediately.

Please make sure every bit of the hacked GMP has been wiped out on Solaris 9.

> Hmph...  Interesting...  Looks like the problem is in libgfortran?

I don't know of any such problem with libgfortran on SPARC/Solaris.

> Should I file bug on bugzilla?

Sure, if you can reproduce it after cleaning up the Solaris 9 machine.

-- 
Eric Botcazou

Re: Problem with gfortran or did I messsed up GMP installation?

[Aleksandar Milivojevic]

Quoting Eric Botcazou <ebotcazou@libertysurf.fr>:

> Please make sure every bit of the hacked GMP has been wiped out on Solaris 9.
>
>> Should I file bug on bugzilla?
>
> Sure, if you can reproduce it after cleaning up the Solaris 9 machine.

To confirm things, I did following:

Install gcc 2.8.1 binary (from 
gnat-3.15p-sparc-sun-solaris2.5.1-bin.tar.gz) into /gcc-test (empty 
directory).  I used this one, since I guess anybody starting from 
scratch (fresh clean system) would use a binary like this (and this one 
can also bootstrap Ada compiler if needed).  /usr/local on this system 
does not conatin any include or library files.

Place /gcc-test/bin first in my path and define LD_RUN_PATH:

  $ export PATH=/gcc-test/bin:$PATH
  $ hash -r
  $ export LD_RUN_PATH=/gcc-test/lib:/gcc-test/lib/sparcv9

Install binutils 2.16:

  $ ../configure  --prefix=/gcc-test --disable-nls \
    --enable-64-bit-bfd

Compile GMP 4.1.4:

  $ ../configure ABI=32 --prefix=/gcc-test --enable-mpfr

Bootstrap GCC 4.0.2 with c and f95:

  $ ../configure --prefix=/gcc-test --with-local-prefix=/gcc-test \
    --enable-languages=c,f95 --disable-nls \
    --with-as=/gcc-test/bin/as --with-ld=/gcc-test/bin/ld \
    --with-gnu-as --with-gnu-ld \
    --with-mpfr=/gcc-test --with-gmp=/gcc-test

Prior to compilation, I removed all sources (binutils, GMP, and GCC), 
and untarred them from original tar archives.  Would this be clean 
enough?  I don't see anything wrong in the way I created this test 
environment.  If there is something wrong, please let me know.

After doing all this, the problem is still there.  So I would say I can 
reproduce it.


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

Re: Problem with gfortran or did I messsed up GMP installation?

[Eric Botcazou]

> Compile GMP 4.1.4:
>
>   $ ../configure ABI=32 --prefix=/gcc-test --enable-mpfr

Would you mind trying as documented in
  http://gcc.gnu.org/install/specific.html#sparc-sun-solaris2
i.e. with --build=sparc-sun-solaris2.9 instead of ABI=32?

Thanks in advance.

-- 
Eric Botcazou

Re: Problem with gfortran or did I messsed up GMP installation?

[Aleksandar Milivojevic]

Quoting Eric Botcazou <ebotcazou@libertysurf.fr>:

>> Compile GMP 4.1.4:
>>
>>   $ ../configure ABI=32 --prefix=/gcc-test --enable-mpfr
>
> Would you mind trying as documented in
>  http://gcc.gnu.org/install/specific.html#sparc-sun-solaris2
> i.e. with --build=sparc-sun-solaris2.9 instead of ABI=32?

I'll try it.  The only difference (AFAIK) should be that GMP will use 
only sparcv7 optimized assembler code.

I'll also try it out on Solaris 2.11 beta (just for the kicks, and 
because it is the only virgin Solaris box I have).


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

Re: Problem with gfortran or did I messsed up GMP installation?

[Aleksandar Milivojevic]

Eric Botcazou wrote:
>> Compile GMP 4.1.4:
>>
>>   $ ../configure ABI=32 --prefix=/gcc-test --enable-mpfr
> 
> Would you mind trying as documented in
>   http://gcc.gnu.org/install/specific.html#sparc-sun-solaris2
> i.e. with --build=sparc-sun-solaris2.9 instead of ABI=32?

Done.  I got same thing (32-bit hello world doesn't work, 64-bit hello 
world works).  It could still be something with my local configuration. 
  After all, 32-bit hello world works on my 2.6 box.  However, I don't 
see anything obvious...  I did builds (the ones I'm now using) in 
exactly same way on both 2.6 and 2.9.

The Solaris 2.11 build is still running (building all languages on an 
older box).  Hopefully it will be done sometime tomorrow ;-)

Re: Problem with gfortran or did I messsed up GMP installation?

[Vincent Lefevre]

Hi,

On 2006-01-25 13:10:50 -0600, Aleksandar Milivojevic wrote:
> Compile GMP 4.1.4:
> 
>  $ ../configure ABI=32 --prefix=/gcc-test --enable-mpfr

You shouldn't use the MPFR version distributed with GMP; it is very
old and buggy. It is much better to compile GMP without MPFR support
then compile MPFR 2.2.0 separately: http://www.mpfr.org/mpfr-current/

-- 
Vincent Lefèvre <vincent@vinc17.org> - Web: <http://www.vinc17.org/>
100% accessible validated (X)HTML - Blog: <http://www.vinc17.org/blog/>
Work: CR INRIA - computer arithmetic / SPACES project at LORIA

Re: Problem with gfortran or did I messsed up GMP installation?

[Aleksandar Milivojevic]

Quoting Vincent Lefevre <vincent+gcc@vinc17.org>:

> Hi,
>
> On 2006-01-25 13:10:50 -0600, Aleksandar Milivojevic wrote:
>> Compile GMP 4.1.4:
>>
>>  $ ../configure ABI=32 --prefix=/gcc-test --enable-mpfr
>
> You shouldn't use the MPFR version distributed with GMP; it is very
> old and buggy. It is much better to compile GMP without MPFR support
> then compile MPFR 2.2.0 separately: http://www.mpfr.org/mpfr-current/

Probably a good idea.  While on the subject, but not directly related 
to gcc as such, is there a way to compile gdb to use already installed 
bfd and opcodes libraries (from binutils package) instead of insisting 
on its own copy?


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

Re: Problem with gfortran or did I messsed up GMP installation?

[Aleksandar Milivojevic]

Vincent Lefevre wrote:
> You shouldn't use the MPFR version distributed with GMP; it is very
> old and buggy. It is much better to compile GMP without MPFR support
> then compile MPFR 2.2.0 separately: http://www.mpfr.org/mpfr-current/

Heh...  If MPFR 2.2.0 (fully patched) is configured with 
--enable-thread-safe option, GCC's configure script complains MPFR is 
non-functional.  Looking at config.log (that I already managed to 
remove, sorry), linker couldn't resolve some symbol with "__" and "tls" 
in name (don't remember exact name) from libmpfr.so.  Probably some 
library missing.  Seems that when MPFR is compiled without that option, 
GCC compiles (well, it's compiling as I type this, but I guess it should 
be OK).

Re: Problem with gfortran or did I messsed up GMP installation?

[Aleksandar Milivojevic]

Quoting Eric Botcazou <ebotcazou@libertysurf.fr>:

>> So, the question is, did I broke something by attempting to have both
>> 32-bit and 64-bit GMP library installed simultaniously?  Did I miss
>> anything needed to have both 32-bit and 64-bit GMP available on the
>> system?
>
> Do not install both 32-bit and 64-bit GMP, you only need one of them:
> sparc-sun-solaris2.* compiler -> 32-bit GMP
> sparc64-sun-solaris2.* compiler -> 64-bit GMP.

I did some additional testing.  I can reproduce the problem *only* on 
UltraSPARC-IIe machine.  If I run the program on any other machine, it 
runs correctly.

Also, if I statically link program on UltraSPARC-IIe machine, it 
doesn't run on any other machine.  If I statically link it on any other 
machine, it runs correctly on UltraSPARC-IIe.  Hmmmm...

I've filled bug report with more information.  This might or might not 
be the bug in gcc/f951, since obviously there are many more components 
involved (gmp, mpfr, Solaris system libraries, the processor itself, or 
any combination).  The bug ID is 25998 for those interested.


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

Re: Problem with gfortran or did I messsed up GMP installation?

[Eric Botcazou]

> I did some additional testing.  I can reproduce the problem *only* on
> UltraSPARC-IIe machine.  If I run the program on any other machine, it
> runs correctly.

Weird.

> Also, if I statically link program on UltraSPARC-IIe machine, it
> doesn't run on any other machine.  If I statically link it on any other
> machine, it runs correctly on UltraSPARC-IIe.  Hmmmm...
>
> I've filled bug report with more information.  This might or might not
> be the bug in gcc/f951, since obviously there are many more components
> involved (gmp, mpfr, Solaris system libraries, the processor itself, or
> any combination).  The bug ID is 25998 for those interested.

I'm not sure we'll be able to sort it out but, in any case, thanks for 
narrowing down the problem and for the extensive testing.

-- 
Eric Botcazou