public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sgk at troutmask dot apl.washington.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/112873] F2023 degree trig functions
Date: Thu, 14 Dec 2023 20:04:33 +0000	[thread overview]
Message-ID: <bug-112873-4-rOlUMLpR0e@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112873-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #25 from Steve Kargl <sgk at troutmask dot apl.washington.edu> ---
On Thu, Dec 14, 2023 at 07:48:08PM +0000, anlauf at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112873
> 
> --- Comment #24 from anlauf at gcc dot gnu.org ---
> (In reply to Jerry DeLisle from comment #23)
> > I am going to suggest the following. The wording was confusing around the
> > functionality of the option vs the intrinsics. Hope this is OK?
> > 
> > @opindex @code{fdec-math}
> > @item -fdec-math
> > Obsolete flag.  The purpose of this option was to
> > enable legacy math intrinsics such as COTAN and degree-valued trigonometric
> > functions (e.g. TAND, ATAND, etc...) for compatibility with older code. This
> > option is no longer operable. The trigonometric functions are now either 
> > part of Fortran 2023 or GNU extensions.
> 
> I am not a native speaker, so this is certainly better than what I wrote.
> 

Your English is much better than my non-existent German. ;-)

The above is fine for the -fdec-math option.  However, we'll need
to audit the description of each function to cleanup the non-support
for complex.  For example, ASIND has

_Arguments_:
    X     The type shall be either ‘REAL’ and a magnitude
          that is less than or equal to one - or be ‘COMPLEX’.

_Return value_:
     The return value is of the same type and kind as X.  The real part
     of the result is in degrees and lies in the range -90 \leq \Re
     \asin(x) \leq 90.

These should likely read

_Arguments_:
    X     The type shall be ‘REAL’.  The  magnitude of X should be
          less than or equal to one.

_Return value_:
     The return value is of the same type and kind as X.  The 
     result is in degrees and lies in the range -90 \leq \Re
     \asin(x) \leq 90.

  parent reply	other threads:[~2023-12-14 20:04 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-05 23:16 [Bug fortran/112873] New: " kargl at gcc dot gnu.org
2023-12-05 23:18 ` [Bug fortran/112873] " kargl at gcc dot gnu.org
2023-12-05 23:18 ` kargl at gcc dot gnu.org
2023-12-06 20:56 ` anlauf at gcc dot gnu.org
2023-12-06 21:17 ` sgk at troutmask dot apl.washington.edu
2023-12-06 21:58 ` anlauf at gcc dot gnu.org
2023-12-07 18:26 ` sgk at troutmask dot apl.washington.edu
2023-12-07 19:59 ` anlauf at gcc dot gnu.org
2023-12-07 20:42 ` sgk at troutmask dot apl.washington.edu
2023-12-09  1:32 ` kargl at gcc dot gnu.org
2023-12-09  1:33 ` kargl at gcc dot gnu.org
2023-12-10 21:45 ` anlauf at gcc dot gnu.org
2023-12-11  2:46 ` sgk at troutmask dot apl.washington.edu
2023-12-11 19:34 ` anlauf at gcc dot gnu.org
2023-12-11 19:53 ` jvdelisle at gcc dot gnu.org
2023-12-11 20:04 ` anlauf at gcc dot gnu.org
2023-12-11 21:00 ` sgk at troutmask dot apl.washington.edu
2023-12-13 17:36 ` jvdelisle at gcc dot gnu.org
2023-12-13 18:43 ` sgk at troutmask dot apl.washington.edu
2023-12-14 17:03 ` jvdelisle at gcc dot gnu.org
2023-12-14 17:15 ` sgk at troutmask dot apl.washington.edu
2023-12-14 17:42 ` anlauf at gcc dot gnu.org
2023-12-14 18:37 ` cvs-commit at gcc dot gnu.org
2023-12-14 19:11 ` jvdelisle at gcc dot gnu.org
2023-12-14 19:31 ` jvdelisle at gcc dot gnu.org
2023-12-14 19:48 ` anlauf at gcc dot gnu.org
2023-12-14 20:04 ` sgk at troutmask dot apl.washington.edu [this message]
2023-12-14 20:16 ` jvdelisle at gcc dot gnu.org
2023-12-14 20:35 ` jvdelisle at gcc dot gnu.org
2023-12-14 20:44 ` sgk at troutmask dot apl.washington.edu
2023-12-14 21:46 ` jvdelisle at gcc dot gnu.org
2023-12-14 22:09 ` anlauf at gcc dot gnu.org
2023-12-15  3:04 ` jvdelisle at gcc dot gnu.org
2023-12-15 21:11 ` jvdelisle at gcc dot gnu.org
2023-12-15 21:41 ` anlauf at gcc dot gnu.org
2023-12-16  0:44 ` jvdelisle at gcc dot gnu.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-112873-4-rOlUMLpR0e@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).