From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 66932 invoked by alias); 6 Aug 2017 14:37:09 -0000 Mailing-List: contact fortran-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: fortran-owner@gcc.gnu.org Received: (qmail 66912 invoked by uid 89); 6 Aug 2017 14:37:08 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=0.6 required=5.0 tests=AWL,BAYES_05,FREEMAIL_FROM,KAM_LAZY_DOMAIN_SECURITY,RP_MATCHES_RCVD autolearn=no version=3.3.2 spammy=H*r:8.6.060, H*r:ip*8.6.060.43, 5x, 6x X-HELO: smtp204.alice.it Received: from smtp204.alice.it (HELO smtp204.alice.it) (82.57.200.100) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Sun, 06 Aug 2017 14:37:06 +0000 Received: from [192.168.1.102] (95.239.230.82) by smtp204.alice.it (8.6.060.43) (authenticated as angelo.graziosi@alice.it) id 59854DFC0111E4A3; Sun, 6 Aug 2017 16:37:03 +0200 Subject: Re: About 'error stop' statement To: mexas@bris.ac.uk, fortran@gcc.gnu.org References: <201708061223.v76CNoP5021680@mech-as222.men.bris.ac.uk> From: Angelo Graziosi Message-ID: <6d885d0d-e5aa-b07c-9744-66f777f98ecb@alice.it> Date: Sun, 06 Aug 2017 14:37:00 -0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: <201708061223.v76CNoP5021680@mech-as222.men.bris.ac.uk> Content-Type: text/plain; charset=iso-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2017-08/txt/msg00016.txt.bz2 Ciao Anton, Il 06/08/2017 14:23, Anton Shterenlikht ha scritto:> All of the above outputs are acceptable. > ERROR STOP initiates error termination. > The standard says, N2134, 5.3.7p3 [42:16-17]: > "When error termination on an image has been > initiated, the processor should initiate > error termination on other images as quickly > as possible." > > Basically, anything can happen. > If calling MPI_abort is deemed by the implementors > to be the quickest way, then this is acceptable. > If an image has initiated error termination, it's > data might or might not be accessible from other images. > If other images try to access it's data before they > realise that error termination was initiated, you > can segfaults or MPI errors or any other error, really. > None of this matters, because the aim of error termination > is to quit the execution on all images as fast as possible. > The way this is achieved does not matter. when this morning I saw "Program received signal SIGSEGV: Segmentation fault - invalid memory reference." in the example n. (1), I tried to figure out what was happening in my apps because, a few months ago, it did not occur.. and so I tried with the test case.. So a change between versions 5.x and 6.x of gfortran is causing this, likely because now 'error stop' is more standard conform. Really I consider this very misleading, maybe I have to replace the new "error stop" with the old 'stop' statement. Thanks for clarification. Ciao, Angelo.