From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-return-198770-listarch-gcc=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 68674 invoked by alias); 8 Apr 2019 12:45:32 -0000
Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc/>
List-Post: <mailto:gcc@gcc.gnu.org>
List-Help: <http://gcc.gnu.org/ml/>
Sender: gcc-owner@gcc.gnu.org
Received: (qmail 68662 invoked by uid 89); 8 Apr 2019 12:45:32 -0000
Authentication-Results: sourceware.org; auth=none
X-Spam-SWARE-Status: No, score=-1.8 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.1 spammy=HX-Languages-Length:688, our
X-HELO: mail-lj1-f169.google.com
Received: from mail-lj1-f169.google.com (HELO mail-lj1-f169.google.com) (209.85.208.169) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Mon, 08 Apr 2019 12:45:31 +0000
Received: by mail-lj1-f169.google.com with SMTP id j89so11135196ljb.1        for <gcc@gcc.gnu.org>; Mon, 08 Apr 2019 05:45:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;        d=gmail.com; s=20161025;        h=mime-version:references:in-reply-to:from:date:message-id:subject:to         :cc;        bh=G3iDnfbTzG++QreNZSYP1CAj1TT05XTIS9gW30/JPIs=;        b=TK9LPf4ZvEPUWSDEeSEnCXbsYDxSVFnkwwMx2FKb1Y8qCwNOWqKl/BeSPupmfGqAG0         FiR/fupUWBEfDL0tTdvQuKThSx0xuIvpxvZ10BfS7wdRSEU76Mt7wTAH6g8iy6aI4y5j         9IQoWDL+OhmLniA0o2Anfu8NBY08x+fDYdB0h4/yk2APyxNdAe9cxPBwdCf02J6n/jNS         VUSd3DS9MsjDFTnkTw3O6H+691IrgM5CJyrXdORGnlKL2mxoSWuFGkdBvmc8cjmja9u+         uQv6wta4aQnNkdm89EPeFaH3PEbESjKHzu0Olq4FfJBH5NzpnoU+1JXeBf8uPwOO37E/         Lt2g==
MIME-Version: 1.0
References: <20190405112727.2219c936@jozef-kubuntu> <alpine.LSU.2.21.1904051556120.20370@wotan.suse.de> <CAFiYyc3Jk9ZDQGgBSGf+=j1qmzx7E1W8bbaX+Cpei6D9k6EzPQ@mail.gmail.com> <alpine.LSU.2.21.1904081228230.20370@wotan.suse.de>
In-Reply-To: <alpine.LSU.2.21.1904081228230.20370@wotan.suse.de>
From: Richard Biener <richard.guenther@gmail.com>
Date: Mon, 08 Apr 2019 12:45:00 -0000
Message-ID: <CAFiYyc2+pbnhv-6HgXHZTPkQOWeMNLH8h7g2uinZpKHAM158Rw@mail.gmail.com>
Subject: Re: non-volatile automatic variables in setjmp tests
To: Michael Matz <matz@suse.de>
Cc: Jozef Lawrynowicz <jozefl.gcc@gmail.com>, GCC Development <gcc@gcc.gnu.org>
Content-Type: text/plain; charset="UTF-8"
X-IsSubscribed: yes
X-SW-Source: 2019-04/txt/msg00115.txt.bz2

On Mon, Apr 8, 2019 at 2:31 PM Michael Matz <matz@suse.de> wrote:
>
> Hi,
>
> On Mon, 8 Apr 2019, Richard Biener wrote:
>
> > Not sure if in this case we run into an RTL optimization that breaks things
> > (PRE / scheduling / invariant motion are candidates).
>
> That's true, what Josef sees might point to a genuine bug in the
> middle-end observed only on msp430; but we do want to make this situation
> work generally, as required by ISO C, not like how it's spelled in our
> manual.

Yes, and there's at least one existing bug, PR57067 for which it was
observed the scheduler genrates wrong-code.

Richard.

>
> Ciao,
> Michael.