public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tkoenig at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libfortran/30415] MINLOC, MAXLOC missing for integer kinds 1 and 2 Date: Thu, 18 Jan 2007 21:57:00 -0000 [thread overview] Message-ID: <20070118215706.17504.qmail@sourceware.org> (raw) In-Reply-To: <bug-30415-6318@http.gcc.gnu.org/bugzilla/> ------- Comment #4 from tkoenig at gcc dot gnu dot org 2007-01-18 21:57 ------- Subject: Bug 30415 Author: tkoenig Date: Thu Jan 18 21:56:53 2007 New Revision: 120932 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=120932 Log: 2007-01-18 Thomas Koenig <Thomas.Koenig@online.de> Backport from trunk PR libfortran/30415 * iresolve.c (gfc_resolve_maxloc): If the rank of the return array is nonzero and we process an integer array smaller than default kind, coerce the array to default integer. * iresolve.c (gfc_resolve_minloc): Likewise. 2007-01-18 Thomas Koenig <Thomas.Koenig@online.de> Backport from trunk PR libfortran/30415 * minmaxloc_integer_kinds_1.f90: New test. Added: branches/gcc-4_2-branch/gcc/testsuite/gfortran.dg/minmaxloc_integer_kinds_1.f90 Modified: branches/gcc-4_2-branch/gcc/fortran/ChangeLog branches/gcc-4_2-branch/gcc/fortran/iresolve.c branches/gcc-4_2-branch/gcc/testsuite/ChangeLog -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30415
next prev parent reply other threads:[~2007-01-18 21:57 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-01-09 8:34 [Bug libfortran/30415] New: " anlauf at gmx dot de 2007-01-09 20:46 ` [Bug libfortran/30415] " tkoenig at gcc dot gnu dot org 2007-01-09 21:30 ` tkoenig at gcc dot gnu dot org 2007-01-11 20:33 ` tkoenig at gcc dot gnu dot org 2007-01-18 21:57 ` tkoenig at gcc dot gnu dot org [this message] 2007-01-18 21:58 ` tkoenig 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=20070118215706.17504.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).