public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kenneth.hoste at elis dot ugent.be" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/40737] Pointer references sometimes fail to define "span" symbols
Date: Thu, 23 Jun 2011 07:37:00 -0000 [thread overview]
Message-ID: <bug-40737-4-1D3CMMwxns@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-40737-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40737
Kenneth Hoste <kenneth.hoste at elis dot ugent.be> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |kenneth.hoste at elis dot
| |ugent.be
--- Comment #14 from Kenneth Hoste <kenneth.hoste at elis dot ugent.be> 2011-06-23 07:36:41 UTC ---
Seems like this issue is still present in the GCC 4.6 branch, at least in GCC
4.6.0 and a checkout on 20110617 of the 4.6 branch.
I can confirm that patching the tera_tf source as suggested by David fixes the
issue, but the runtime still fails: the benchmark seems stuck in an infinite
loop or something when compiled with "-Ofast -march=native -mtune=native
-floop-strip-mine -floop-interchange -floop-block" at least. Not sure if the
failing runtime is caused by this issue though.
Is the patch that has been proposed insufficient?
Any of you know whether anyone has been able to build whole of SPEC MPI2007
using (a recent) GCC?
next prev parent reply other threads:[~2011-06-23 7:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-40737-4@http.gcc.gnu.org/bugzilla/>
2010-12-28 22:31 ` dfranke at gcc dot gnu.org
2011-01-22 23:46 ` dominiq at lps dot ens.fr
2011-06-23 7:37 ` kenneth.hoste at elis dot ugent.be [this message]
2013-01-06 14:56 ` burnus at gcc dot gnu.org
2015-08-30 10:26 ` dominiq at lps dot ens.fr
2009-07-13 21:37 [Bug fortran/40737] New: " dh458 at oakapple dot net
2009-07-13 21:39 ` [Bug fortran/40737] " dh458 at oakapple dot net
2009-07-13 21:40 ` dh458 at oakapple dot net
2009-07-14 7:50 ` burnus at gcc dot gnu dot org
2009-07-21 15:19 ` dh458 at oakapple dot net
2009-07-22 7:11 ` burnus at gcc dot gnu dot org
2009-07-22 7:13 ` burnus at gcc dot gnu dot org
2009-07-22 9:21 ` burnus at gcc dot gnu dot org
2009-10-06 22:04 ` bergner at gcc dot gnu dot org
2009-10-06 23:10 ` kargl at gcc dot gnu dot org
2009-10-07 8:20 ` burnus at gcc dot gnu dot org
2009-10-07 22:42 ` dh458 at oakapple dot net
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=bug-40737-4-1D3CMMwxns@http.gcc.gnu.org/bugzilla/ \
--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).