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 C4A1B3850417; Thu,  3 Sep 2020 14:40:06 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org C4A1B3850417
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
 s=default; t=1599144006;
 bh=9HhKLKU6Nh15gvyDEDX+UKHxm3SWkR8Hz5i8uyn4Huw=;
 h=From:To:Subject:Date:In-Reply-To:References:From;
 b=xFClcCSISR+s9PCpQgBMRiCNW/JeYYIT9BBreaMhs1iBzUOFgxiL2gh2g9MZ4LNgi
 eFe9fOSrJAOyQmDslwioH1aVr57+DVwJQ9T//ZpH5NzOEZA/Z2MuFLpOYELH4r784m
 W4cJoFoBaVzRMOZGzZ1kFVcBbqjEcfIHtHd39o5k=
From: "sgk at troutmask dot apl.washington.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/96890] Wrong answer with intrinsic IALL
Date: Thu, 03 Sep 2020 14:40:06 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libfortran
X-Bugzilla-Version: 10.1.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: sgk at troutmask dot apl.washington.edu
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-96890-4-A9fpz0R8ut@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-96890-4@http.gcc.gnu.org/bugzilla/>
References: <bug-96890-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: <https://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: <https://gcc.gnu.org/mailman/listinfo/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Sep 2020 14:40:06 -0000

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

--- Comment #4 from Steve Kargl <sgk at troutmask dot apl.washington.edu> -=
--
On Thu, Sep 03, 2020 at 02:32:32PM +0000, anlauf at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D96890
>=20
> --- Comment #3 from anlauf at gcc dot gnu.org ---
> (In reply to kargl from comment #2)
> > At one point, you did it by using --maintainer-mode with configure.
> > With the move to git and other changes, I don't know if this has
> > changed.
>=20
> Well, --enable-maintainer-mode exists, but then I hit for libgomp:
>=20

Yes, that's the option.

> WARNING: 'aclocal-1.16' is missing on your system.
>=20
> % aclocal --version
> aclocal (GNU automake) 1.15.1

Yep. This is a pain of --enable-maintainer-mode, it=20
runs the autotools over the src hierarchy.  There is
supposedly another way to regenerate the libgfortran
source from the m4 files, but I cannot remember it.

>=20
> Giving up for someone else to take it up.
>=20

Ping Thomas.  I recall seeing that he recently was
asking about --enable-maintainer-mode in a git=20
world.=