public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "zadeck at naturalbridge dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/66311] [5/6 Regression] Problems with some integer(16) values
Date: Tue, 04 Aug 2015 17:03:00 -0000	[thread overview]
Message-ID: <bug-66311-4-EcWxIYfnPz@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-66311-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #10 from Kenneth Zadeck <zadeck at naturalbridge dot com> ---
I have audited the patch for the non memory management issues and it is 
approved.

thanks for doing this.

kenny

On 08/04/2015 07:38 AM, mikael at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66311
>
> --- Comment #8 from Mikael Morin <mikael at gcc dot gnu.org> ---
> Created attachment 36121
>    --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=36121&action=edit
> Beginning of a patch
>
> The existing code mixes gmp allocation with wide_int allocation.
> With the patch, an extra sign bit needs to be written in the most significant
> word.
> I don't know how to avoid the memory management nightmare.
>


  parent reply	other threads:[~2015-08-04 17:03 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-27 15:35 [Bug fortran/66311] New: [5 " gerhard.steinmetz.fortran@t-online.de
2015-05-28  1:48 ` [Bug fortran/66311] " jvdelisle at gcc dot gnu.org
2015-05-28  7:38 ` [Bug fortran/66311] [5/6 " rguenth at gcc dot gnu.org
2015-05-28  9:22 ` dominiq at lps dot ens.fr
2015-07-16  9:13 ` rguenth at gcc dot gnu.org
2015-07-17  0:52 ` zadeck at naturalbridge dot com
2015-08-04 10:07 ` mikael at gcc dot gnu.org
2015-08-04 11:38 ` mikael at gcc dot gnu.org
2015-08-04 17:00 ` mrs at gcc dot gnu.org
2015-08-04 17:03 ` zadeck at naturalbridge dot com [this message]
2015-08-04 17:18 ` rsandifo at gcc dot gnu.org
2015-08-04 18:31 ` fxcoudert at gcc dot gnu.org
2015-08-04 18:51 ` mikael at gcc dot gnu.org
2015-08-04 19:09 ` fxcoudert at gcc dot gnu.org
2015-08-04 20:12 ` rsandifo at gcc dot gnu.org
2015-08-05 14:24 ` rsandifo at gcc dot gnu.org
2015-08-05 14:25 ` rsandifo at gcc dot gnu.org
2015-10-16  8:32 ` rguenth at gcc dot gnu.org
2015-10-17  3:55 ` [Bug middle-end/66311] [5 " mrs at gcc dot gnu.org
2015-10-17  3:58 ` mrs at gcc dot gnu.org
2015-10-27  9:21 ` clyon at gcc dot gnu.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=bug-66311-4-EcWxIYfnPz@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).