public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pault at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/29371] Coredump when using -fbounds-check with pointer & nullify
Date: Wed, 11 Oct 2006 20:43:00 -0000 [thread overview]
Message-ID: <20061011204323.18854.qmail@sourceware.org> (raw)
In-Reply-To: <bug-29371-1719@http.gcc.gnu.org/bugzilla/>
------- Comment #2 from pault at gcc dot gnu dot org 2006-10-11 20:43 -------
Created an attachment (id=12412)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=12412&action=view)
The correct fix for this PR
THis turns out to be completely specific to nullify, or to a pointer assign to
NULL(). Looking at the code for pointer assignment, we immediately see that
the descriptor data set is being added to the block, FOLLOWED by the pre and
post blocks. Since -fbounds-check fixes the value of the index in the pre
block, the net result is an index that is used before it is set. The fix adds
the data set to the pre block, thereby putting things in the right order.
I'll just regtest this and then submit it.
Paul
--
pault at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #12395|0 |1
is obsolete| |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29371
next prev parent reply other threads:[~2006-10-11 20:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-06 14:29 [Bug fortran/29371] New: " tobias dot burnus at physik dot fu-berlin dot de
2006-10-07 21:23 ` [Bug fortran/29371] " pault at gcc dot gnu dot org
2006-10-07 21:24 ` pault at gcc dot gnu dot org
2006-10-11 20:43 ` pault at gcc dot gnu dot org [this message]
2006-10-12 0:15 ` patchapp at dberlin dot org
2006-10-14 13:10 ` pault at gcc dot gnu dot org
2006-10-14 13:19 ` pault at gcc dot gnu dot org
2006-11-10 21:53 ` pault 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=20061011204323.18854.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).