From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
 id 8CB023861872; Thu,  2 Jul 2020 15:53:22 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 8CB023861872
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
 s=default; t=1593705202;
 bh=epnzJT4x/NxRWvxCkRAPI8NZUFmCFawkY/htMKubtfs=;
 h=From:To:Subject:Date:In-Reply-To:References:From;
 b=E50sHOhRb3jlp3QJnryHPM5lws+Zv6whHD0D7ih1+Hk4bOx4/Nk8kGh+rm9bN6zdi
 IaqDNCYbGSRqh+ja6qGNDB/ylF9UUv+nANbZ9aqrDhQCT7zYzFOMiO3N7XxcXuK0c8
 H9QN5n5j0AYNdMpK3jF8tb/3va9bqzUqyj+kh3p8=
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/52279] Fortran translation issues
Date: Thu, 02 Jul 2020 15:53:22 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 4.7.0
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P5
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-52279-4-oA4688nFMt@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-52279-4@http.gcc.gnu.org/bugzilla/>
References: <bug-52279-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: gcc-bugs@gcc.gnu.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Gcc-bugs mailing list <gcc-bugs.gcc.gnu.org>
List-Unsubscribe: <http://gcc.gnu.org/mailman/options/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=unsubscribe>
List-Archive: <https://gcc.gnu.org/pipermail/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-request@gcc.gnu.org?subject=help>
List-Subscribe: <http://gcc.gnu.org/mailman/listinfo/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Jul 2020 15:53:22 -0000

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D52279

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jakub at gcc dot gnu.org

--- Comment #7 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
(In reply to kargl from comment #6)
> There is no -fno-allow-invalid-boz option.  The option is
> -fallow-invalid-boz.  fortan/lang.opt defines the options
> with the RejectNegative annotation.

Why is it RejectNegative?  Is there some other option that acts as it negat=
ive
option?  If it is just a standalone boolean option, it should have a negati=
ve,
so that if e.g. one uses -fallow-invalid-boz in $FFLAGS for most of files in
some project, but there is a specific one that shouldn't allow it, one can =
just
append -fno-allow-invalid-boz for it to cancel the earlier option.=