public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "enok at lysator dot liu dot se" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/33354] [4.2 only] MINLOC in combination with SUM gives wrong result
Date: Sun, 30 Sep 2007 20:56:00 -0000 [thread overview]
Message-ID: <20070930205622.16703.qmail@sourceware.org> (raw)
In-Reply-To: <bug-33354-7816@http.gcc.gnu.org/bugzilla/>
------- Comment #7 from enok at lysator dot liu dot se 2007-09-30 20:56 -------
(In reply to comment #6)
> (In reply to comment #5)
> > I added a testcase for this.
> Thanks!
> > Can this bug be closed or does anyone feel
> > strongly enough about it to fix it in 4.2?
> If we can identify which patch fixed this, I'd be in favor
> of backporting (even though we'll miss 4.2.2).
> Thomas
I think it's a pretty serious bug. Everyone who uses MINLOC or MAXLOC will
silently get wrong result in certain cases and those intrinsics are fairly
commonly used. It would sure be nice if this could be fixed in 4.2.3, to bad
its to late for 4.2.2. Let me know if theres anything I can do to help.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33354
next prev parent reply other threads:[~2007-09-30 20:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-08 13:02 [Bug fortran/33354] New: " enok at lysator dot liu dot se
2007-09-08 15:31 ` [Bug fortran/33354] " kargl at gcc dot gnu dot org
2007-09-08 16:16 ` burnus at gcc dot gnu dot org
2007-09-11 18:37 ` pault at gcc dot gnu dot org
2007-09-22 8:53 ` [Bug fortran/33354] [4.2 only] " tkoenig at gcc dot gnu dot org
2007-09-29 7:58 ` tobi at gcc dot gnu dot org
2007-09-29 8:00 ` tobi at gcc dot gnu dot org
2007-09-29 13:12 ` tkoenig at gcc dot gnu dot org
2007-09-30 20:56 ` enok at lysator dot liu dot se [this message]
2007-09-30 21:03 ` tkoenig at gcc dot gnu dot org
2007-10-02 18:09 ` tkoenig at gcc dot gnu dot org
2007-10-02 18:51 ` tobi at gcc dot gnu dot org
2007-10-15 18:24 ` tkoenig at gcc dot gnu dot org
2007-10-15 18:24 ` 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=20070930205622.16703.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: link
Be 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).