public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <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:36:00 -0000	[thread overview]
Message-ID: <bug-48785-4-5duGS7Lnp5@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 #7 from Tobias Burnus <burnus at gcc dot gnu.org> 2011-05-02 14:31:56 UTC ---
(In reply to comment #6)
> Can you elaborate on this?
> That's why I changed the mask from GFC_STD_GNU to (GFC_STD_GNU |
> GFC_STD_F2008).

First, the code is/should be also allowed for -std=legacy (GFC_STD_LEGACY).

Secondly, the point is not that GFC_STD_GNU and GFC_STD_F2008 are same (they
obviously aren't), but that

having      (compile_options.allow_std | GFC_STD_F2008) != 0
 => implies (compile_options.allow_std | GFC_STD_GNU) != 0

which is a property of "allow_std". See gcc/fortran/options.c:

    case OPT_std_f2003:
      gfc_option.allow_std = GFC_STD_F95_OBS | GFC_STD_F77 
    | GFC_STD_F2003 | GFC_STD_F95 | GFC_STD_F2008_OBS;
    case OPT_std_f2008:
      gfc_option.allow_std = GFC_STD_F95_OBS | GFC_STD_F77 
    | GFC_STD_F2003 | GFC_STD_F95 | GFC_STD_F2008 | GFC_STD_F2008_OBS;
    case OPT_std_gnu:
      set_default_std_flags ();
      break;


  parent reply	other threads:[~2011-05-02 14:36 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
2011-05-02 14:36 ` burnus at gcc dot gnu.org [this message]
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-5duGS7Lnp5@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).