public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dfranke at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/35030] New: add type/kind information to pointer assignments Date: Wed, 30 Jan 2008 16:00:00 -0000 [thread overview] Message-ID: <bug-35030-13648@http.gcc.gnu.org/bugzilla/> (raw) As done for actual and formal arguments in functions/subroutines (e.g. PR34901), the error messages for pointer assignments could be improved: E,g, neighbours_neighbours => dummy_atom_kdtree_region_search(this%beads, at 1 Error: Different types in pointer assignment at (1) is correct but not extraordinarily helpful. Better: "Error: Different types in pointer assignment at (1); attempted to assign TYPE(...) to TYPE(...)." Reminder to self: see expr.c (gfc_check_pointer_assign). -- Summary: add type/kind information to pointer assignments Product: gcc Version: 4.3.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: dfranke at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35030
next reply other threads:[~2008-01-30 15:06 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-01-30 16:00 dfranke at gcc dot gnu dot org [this message] 2008-01-30 20:27 ` [Bug fortran/35030] " dfranke at gcc dot gnu dot org 2008-02-19 18:27 ` dfranke at gcc dot gnu dot org 2008-02-19 18:33 ` dfranke at gcc dot gnu dot 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-35030-13648@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: linkBe 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).