public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "fxcoudert at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libfortran/47894] Documentation text for VERIFY intrinsic function is wrong. Date: Mon, 28 Feb 2011 08:55:00 -0000 [thread overview] Message-ID: <bug-47894-4-fGHqRDund1@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-47894-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47894 --- Comment #4 from Francois-Xavier Coudert <fxcoudert at gcc dot gnu.org> 2011-02-28 08:16:24 UTC --- Author: fxcoudert Date: Mon Feb 28 08:16:21 2011 New Revision: 170557 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=170557 Log: PR fortran/47894 * intrinsic.texi: Fix doc of the VERIFY intrinsic. Modified: trunk/gcc/fortran/ChangeLog trunk/gcc/fortran/intrinsic.texi
next prev parent reply other threads:[~2011-02-28 8:16 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-02-25 12:51 [Bug libfortran/47894] New: " thenlich at users dot sourceforge.net 2011-02-26 18:24 ` [Bug libfortran/47894] " fxcoudert at gcc dot gnu.org 2011-02-26 18:32 ` fxcoudert at gcc dot gnu.org 2011-02-28 8:16 ` thenlich at users dot sourceforge.net 2011-02-28 8:55 ` fxcoudert at gcc dot gnu.org [this message] 2011-02-28 8:56 ` fxcoudert 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-47894-4-fGHqRDund1@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).