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 fortran/45824] New: Update expr.c's check_inquiry for C_SIZEOF, compiler_version/_options, etc.
Date: Tue, 28 Sep 2010 23:34:00 -0000	[thread overview]
Message-ID: <bug-45824-4@http.gcc.gnu.org/bugzilla/> (raw)

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

           Summary: Update expr.c's check_inquiry for C_SIZEOF,
                    compiler_version/_options, etc.
           Product: gcc
           Version: 4.6.0
            Status: UNCONFIRMED
          Keywords: rejects-valid
          Severity: normal
          Priority: P3
         Component: fortran
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: burnus@gcc.gnu.org
                CC: dfranke@gcc.gnu.org


Follow up to PR 40568 - but also to PR 40569. The PR of the former - I might
not have copied all remaining tasks.


ISO_C_BINDING's C_SIZEOF but also ISO_FORTRAN_ENV's
compiler_options/compiler_version as listed under Fortran 2008's "7.1.11 Speci
cation expression" as "speci\fcation inquiry".

If I understood this part of the previous PR correctly, it means that expr.c's
check_inquiry needs to be updated.

I think except for some F95 vs. newer checks, most items should be handled via
flags in add_function/subroutine of intrinsic.c as one easily forgets to update
check_inquiry.


             reply	other threads:[~2010-09-28 19:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-28 23:34 burnus at gcc dot gnu.org [this message]
2013-03-24 23:15 ` [Bug fortran/45824] " burnus at gcc dot gnu.org
2013-03-25 15:54 ` burnus at gcc dot gnu.org
2013-06-20 22:30 ` dominiq at lps dot ens.fr
2013-12-14 20:25 ` dominiq at lps dot ens.fr

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