public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tobias dot burnus at physik dot fu-berlin dot de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/29471] New: Warn with -std=f95/f2003 when BOZ is used at invalid places Date: Sat, 14 Oct 2006 19:20:00 -0000 [thread overview] Message-ID: <bug-29471-1719@http.gcc.gnu.org/bugzilla/> (raw) gfortran allows everywhere to use a BOZ. However, there are constrains in Fortran 95 and 2003 on where to use them. - Fortran 95: Only in DATA and only integer - Fortran 2003: Only in DATA or as argument of INT, REAL, DBLE, CMPLX Expected: An ERROR (or WARNING) is shown, when -std=f95/f2003 is used. Fortran 95: "R407 boz-literal-constant [...] Constraint: A boz-literal-constant may appear only in a DATA statement.[...] If a data-statement-constant is a boz-literal-constant, the corresponding object shall be of type integer." Fortran 2003: "C410 (R411) A boz-literal-constant shall appear only as a data-stmt-constant in a DATA statement, as the actual argument associated with the dummy argument A of the numeric intrinsic functions DBLE, REAL or INT, or as the actual argument associated with the X or Y dummy argument of the intrinsic function CMPLX." -- Summary: Warn with -std=f95/f2003 when BOZ is used at invalid places Product: gcc Version: unknown Status: UNCONFIRMED Severity: enhancement Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: tobias dot burnus at physik dot fu-berlin dot de http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29471
next reply other threads:[~2006-10-14 19:20 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-10-14 19:20 tobias dot burnus at physik dot fu-berlin dot de [this message] 2006-10-16 13:34 ` [Bug fortran/29471] " tobias dot burnus at physik dot fu-berlin dot de 2006-10-16 16:51 ` kargl at gcc dot gnu dot org 2006-10-16 17:12 ` tobias dot burnus at physik dot fu-berlin dot de 2006-10-16 17:23 ` kargl at gcc dot gnu dot org 2007-03-16 3:46 ` jkrahn at nc dot rr dot com 2007-03-16 3:54 ` jkrahn at nc dot rr dot com 2007-03-16 4:07 ` sgk at troutmask dot apl dot washington dot edu 2007-03-16 4:09 ` sgk at troutmask dot apl dot washington dot edu 2007-03-16 9:45 ` burnus at gcc dot gnu dot org 2007-08-12 20:10 ` fxcoudert at gcc dot gnu dot org 2007-12-08 21:47 ` burnus at gcc dot gnu dot org 2007-12-08 22:08 ` burnus at gcc dot gnu dot org 2007-12-08 22:10 ` burnus at gcc dot gnu dot org 2007-12-11 19:40 ` jkrahn at nc dot rr dot com 2007-12-11 23:15 ` burnus at gcc dot gnu dot org 2007-12-12 1:04 ` jkrahn at nc dot rr 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-29471-1719@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).