public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Harald Anlauf <anlauf@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r13-5705] Fortran: prevent redundant integer division truncation warnings [PR108592] Date: Sun, 5 Feb 2023 21:53:52 +0000 (GMT) [thread overview] Message-ID: <20230205215352.665AC385843E@sourceware.org> (raw) https://gcc.gnu.org/g:d042f118798ae0648b45f97e63b0e5ab7c82c8ef commit r13-5705-gd042f118798ae0648b45f97e63b0e5ab7c82c8ef Author: Harald Anlauf <anlauf@gmx.de> Date: Mon Jan 30 22:46:43 2023 +0100 Fortran: prevent redundant integer division truncation warnings [PR108592] gcc/fortran/ChangeLog: PR fortran/108592 * arith.cc (gfc_arith_divide): Emit integer division truncation warnings using gfc_warning instead of gfc_warning_now to prevent redundant messages. gcc/testsuite/ChangeLog: PR fortran/108592 * gfortran.dg/pr108592.f90: New test. Diff: --- gcc/fortran/arith.cc | 2 +- gcc/testsuite/gfortran.dg/pr108592.f90 | 8 ++++++++ 2 files changed, 9 insertions(+), 1 deletion(-) diff --git a/gcc/fortran/arith.cc b/gcc/fortran/arith.cc index 6de6d21c73d..d0d1c0b03d2 100644 --- a/gcc/fortran/arith.cc +++ b/gcc/fortran/arith.cc @@ -778,7 +778,7 @@ gfc_arith_divide (gfc_expr *op1, gfc_expr *op2, gfc_expr **resultp) { char *p; p = mpz_get_str (NULL, 10, result->value.integer); - gfc_warning_now (OPT_Winteger_division, "Integer division " + gfc_warning (OPT_Winteger_division, "Integer division " "truncated to constant %qs at %L", p, &op1->where); free (p); diff --git a/gcc/testsuite/gfortran.dg/pr108592.f90 b/gcc/testsuite/gfortran.dg/pr108592.f90 new file mode 100644 index 00000000000..224b1d8d1fc --- /dev/null +++ b/gcc/testsuite/gfortran.dg/pr108592.f90 @@ -0,0 +1,8 @@ +! { dg-do compile } +! { dg-options "-Winteger-division" } +! PR fortran/108592 - warn only once for truncation of integer division + +program foo + if (8 < (20/9)) stop 1 ! { dg-bogus "Integer division.*Integer division" } +! { dg-message "Integer division truncated" "" { target *-*-* } .-1 } +end program
reply other threads:[~2023-02-05 21:53 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20230205215352.665AC385843E@sourceware.org \ --to=anlauf@gcc.gnu.org \ --cc=gcc-cvs@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).