From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugs-return-410471-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 25467 invoked by alias); 21 Dec 2012 08:11:44 -0000
Received: (qmail 25330 invoked by uid 48); 21 Dec 2012 08:11:24 -0000
From: "kcc at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/55341] address-sanitizer and Fortran
Date: Fri, 21 Dec 2012 08:11:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kcc at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Changed-Fields:
Message-ID: <bug-55341-4-ltSz0VRmPK@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-55341-4@http.gcc.gnu.org/bugzilla/>
References: <bug-55341-4@http.gcc.gnu.org/bugzilla/>
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
Content-Type: text/plain; charset="UTF-8"
MIME-Version: 1.0
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
X-SW-Source: 2012-12/txt/msg02079.txt.bz2


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55341

--- Comment #41 from Kostya Serebryany <kcc at gcc dot gnu.org> 2012-12-21 08:11:19 UTC ---
Wild guess: does Fortran have any custom unwinding mechanism (like exceptions
in C++ or longjmp in C)?
For C/C++ we've spent quite some time to get rid of false stack-buffer-overflow
reports caused by exceptions and longjmp.