public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/113412] ATAN(Y,X) does not check arguments and generates wrong error message. Date: Tue, 16 Jan 2024 20:25:22 +0000 [thread overview] Message-ID: <bug-113412-4-37d7fEGBly@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113412-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113412 --- Comment #1 from kargl at gcc dot gnu.org --- Ugh. This seems to be by design. The error message Error: Too many arguments in call to ‘atan’ at (1) is queued by intrinsic.cc(sort_actual) and appears to take precedence over an error queued by check.cc(gfc_check_atan2). For a robust error message, if looks like we'll need to special case the one versus to argument atan(), atand(), and atanpi() cases intrinsic.cc(sort_actual). In pseudocode, change whoops: gfc_error ("Too many arguments in call to %qs at %L", name, where); return false; to whoops: if (name == "atan") check for two arguments and issue error else above gfc_error() return false;
next prev parent reply other threads:[~2024-01-16 20:25 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-16 2:13 [Bug fortran/113412] New: " kargl at gcc dot gnu.org 2024-01-16 2:13 ` [Bug fortran/113412] " kargl at gcc dot gnu.org 2024-01-16 20:25 ` kargl at gcc dot gnu.org [this message] 2024-01-16 20:44 ` kargl at gcc dot gnu.org 2024-01-17 0:46 ` kargl at gcc dot gnu.org 2024-04-02 20:20 ` anlauf at gcc dot gnu.org 2024-04-02 22:15 ` kargls at comcast dot net 2024-04-03 20:12 ` anlauf at gcc dot gnu.org 2024-04-04 5:03 ` kargls at comcast dot net
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-113412-4-37d7fEGBly@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: linkBe 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).