public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jv244 at cam dot ac dot uk" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/43866] [4.3/4.4/4.5/4.6 Regression] wrong code with -fbounds-check -funswitch-loops
Date: Fri, 25 Jun 2010 09:29:00 -0000 [thread overview]
Message-ID: <20100625092839.26288.qmail@sourceware.org> (raw)
In-Reply-To: <bug-43866-6642@http.gcc.gnu.org/bugzilla/>
------- Comment #20 from jv244 at cam dot ac dot uk 2010-06-25 09:28 -------
(In reply to comment #18)
> That part comes from the questionable testcase, which does
> a_sp => matrix%local_data_sp
> before the loop unconditionally, eventhough matrix%local_data_sp is
> uninitialized unless use_sp is .true.
thanks for looking into the bug report. Actually the testcase can be turned in
'unquestionable' by adding a 'NULLIFY(a%local_data_sp)' in the main program. At
that point the pointer assignment (a_sp => matrix%local_data_sp) makes a_sp
defined, but valgrind still yields an error.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43866
next prev parent reply other threads:[~2010-06-25 9:29 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-23 9:14 [Bug middle-end/43866] New: wrong code with -O3 -fbounds-check jv244 at cam dot ac dot uk
2010-04-23 9:21 ` [Bug middle-end/43866] wrong code with -fbounds-check -funswitch-loops jv244 at cam dot ac dot uk
2010-04-23 9:25 ` jv244 at cam dot ac dot uk
2010-04-23 10:30 ` jv244 at cam dot ac dot uk
2010-04-23 12:30 ` rguenth at gcc dot gnu dot org
2010-04-23 13:32 ` jv244 at cam dot ac dot uk
2010-04-23 17:29 ` [Bug middle-end/43866] [4.3/4.4/4.5/4.6 Regression] " jv244 at cam dot ac dot uk
2010-04-26 11:07 ` jv244 at cam dot ac dot uk
2010-05-14 12:57 ` rguenth at gcc dot gnu dot org
2010-05-22 14:09 ` jv244 at cam dot ac dot uk
2010-05-22 19:00 ` rguenth at gcc dot gnu dot org
2010-06-24 13:31 ` jakub at gcc dot gnu dot org
2010-06-24 16:21 ` jakub at gcc dot gnu dot org
2010-06-24 16:24 ` jakub at gcc dot gnu dot org
2010-06-24 16:47 ` jakub at gcc dot gnu dot org
2010-06-24 20:49 ` rguenth at gcc dot gnu dot org
2010-06-25 8:13 ` jakub at gcc dot gnu dot org
2010-06-25 9:04 ` rakdver at gcc dot gnu dot org
2010-06-25 9:12 ` rakdver at gcc dot gnu dot org
2010-06-25 9:15 ` jakub at gcc dot gnu dot org
2010-06-25 9:20 ` jakub at gcc dot gnu dot org
2010-06-25 9:29 ` jv244 at cam dot ac dot uk [this message]
2010-06-25 9:39 ` jakub at gcc dot gnu dot org
2010-06-25 12:11 ` jakub at gcc dot gnu dot org
2010-06-25 12:31 ` jakub at gcc dot gnu dot org
2010-06-30 15:34 ` [Bug middle-end/43866] [4.3/4.4/4.5 " jakub 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=20100625092839.26288.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).