public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "nmm1 at cam dot ac dot uk" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/41977] gfortran -fopenp and ACML_MP seem incompatible
Date: Sat, 07 Nov 2009 18:56:00 -0000	[thread overview]
Message-ID: <20091107185619.12439.qmail@sourceware.org> (raw)
In-Reply-To: <bug-41977-15342@http.gcc.gnu.org/bugzilla/>



------- Comment #8 from nmm1 at cam dot ac dot uk  2009-11-07 18:56 -------
Subject: Re:  gfortran -fopenp and ACML_MP seem incompatible

On Nov 7 2009, rguenth at gcc dot gnu dot org wrote:
>
> ------- Comment #7 from rguenth at gcc dot gnu dot org 2009-11-07 18:40 
> ------- I suspect acml_mp is built using a different GCC version and they 
> link libgomp statically. Can you check what the acml_mp library links 
> against? Just use ldd for this. Then check that this is consistent with 
> what your test program uses.

Nothing noticeable.  The only lines that are in the executable and not
acml_mp are:
      libacml_mp.so => /usr/local/lib64/libacml_mp.so
      libgcc_s.so.1 => /lib64/libgcc_s.so.1
and the only line that is in acml_mp but not acml is:
      libgomp.so.1 => /usr/lib64/libgomp.so.1

No other differences (checked by diff), except for the hex. grobble in
brackets.  Checking the binary for the lapack version shows that the only
difference from the failing one is the ACML libraries are replaced by
LAPACK and BLAS.

It could still be a gcc version problem, of course, but not in that respect.

Regards,
Nick.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41977


  parent reply	other threads:[~2009-11-07 18:56 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-07 17:36 [Bug fortran/41977] New: " nmm1 at cam dot ac dot uk
2009-11-07 17:44 ` [Bug fortran/41977] " nmm1 at cam dot ac dot uk
2009-11-07 17:46 ` nmm1 at cam dot ac dot uk
2009-11-07 17:46 ` nmm1 at cam dot ac dot uk
2009-11-07 17:48 ` nmm1 at cam dot ac dot uk
2009-11-07 18:25 ` kargl at gcc dot gnu dot org
2009-11-07 18:29 ` nmm1 at cam dot ac dot uk
2009-11-07 18:40 ` rguenth at gcc dot gnu dot org
2009-11-07 18:56 ` nmm1 at cam dot ac dot uk [this message]
2009-11-07 19:00 ` kargl at gcc dot gnu dot org
2009-11-07 19:15 ` nmm1 at cam dot ac dot uk
2009-11-07 22:19 ` burnus at gcc dot gnu dot org
2009-11-07 23:33 ` nmm1 at cam dot ac dot uk
2009-11-10 13:32 ` nmm1 at cam dot ac dot uk
2009-11-10 20:30 ` jvdelisle at gcc dot gnu dot org
2009-11-10 21:49 ` nmm1 at cam dot ac dot uk
2010-05-07 16:41 ` [Bug fortran/41977] gfortran -fopenmp " dfranke at gcc dot gnu dot org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20091107185619.12439.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).