public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "burnus at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/40588] Small bug in match_charkind_name Date: Mon, 13 Jul 2009 06:27:00 -0000 [thread overview] Message-ID: <20090713062653.3608.qmail@sourceware.org> (raw) In-Reply-To: <bug-40588-17820@http.gcc.gnu.org/bugzilla/> ------- Comment #2 from burnus at gcc dot gnu dot org 2009-07-13 06:26 ------- Subject: Bug 40588 Author: burnus Date: Mon Jul 13 06:26:38 2009 New Revision: 149545 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=149545 Log: 2009-07-12 Tobias Burnus <burnus@net-b.de> Philippe Marguinaud <philippe.marguinaud@meteo.fr> PR fortran/40588 * primary.c (match_charkind_name): Fix condition for $ matching. PR libfortran/22423 * libgfortran.h: Typedef the GFC_DTYPE_* enum. 2009-07-12 Tobias Burnus <burnus@net-b.de> PR libfortran/22423 * io/io.h (namelist_type): Use the proper enum for GFC_DTYPE_*. * intrinsics/iso_c_binding.c (c_f_pointer_u0): Make sure variable is initialized to silence warning. Modified: trunk/gcc/fortran/ChangeLog trunk/gcc/fortran/libgfortran.h trunk/gcc/fortran/primary.c trunk/libgfortran/ChangeLog trunk/libgfortran/intrinsics/iso_c_binding.c trunk/libgfortran/io/io.h -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40588
next prev parent reply other threads:[~2009-07-13 6:27 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-06-29 14:24 [Bug fortran/40588] New: " philippe dot marguinaud at meteo dot fr 2009-06-29 15:18 ` [Bug fortran/40588] " burnus at gcc dot gnu dot org 2009-07-05 9:14 ` fxcoudert at gcc dot gnu dot org 2009-07-13 6:27 ` burnus at gcc dot gnu dot org [this message] 2009-07-13 6:29 ` burnus 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=20090713062653.3608.qmail@sourceware.org \ --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).