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/48720] quad precision literals do not work
Date: Wed, 04 May 2011 19:26:00 -0000	[thread overview]
Message-ID: <bug-48720-4-vl6rWd5P3p@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-48720-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48720

--- Comment #10 from kargl at gcc dot gnu.org 2011-05-04 19:18:04 UTC ---
Author: kargl
Date: Wed May  4 19:18:01 2011
New Revision: 173392

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=173392
Log:
2011-05-04  Steven G. Kargl  <kargl@gcc.gnu.org>

        PR fortran/48720
        * gfortran.texi: Document the 'Q' exponent-letter extension.
        * invoke.texi: Document -Wreal-q-constant.
        * lang.opt: Add -Wreal-q-constant option.
        * gfortran.h: Add warn_real_q_constant to option struct.
        * primary.c (match_real_constant):  Use it.  Accept 'Q' as
        exponent-letter for REAL(16) real-literal-constant with a
        fallback to REAL(10) or error if REAL(10) is not available.
        * options.c (gfc_init_options, set_Wall) Set it.
        (gfc_handle_option): Handle new option.

Modified:
    branches/gcc-4_6-branch/gcc/fortran/ChangeLog
    branches/gcc-4_6-branch/gcc/fortran/gfortran.h
    branches/gcc-4_6-branch/gcc/fortran/gfortran.texi
    branches/gcc-4_6-branch/gcc/fortran/invoke.texi
    branches/gcc-4_6-branch/gcc/fortran/lang.opt
    branches/gcc-4_6-branch/gcc/fortran/options.c
    branches/gcc-4_6-branch/gcc/fortran/primary.c


      parent reply	other threads:[~2011-05-04 19:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-21 22:31 [Bug fortran/48720] New: " sliwa at blue dot cft.edu.pl
2011-04-21 22:33 ` [Bug fortran/48720] " sliwa at blue dot cft.edu.pl
2011-04-22  2:22 ` jvdelisle at gcc dot gnu.org
2011-04-22  4:08 ` kargl at gcc dot gnu.org
2011-04-22 12:47 ` jvdelisle at frontier dot com
2011-04-22 15:01 ` sgk at troutmask dot apl.washington.edu
2011-04-22 15:16 ` sgk at troutmask dot apl.washington.edu
2011-04-25 18:45 ` kargl at gcc dot gnu.org
2011-05-03  1:25 ` kargl at gcc dot gnu.org
2011-05-03  1:34 ` kargl at gcc dot gnu.org
2011-05-04 19:20 ` kargl at gcc dot gnu.org
2011-05-04 19:26 ` kargl at gcc dot gnu.org [this message]

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-48720-4-vl6rWd5P3p@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).