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 5C7073858D20; Thu, 16 May 2024 17:06:29 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 5C7073858D20
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1715879190;
	bh=tXUo6qiXWVYxgHFA5JskiyrgyPAHO5xvfPduRanjM0M=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=ayZ8ZrlnCF9RJ8w9+C0GTxzUcqGRbf7ePzF6ReX+0qRkR1NVe8Z6UnAj7HBXRaxyv
	 93su/PtU3xAXrbzzclTCC0YaFrK/gSHAqxxKjBqCKKGprrPPe33sl8pjxArivPQPK2
	 emEXmlloxPQjqNOtjBEi9q0F+yLgSQpXPgk2OMYA=
From: "anlauf at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/115107] f951: internal compiler error: Segmentation
 fault 0xcf878f crash_signal toplev.cc:314
Date: Thu, 16 May 2024 17:06:29 +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: 13.2.0
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: anlauf at gcc dot gnu.org
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-115107-4-vm2HdfikCQ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-115107-4@http.gcc.gnu.org/bugzilla/>
References: <bug-115107-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
List-Id: <gcc-bugs.sourceware.org>

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

--- Comment #7 from anlauf at gcc dot gnu.org ---
(In reply to Natalie Perlin from comment #6)
> (In reply to anlauf from comment #3)
> > The traceback is essentially identical to that in pr114467.
> >=20
> > Can you please try the 14-release like the other reporter, or the upcom=
ing
> > 13.3 release next week?
>=20
> Thank you for the comment. Yes, this indeed looks similar to pr114467.=20
> I did try to use gnu/14.1.0 + openmpi/4.1.6, but was not able to build a
> software stack needed for building the model that produced the original
> error.=20
>=20
> The issue with the gnu/14.1.0 compiler was that it produced an error where
> the gnu/13.2.0 had only a warning. The error with the gnu/14.1.0 compiler
> was as shown below, and is related to -Wimplicit-function-declaration.=20
> Could it be that a certain compiler flag helps to avoid such an error?..
>=20
>=20
> And yes, I'd gladly try the upcoming v13.3 release next week!
>=20
>=20
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D
>  /scratch2/NCEPDEV/stmp1/role.epic/spack-stack/spack-stack-1.6.0_gnu14/sp=
ack/
> lib/spack/env/gcc/gcc -DHAVE_CONFIG_H -I. -I.
> -I../../../src/libjasper/include/jasper -I../../../src/libjasper/include =
-g
> -O2 -MT jas_getopt.lo -MD -MP -MF .deps/jas_getopt.Tpo -c jas_getopt.c -o
> jas_getopt.o
> jas_getopt.c: In function 'jas_getopt':
> jas_getopt.c:129:49: error: implicit declaration of function 'jas_eprintf=
';
> did you mean 'vsnprintf'? [-Wimplicit-function-declaration]
>   129 |                                                 jas_eprintf("unkn=
own
> long option %s\n", s);
>       |                                                 ^~~~~~~~~~~
>       |                                                 vsnprintf
> make[4]: *** [Makefile:349: jas_getopt.lo] Error 1
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D

This looks like the header file jas_debug.h is not found or not included.
(On my Linux system it is /usr/include/jasper/jas_debug.h).=