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 A7D823858C35; Mon, 18 Mar 2024 18:53:06 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org A7D823858C35
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1710787986;
	bh=l961AtJgViw+cEL0+ZfAWJPTjfXutYNNr3cUK6sva9I=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=Rk9DJdoRiTP80qq6dkGQlBAIkdBlbFr4Oi0AfbhDnqeq+RtE5BzA+ZRRJUw6mPlVp
	 m5mDpaQu1+J31bFpbvYLmIo85smkgl7Jixgdy+TchEhoBz21tfyAE2V8VWXYQ5yMyI
	 mMwCefunReO3VAMU52sDhXJjQio8fsmfAX+lXICY=
From: "jvdelisle at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/80012] FIXME in diagnostic "%s procedure at %L is
 already declared as %s procedure" from symbol.c
Date: Mon, 18 Mar 2024 18:53:04 +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: 7.0
X-Bugzilla-Keywords: diagnostic, easyhack, FIXME
X-Bugzilla-Severity: trivial
X-Bugzilla-Who: jvdelisle at gcc dot gnu.org
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: cc
Message-ID: <bug-80012-4-uKUDj9OIUV@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-80012-4@http.gcc.gnu.org/bugzilla/>
References: <bug-80012-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=3D80012

Jerry DeLisle <jvdelisle at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jvdelisle at gcc dot gnu.o=
rg

--- Comment #5 from Jerry DeLisle <jvdelisle at gcc dot gnu.org> ---
I have not looked at this in detail. Generally, you can do conditional erro=
rs
depending on what -std=3Dfxxxx a user specifies at compile time. So theoret=
ically
you can do two different errors depending on these options.

Also look in the codes for examples of 'notify' or 'notification' to see wa=
ys
to do these things.

Another way is to build an error message with snprintf for example and use =
that
string in the error message.=