public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jvdelisle at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libquadmath/65757] gfortran gives incorrect result for anint with real*16 argument
Date: Thu, 23 Apr 2015 00:49:00 -0000	[thread overview]
Message-ID: <bug-65757-4-URKH3Mr3hJ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-65757-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65757

Jerry DeLisle <jvdelisle at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jvdelisle at gcc dot gnu.org

--- Comment #4 from Jerry DeLisle <jvdelisle at gcc dot gnu.org> ---
Typically you need a libquadmath maintainer to review the patch and approve it.

I did try the patch with the small test case here, but it probably needs to get
tested for other cases.

Since it is a fairly serious wrong code bug, it would first need to go into GCC
trunk (6.0) and then after some proving time, it could be back ported. The
patch seems simple enough that one could go back a few versions I suppose.


  parent reply	other threads:[~2015-04-23  0:49 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-13 23:33 [Bug fortran/65757] New: " bugs at dhbailey dot com
2015-04-14  1:38 ` [Bug libquadmath/65757] " kargl at gcc dot gnu.org
2015-04-14 17:26 ` sgk at troutmask dot apl.washington.edu
2015-04-22 23:19 ` bugs at dhbailey dot com
2015-04-23  0:49 ` jvdelisle at gcc dot gnu.org [this message]
2015-04-23  0:55 ` sgk at troutmask dot apl.washington.edu
2015-04-23  1:31 ` jvdelisle at gcc dot gnu.org
2015-04-23  8:05 ` dominiq at lps dot ens.fr
2015-04-23 19:54 ` bugs at dhbailey dot com
2015-04-28 17:32 ` joseph at codesourcery dot com
2015-04-28 21:55 ` sgk at troutmask dot apl.washington.edu
2015-04-28 22:09 ` joseph at codesourcery dot com

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=bug-65757-4-URKH3Mr3hJ@http.gcc.gnu.org/bugzilla/ \
    --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).