From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 89690 invoked by alias); 26 Jan 2016 17:36:32 -0000 Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-patches-owner@gcc.gnu.org Received: (qmail 89666 invoked by uid 89); 26 Jan 2016 17:36:31 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-0.8 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 spammy=dear, management, hear X-Spam-User: qpsmtpd, 2 recipients X-HELO: mail-ob0-f177.google.com Received: from mail-ob0-f177.google.com (HELO mail-ob0-f177.google.com) (209.85.214.177) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-GCM-SHA256 encrypted) ESMTPS; Tue, 26 Jan 2016 17:36:30 +0000 Received: by mail-ob0-f177.google.com with SMTP id zv1so46675039obb.2; Tue, 26 Jan 2016 09:36:30 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=dizoJoXz9u68mzCQpFilSzRh1oL+Vjbx0tqoYW1jZB8=; b=Jf2shcTrQKmuSoM3+6CZecm4chYM5VhM0bXfb09G501cBpnLur1MaA7leYwuUSl2D1 Jm5+gcMutL2DKtQvJQxA6RtzPtWnAc7W10+Y0wJ//pTTtv1Slkyb4sNZ2oR5xBSHlCov JQFJODmxXNLe0nHHshaujceDBcRUCMRRY8IrEEoYRvyM8Z9eNQ2IdawiBPYkpvYZCbs5 8I0lTjkIriOHzJ39yBEi0BbVrA3Tt1NMR1pBxMG9jbdeU+KAo3JFbk6BKpAWBXF2VtgU fWVvMV3ZZ/2DxgXC/JYEC3QvySLN2mxgtHo6u2mBlbU4Aoxjg+oivtov05+0N9fzWHed CDDQ== X-Gm-Message-State: AG10YOSSTRYorZxjerTWeOQGxrdudKn2TLooyYzFtTTWj0CVqVXQsH5UVlaVScEiiJK7M92wYckU/ipuD9wcyQ== MIME-Version: 1.0 X-Received: by 10.182.241.134 with SMTP id wi6mr18659303obc.81.1453829788965; Tue, 26 Jan 2016 09:36:28 -0800 (PST) Received: by 10.202.175.19 with HTTP; Tue, 26 Jan 2016 09:36:28 -0800 (PST) In-Reply-To: <20160126132816.5a8c9f35@vepi2> References: <20160126132816.5a8c9f35@vepi2> Date: Tue, 26 Jan 2016 17:36:00 -0000 Message-ID: Subject: Re: [Fortran, gcc-5, patch, pr69268, v1] [5 Regression] Sourced allocation calls function twice From: Paul Richard Thomas To: Andre Vehreschild Cc: GCC-Patches-ML , GCC-Fortran-ML Content-Type: text/plain; charset=UTF-8 X-SW-Source: 2016-01/txt/msg02015.txt.bz2 Dear Andre, The patch looks fine to me. OK for 5-branch. Thanks for the patch. Paul On 26 January 2016 at 13:28, Andre Vehreschild wrote: > Hi all, > > please find attached a patch to solve the issue of evaluating a source= > expression of an allocate() twice in gcc-5. The patch is a combination > and partial back port of several prs of the mainline (namely, but not > the complete list: pr44672, pr65548). > > The patch needed the counts of builtin_mallocs/frees in > allocatable_scalar_13 to be adapted. There are now fewer calls to the > memory management routines. Valgrind does not report any memory issues > in the modified code, but that does not mean there aren't any. I am > happy to hear about any issue, this patch causes (still having issues > getting the sanitizer to work). > > Bootstrapped and regtested on x86_64-linux-gnu/F23. > > Ok, for gcc-5-branch? > > Regards, > Andre > -- > Andre Vehreschild * Email: vehre ad gmx dot de -- The difference between genius and stupidity is; genius has its limits. Albert Einstein