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/50570] [4.6/4.7 Regression] Incorrect error for assignment to intent(in) pointer
Date: Fri, 30 Sep 2011 07:00:00 -0000	[thread overview]
Message-ID: <bug-50570-4-sCEtmEkKxp@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-50570-4@http.gcc.gnu.org/bugzilla/>

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

Tobias Burnus <burnus at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
           Keywords|                            |rejects-valid
   Last reconfirmed|                            |2011-09-30
                 CC|                            |burnus at gcc dot gnu.org,
                   |                            |domob at gcc dot gnu.org
     Ever Confirmed|0                           |1
            Summary|Incorrect error for         |[4.6/4.7 Regression]
                   |assignment to intent(in)    |Incorrect error for
                   |pointer                     |assignment to intent(in)
                   |                            |pointer
   Target Milestone|---                         |4.6.2

--- Comment #1 from Tobias Burnus <burnus at gcc dot gnu.org> 2011-09-30 06:25:40 UTC ---
Working: 2010-09-09-r164046
Failing: 2010-09-28-r164677

Possible culprit:

r164550 | domob | 2010-09-23 10:37:54 +0200
http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=164550

2010-09-23  Daniel Kraft  <d@domob.eu>

        PR fortran/38936
        PR fortran/44044
        PR fortran/45474

        * expr.c (gfc_check_assign): Remove INTENT(IN) check here.
        (gfc_check_pointer_assign): Ditto (and other checks removed).
        (gfc_check_vardef_context): New method.


In expr.c's gfc_check_vardef_context, the problem is that for

4547          sym = e->value.function.esym ? e->value.function.esym :
e->symtree->n.sym;
4550      attr = gfc_expr_attr (e);

(gdb) p sym->attr.pointer
$3 = 1
(gdb) p attr.pointer
$1 = 0

Here, gfc_expr_attr() takes the array reference into account such that
"dummy(1)" is not pointer ...


  reply	other threads:[~2011-09-30  6:26 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-29 19:28 [Bug fortran/50570] New: " longb at cray dot com
2011-09-30  7:00 ` burnus at gcc dot gnu.org [this message]
2011-10-03 10:15 ` [Bug fortran/50570] [4.6/4.7 Regression] " msteghofer at cistib dot upf.edu
2011-10-03 10:17 ` msteghofer at cistib dot upf.edu
2011-10-09 20:32 ` janus at gcc dot gnu.org
2011-10-09 20:40 ` burnus at gcc dot gnu.org
2011-10-09 21:15 ` janus at gcc dot gnu.org
2011-10-09 23:08 ` janus at gcc dot gnu.org
2011-10-09 23:28 ` janus at gcc dot gnu.org
2011-10-10  6:58 ` burnus at gcc dot gnu.org
2011-10-10  9:45 ` msteghofer at cistib dot upf.edu
2011-10-10 11:48 ` janus at gcc dot gnu.org
2011-10-10 13:25 ` msteghofer at cistib dot upf.edu
2011-10-10 15:17 ` rguenth at gcc dot gnu.org
2011-10-14 17:59 ` janus at gcc dot gnu.org
2011-10-15 13:31 ` janus at gcc dot gnu.org
2011-10-15 13:32 ` janus 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-50570-4-sCEtmEkKxp@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).