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/98558] Scalar character parameter does not print warning if actual length >1
Date: Wed, 06 Jan 2021 17:46:27 +0000	[thread overview]
Message-ID: <bug-98558-4-T2C3j2PHVw@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98558-4@http.gcc.gnu.org/bugzilla/>

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

kargl at gcc dot gnu.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |WAITING
   Last reconfirmed|                            |2021-01-06
     Ever confirmed|0                           |1
                 CC|                            |kargl at gcc dot gnu.org

--- Comment #1 from kargl at gcc dot gnu.org ---
What options are you using?

% gfcg -c -Wall b.f90
b.f90:4:40:

    4 |       character, parameter :: b = 'bbbbb'  ! NO -> No warnings printed!
      |                                        1
Warning: CHARACTER expression at (1) is being truncated (5/1)
[-Wcharacter-truncation]
b.f90:5:40:

    5 |       character(len=1), parameter :: c = 'ccccc'  ! NO -> No warnings
printed!
      |                                        1
Warning: CHARACTER expression at (1) is being truncated (5/1)
[-Wcharacter-truncation]

  reply	other threads:[~2021-01-06 17:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-06  9:31 [Bug fortran/98558] New: " federico.perini at gmail dot com
2021-01-06 17:46 ` kargl at gcc dot gnu.org [this message]
2021-01-07  8:32 ` [Bug fortran/98558] " federico.perini at gmail dot com

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-98558-4-T2C3j2PHVw@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).