public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "burnus at gcc dot gnu dot org" <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 22:19:00 -0000 [thread overview] Message-ID: <20091107221949.32019.qmail@sourceware.org> (raw) In-Reply-To: <bug-41977-15342@http.gcc.gnu.org/bugzilla/> ------- Comment #11 from burnus at gcc dot gnu dot org 2009-11-07 22:19 ------- Which version of ACML are you using? I get a bit confused with all those 4-dot-something version numbers as both GCC and ACML have them. Do you use ACML 4.3.0? strings /opt/acml4.3.0/gfortran64/lib/libacml.a |grep GCC |sort -u strings /opt/acml4.3.0/gfortran64_mp/lib/libacml_mp.so |grep GCC |sort -u shows here: Built using Fortran compiler: GNU Fortran (GCC) 4.3.2 Thus it should be ABI compatible with GCC 4.3.x, 4.4.x and 4.5.x. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41977
next prev parent reply other threads:[~2009-11-07 22:19 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 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 [this message] 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=20091107221949.32019.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: linkBe 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).