From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18064 invoked by alias); 19 Dec 2012 10:32:52 -0000 Received: (qmail 17595 invoked by uid 48); 19 Dec 2012 10:32:30 -0000 From: "kcc at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/55341] address-sanitizer and Fortran Date: Wed, 19 Dec 2012 10:32: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: In-Reply-To: References: 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: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2012-12/txt/msg01847.txt.bz2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55341 --- Comment #25 from Kostya Serebryany 2012-12-19 10:32:29 UTC --- >> So, to fix this, either libasan should for memset ignore any diagnostics for >> stores into shadow memory area, That's not a good choice. I remember actually catching a bug or two when a program was reading wild addresses and hitting the shadow. >> or I'll need to force somehow that memset is never generated for it, This is imho the best choice. >> or we could have a non-instrumented memset alternative in libasan and we could call that. That's doable too, although it will look strange and I'd prefer to avoid this.