public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fxcoudert at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/27588] -fbounds-check should catch substring out of range accesses
Date: Thu, 08 Jun 2006 09:11:00 -0000 [thread overview]
Message-ID: <20060608090155.32710.qmail@sourceware.org> (raw)
In-Reply-To: <bug-27588-1719@http.gcc.gnu.org/bugzilla/>
------- Comment #2 from fxcoudert at gcc dot gnu dot org 2006-06-08 09:01 -------
I'm writing a patch to add substring bounds checking. I hope to post it in the
next few days.
--
fxcoudert at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |fxcoudert at gcc dot gnu dot
| |org
AssignedTo|unassigned at gcc dot gnu |fxcoudert at gcc dot gnu dot
|dot org |org
Status|NEW |ASSIGNED
Last reconfirmed|2006-06-05 21:01:03 |2006-06-08 09:01:54
date| |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27588
next prev parent reply other threads:[~2006-06-08 9:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-13 14:07 [Bug fortran/27588] New: " tobias dot burnus at physik dot fu-berlin dot de
2006-05-13 14:07 ` [Bug fortran/27588] " tobias dot burnus at physik dot fu-berlin dot de
2006-06-05 21:16 ` pault at gcc dot gnu dot org
2006-06-08 9:11 ` fxcoudert at gcc dot gnu dot org [this message]
2006-10-02 15:15 ` tobias dot burnus at physik dot fu-berlin dot de
2006-10-02 15:32 ` Francois-Xavier dot Coudert at ens dot fr
2006-10-05 8:08 ` patchapp at dberlin dot org
2006-11-10 20:46 ` burnus at gcc dot gnu dot org
2006-11-10 22:41 ` burnus at gcc dot gnu dot org
2006-11-11 1:25 ` patchapp at dberlin dot org
2006-11-15 10:13 ` burnus at gcc dot gnu dot org
2006-11-15 10:16 ` burnus at gcc dot gnu dot org
2006-12-01 2:06 ` chaoyingfu at gcc dot gnu dot org
2007-01-31 10:24 ` burnus 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=20060608090155.32710.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).