public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kargls at comcast dot net" <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, 02 Apr 2024 22:15:48 +0000	[thread overview]
Message-ID: <bug-113412-4-NZ1EUPDZ3p@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 #5 from kargls at comcast dot net ---
(In reply to anlauf from comment #4)
> (In reply to kargls from comment #3)
> > Created attachment 57109 [details]
> > patch
> > 
> > The attached patch has been regtested.  There were no regression.
> 
> Steve,
> 
> I just tried your patch.  While it fixes comment#0, it misses:
> 
>   print *, atan(1.d0,1.0)
> end
> 

Ugh.  I forgot literal constants don't have symtrees or names. :(


    gfc_error ("%qs argument of %qs intrinsic at %L must be the same type "
                "and kind as %qs", (*ap)->next->expr->symtree->name, name,
                &(*ap)->next->expr->where, (*ap)->expr->symtree->name);


The pointers to expr->symtree is NULL.  This new patch catches your example.

diff --git a/gcc/fortran/intrinsic.cc b/gcc/fortran/intrinsic.cc
index c35f2bdd183..a8a92874583 100644
--- a/gcc/fortran/intrinsic.cc
+++ b/gcc/fortran/intrinsic.cc
@@ -4371,7 +4371,19 @@ sort_actual (const char *name, gfc_actual_arglist **ap,
     goto do_sort;

 whoops:
-  gfc_error ("Too many arguments in call to %qs at %L", name, where);
+  if ((gfc_option.allow_std & GFC_STD_F2008) != 0
+      && strcmp(name, "atan") == 0)
+    {
+      if ((*ap)->expr->symtree == NULL || (*ap)->next->expr->symtree == NULL)
+       gfc_error ("Arguments of %qs intrinsic at %L must have the same "
+                  "type and kind", name, &(*ap)->expr->where);
+      else
+       gfc_error ("%qs argument of %qs intrinsic at %L must be the same "
+                  "type and kind as %qs", (*ap)->next->expr->symtree->name,
+                  name, &(*ap)->next->expr->where,
(*ap)->expr->symtree->name);
+    }
+  else
+    gfc_error ("Too many arguments in call to %qs at %L", name, where);
   return false;

 keywords:

  parent reply	other threads:[~2024-04-02 22:15 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
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 [this message]
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-NZ1EUPDZ3p@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).