public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "thenlich at users dot sourceforge.net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libfortran/48785] BOZ editing of real numbers not working with -std=f2008 Date: Mon, 02 May 2011 14:11:00 -0000 [thread overview] Message-ID: <bug-48785-4-q14EG7VlsM@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-48785-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48785 --- Comment #6 from Thomas Henlich <thenlich at users dot sourceforge.net> 2011-05-02 14:10:22 UTC --- Can you elaborate on this? Previously we allowed the format with -std=gnu. Now we want to allow it with -std=gnu or -std=f2008. So we call require_type() only if neither of these options is set. That's why I changed the mask from GFC_STD_GNU to (GFC_STD_GNU | GFC_STD_F2008). And the values have different bits set, so the OR is not redundant: #define GFC_STD_F2008 (1<<7) /* New in F2008. */ #define GFC_STD_LEGACY (1<<6) /* Backward compatibility. */ #define GFC_STD_GNU (1<<5) /* GNU Fortran extension. */
next prev parent reply other threads:[~2011-05-02 14:11 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-04-27 6:27 [Bug libfortran/48785] New: " thenlich at users dot sourceforge.net 2011-04-27 7:03 ` [Bug libfortran/48785] " burnus at gcc dot gnu.org 2011-05-02 13:04 ` thenlich at users dot sourceforge.net 2011-05-02 13:08 ` jvdelisle at gcc dot gnu.org 2011-05-02 13:15 ` thenlich at users dot sourceforge.net 2011-05-02 13:45 ` burnus at gcc dot gnu.org 2011-05-02 14:11 ` thenlich at users dot sourceforge.net [this message] 2011-05-02 14:36 ` burnus at gcc dot gnu.org 2011-05-02 15:14 ` thenlich at users dot sourceforge.net 2013-01-02 20:03 ` jvdelisle at gcc dot gnu.org
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-48785-4-q14EG7VlsM@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).