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 AC6263858D38; Wed, 27 Dec 2023 10:20:54 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org AC6263858D38
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1703672454;
	bh=W6NnrgXBl8A2EeV3wIkxRlpvfYq6wJGX9xGOsFnr14U=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=YnZO9CLJDbhb1t1SfeVTYrrfG2tOhdE6Ke/3+ENHW4Q9SLhkD1uteewWO+chL0a2e
	 hUSMcBBHcuNKhW/ttQtLcNL5uAZ7Sjwjlv0xn8BoM6RLBaJ0vJUYT+ZwNzhPE44jxi
	 ZlCNdaOfenwAiUYq/0ItmBwbNGM5yUCXGz6ufkh4=
From: "mikael at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/113152] Fortran 2023 half-cycle trigonometric functions
Date: Wed, 27 Dec 2023 10:20:53 +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.0
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mikael at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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: cc
Message-ID: <bug-113152-4-XWNyYEDhMe@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-113152-4@http.gcc.gnu.org/bugzilla/>
References: <bug-113152-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=3D113152

Mikael Morin <mikael at gcc dot gnu.org> changed:

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

--- Comment #5 from Mikael Morin <mikael at gcc dot gnu.org> ---
(In reply to kargl from comment #0)
>
> 4) I don't use git.  I tried to do 'git add libgfortran/intrinsics/trigpi=
\*'
>    followed by 'git commit libgfortran/intrinsics/trigpi\*', and then=20
>    finally 'git diff > z_halfcycle.diff'.  This does not generate one=20
>    unified diff file.  Sigh.  I'll attach the new files along with the
>    mangled diff.

With git you need to add all the files, not only the new ones (you can use =
git
add --update to add the existing files).
Then the patch can be generated (if you don't commit) with git diff --staged

If you commit, you need to add an argument to git diff to tell him a refere=
nce
to compare against, namely origin/master (remote master), master (local
master), HEAD^ (last commit before the tip of the branch), etc.  The default
reference if omitted is the tip of the branch, what you have just committed=
, so
the diff is empty.=