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/30512] [4.2, 4.1 only] MAXVAL() incorrect for zero-size int arrays, and for -HUGE-1 maximum values. Date: Fri, 16 Feb 2007 14:16:00 -0000 [thread overview] Message-ID: <20070216141551.7252.qmail@sourceware.org> (raw) In-Reply-To: <bug-30512-13350@http.gcc.gnu.org/bugzilla/> ------- Comment #12 from burnus at gcc dot gnu dot org 2007-02-16 14:15 ------- Subject: Bug 30512 Author: burnus Date: Fri Feb 16 14:15:36 2007 New Revision: 122043 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=122043 Log: fortran/ 2007-02-16 Tobias Burnus <burnus@net-b.de> PR fortran/30512 * trans-intrinsic.c (gfc_conv_intrinsic_minmaxloc, gfc_conv_intrinsic_minmaxval): Use HUGE-1 for most negative integer. testsuite/ 2007-02-16 Tobias Burnus <burnus@net-b.de> PR fortran/30512 * gfortran.dg/maxlocval_1.f90: New test. libgfortran/ 2007-02-16 Thomas Koenig <Thomas.Koenig@online.de> Tobias Burnus <burnus@net-b.de> PR fortran/30512 * m4/iparm.m4: Use HUGE-1 for most negative integer. * generated/maxloc1_8_i4.c: Regenerate. * generated/maxloc0_8_i8.c: Regenerate. * generated/maxloc1_16_i4.c: Regenerate. * generated/maxloc0_16_i8.c: Regenerate. * generated/maxval_i4.c: Regenerate. * generated/maxloc1_4_i8.c: Regenerate. * generated/maxloc0_16_i16.c: Regenerate. * generated/maxloc1_4_i16.c: Regenerate. * generated/maxloc0_8_i16.c: Regenerate. * generated/maxloc0_4_i4.c: Regenerate. * generated/maxloc1_8_i8.c: Regenerate. * generated/maxloc0_8_i4.c: Regenerate. * generated/maxloc0_16_i4.c: Regenerate. * generated/maxloc1_16_i8.c: Regenerate. * generated/maxloc1_4_i4.c: Regenerate. * generated/maxval_i8.c: Regenerate. * generated/maxloc0_4_i16.c: Regenerate. * generated/maxloc1_8_i16.c: Regenerate. * generated/maxloc0_4_i8.c: Regenerate. * generated/maxloc1_16_i16.c: Regenerate. * generated/maxval_i16.c: Regenerate. Added: branches/gcc-4_2-branch/gcc/testsuite/gfortran.dg/maxlocval.f90 Modified: branches/gcc-4_2-branch/gcc/fortran/ChangeLog branches/gcc-4_2-branch/gcc/fortran/trans-intrinsic.c branches/gcc-4_2-branch/gcc/testsuite/ChangeLog branches/gcc-4_2-branch/libgfortran/ChangeLog branches/gcc-4_2-branch/libgfortran/generated/maxloc0_16_i16.c branches/gcc-4_2-branch/libgfortran/generated/maxloc0_16_i4.c branches/gcc-4_2-branch/libgfortran/generated/maxloc0_16_i8.c branches/gcc-4_2-branch/libgfortran/generated/maxloc0_4_i16.c branches/gcc-4_2-branch/libgfortran/generated/maxloc0_4_i4.c branches/gcc-4_2-branch/libgfortran/generated/maxloc0_4_i8.c branches/gcc-4_2-branch/libgfortran/generated/maxloc0_8_i16.c branches/gcc-4_2-branch/libgfortran/generated/maxloc0_8_i4.c branches/gcc-4_2-branch/libgfortran/generated/maxloc0_8_i8.c branches/gcc-4_2-branch/libgfortran/generated/maxloc1_16_i16.c branches/gcc-4_2-branch/libgfortran/generated/maxloc1_16_i4.c branches/gcc-4_2-branch/libgfortran/generated/maxloc1_16_i8.c branches/gcc-4_2-branch/libgfortran/generated/maxloc1_4_i16.c branches/gcc-4_2-branch/libgfortran/generated/maxloc1_4_i4.c branches/gcc-4_2-branch/libgfortran/generated/maxloc1_4_i8.c branches/gcc-4_2-branch/libgfortran/generated/maxloc1_8_i16.c branches/gcc-4_2-branch/libgfortran/generated/maxloc1_8_i4.c branches/gcc-4_2-branch/libgfortran/generated/maxloc1_8_i8.c branches/gcc-4_2-branch/libgfortran/generated/maxval_i16.c branches/gcc-4_2-branch/libgfortran/generated/maxval_i4.c branches/gcc-4_2-branch/libgfortran/generated/maxval_i8.c branches/gcc-4_2-branch/libgfortran/m4/iparm.m4 -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30512
next prev parent reply other threads:[~2007-02-16 14:16 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-01-20 0:10 [Bug fortran/30512] New: " brooks at gcc dot gnu dot org 2007-01-20 9:38 ` [Bug fortran/30512] " burnus at gcc dot gnu dot org 2007-01-20 12:46 ` burnus at gcc dot gnu dot org 2007-01-22 7:56 ` fxcoudert at gcc dot gnu dot org 2007-01-22 8:47 ` burnus at gcc dot gnu dot org 2007-01-22 20:16 ` sgk at troutmask dot apl dot washington dot edu 2007-01-27 13:24 ` tkoenig at gcc dot gnu dot org 2007-01-28 22:39 ` tkoenig at gcc dot gnu dot org 2007-01-29 8:40 ` burnus at gcc dot gnu dot org 2007-01-30 17:58 ` burnus at gcc dot gnu dot org 2007-02-01 9:01 ` patchapp at dberlin dot org 2007-02-09 21:56 ` burnus at gcc dot gnu dot org 2007-02-16 14:16 ` burnus at gcc dot gnu dot org [this message] 2007-02-16 14:17 ` [Bug fortran/30512] [4.1 only] " burnus at gcc dot gnu dot org 2007-02-17 21:29 ` tkoenig at gcc dot gnu dot org 2007-02-20 17:39 ` 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=20070216141551.7252.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).