public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jvdelisle at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/36239] ICE: gfc_validate_kind(): Got bad kind Date: Fri, 16 May 2008 03:42:00 -0000 [thread overview] Message-ID: <20080516034207.18613.qmail@sourceware.org> (raw) In-Reply-To: <bug-36239-13404@http.gcc.gnu.org/bugzilla/> ------- Comment #3 from jvdelisle at gcc dot gnu dot org 2008-05-16 03:42 ------- Subject: Bug 36239 Author: jvdelisle Date: Fri May 16 03:41:17 2008 New Revision: 135408 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=135408 Log: 2008-05-15 Steven G. Kargl <kargls@comcast.net> * simplify.c (gfc_simplify_dble, gfc_simplify_float, simplify_bound, gfc_simplify_nearest, gfc_simplify_real): Plug possible memory leaks. (gfc_simplify_reshape): Plug possible memory leaks and dereferencing of NULL pointers. 2008-05-15 Steven G. Kargl <kargls@comcast.net> PR fortran/36239 * simplify.c (gfc_simplify_int, gfc_simplify_intconv): Replaced hand rolled integer conversion with gfc_int2int, gfc_real2int, and gfc_complex2int. (gfc_simplify_intconv): Renamed to simplify_intconv. 2008-05-15 Steven G. Kargl, <kargl@comcast.net> * gfortran.dg/and_or_xor.f90: New test * fortran/simplify.c (gfc_simplify_and, gfc_simplify_or, gfc_simplify_xor): Don't range check logical results. Modified: trunk/gcc/fortran/ChangeLog trunk/gcc/fortran/intrinsic.texi trunk/gcc/fortran/simplify.c -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36239
next prev parent reply other threads:[~2008-05-16 3:42 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-05-15 5:47 [Bug fortran/36239] New: " burnus at gcc dot gnu dot org 2008-05-15 17:44 ` [Bug fortran/36239] " kargl at gcc dot gnu dot org 2008-05-15 18:26 ` kargl at gcc dot gnu dot org 2008-05-16 3:42 ` jvdelisle at gcc dot gnu dot org [this message] 2008-05-16 3:43 ` jvdelisle at gcc dot gnu dot org 2008-12-28 4:17 ` pinskia 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=20080516034207.18613.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).