public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "Joost.VandeVondele at mat dot ethz.ch" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/61180] surprising -Wsurprising warning
Date: Tue, 13 May 2014 17:46:00 -0000	[thread overview]
Message-ID: <bug-61180-4-Oe33iqOAI6@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-61180-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61180

Joost VandeVondele <Joost.VandeVondele at mat dot ethz.ch> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |Joost.VandeVondele at mat dot ethz
                   |                            |.ch

--- Comment #2 from Joost VandeVondele <Joost.VandeVondele at mat dot ethz.ch> ---
(In reply to Dominique d'Humieres from comment #1)
> Why do you think the warnings are not needed?

I'm only suggesting that the warning is not needed for the first two
assignments. They are just correct, and clearly pointer assignment is not
intended (or possible in the first case).

The crash is for the 3rd case, where the warning is indeed correct (but it is
not documented that this check is done).


  parent reply	other threads:[~2014-05-13 17:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-13 16:36 [Bug fortran/61180] New: " Joost.VandeVondele at mat dot ethz.ch
2014-05-13 17:39 ` [Bug fortran/61180] " dominiq at lps dot ens.fr
2014-05-13 17:46 ` Joost.VandeVondele at mat dot ethz.ch [this message]
2014-05-15 14:09 ` 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-61180-4-Oe33iqOAI6@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).