public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "manu at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/67064] Register asm variable broken
Date: Mon, 03 Aug 2015 18:53:00 -0000	[thread overview]
Message-ID: <bug-67064-4-iNdY8eaL4S@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-67064-4@http.gcc.gnu.org/bugzilla/>

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

Manuel López-Ibáñez <manu at gcc dot gnu.org> changed:

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

--- Comment #19 from Manuel López-Ibáñez <manu at gcc dot gnu.org> ---
(In reply to Daniel Gutson from comment #18)
> Please assign this to me. Thanks.

You need to login with your @gcc.gnu.org account to be able to assign bugs (and
do other Bugzilla operations).
>From gcc-bugs-return-493991-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Aug 03 19:03:47 2015
Return-Path: <gcc-bugs-return-493991-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 92038 invoked by alias); 3 Aug 2015 19:03:47 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 91834 invoked by uid 48); 3 Aug 2015 19:03:43 -0000
From: "daniel.gutson at tallertechnologies dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/67064] Register asm variable broken
Date: Mon, 03 Aug 2015 19:03:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 6.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: daniel.gutson at tallertechnologies dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-67064-4-1Qmy89JGUQ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-67064-4@http.gcc.gnu.org/bugzilla/>
References: <bug-67064-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2015-08/txt/msg00133.txt.bz2
Content-length: 686

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

--- Comment #20 from Daniel Gutson <daniel.gutson at tallertechnologies dot com> ---
(In reply to Manuel López-Ibáñez from comment #19)
> (In reply to Daniel Gutson from comment #18)
> > Please assign this to me. Thanks.
> 
> You need to login with your @gcc.gnu.org account to be able to assign bugs
> (and do other Bugzilla operations).

I don't have a @gcc.gnu.org account. Should I simply send the attachment?
Otherwise please assign this to me for me if it is still possible. FWIW, I've
been listed in the MAINTAINER list in the past while working for CodeSourcery
but my name no longer is in that list.
>From gcc-bugs-return-493992-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Aug 03 19:08:32 2015
Return-Path: <gcc-bugs-return-493992-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 99668 invoked by alias); 3 Aug 2015 19:08:32 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 99212 invoked by uid 48); 3 Aug 2015 19:08:25 -0000
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/66079] [6 Regression] memory leak with source allocation in internal subprogram
Date: Mon, 03 Aug 2015 19:08:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 6.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kargl at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: pault at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 6.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-66079-4-wgcU6Ewn3c@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-66079-4@http.gcc.gnu.org/bugzilla/>
References: <bug-66079-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2015-08/txt/msg00134.txt.bz2
Content-length: 936

https://gcc.gnu.org/bugzilla/show_bug.cgi?idf079

kargl at gcc dot gnu.org changed:

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

--- Comment #9 from kargl at gcc dot gnu.org ---
(In reply to Paul Thomas from comment #8)
> Created attachment 36113 [details]
> Patch for th 5 branch
>
> Before closing this PR, I checked and found that the 5 branch now leaks
> memory.
>
> The attached fixes the memory leak but does not fix the ICEs for which the
> tests have been commented out. There is already too much divergence in
> trans_allocate between 5 and 6 to do any more.
>
> What do you think about applying this patch, which bootstraps and regtests?
>

I think that it would be fine to apply the patch (as you already have
done the backport of a patch and tested it).


  parent reply	other threads:[~2015-08-03 18:53 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-30  6:41 [Bug c++/67064] New: " sebastian.huber@embedded-brains.de
2015-07-30  6:51 ` [Bug c++/67064] " sebastian.huber@embedded-brains.de
2015-07-30  7:10 ` pinskia at gcc dot gnu.org
2015-07-30 14:31 ` hannes_weisbach at gmx dot net
2015-07-30 15:23 ` daniel.gutson at tallertechnologies dot com
2015-07-30 16:34 ` daniel.gutson at tallertechnologies dot com
2015-07-30 17:54 ` jens.maurer at gmx dot net
2015-07-30 18:27 ` daniel.gutson at tallertechnologies dot com
2015-07-30 18:47 ` jason at gcc dot gnu.org
2015-07-30 18:50 ` ville.voutilainen at gmail dot com
2015-07-30 18:52 ` daniel.gutson at tallertechnologies dot com
2015-07-30 19:08 ` ville.voutilainen at gmail dot com
2015-07-30 19:18 ` jason at gcc dot gnu.org
2015-07-31 14:53 ` daniel.gutson at tallertechnologies dot com
2015-07-31 20:24 ` jens.maurer at gmx dot net
2015-08-03 15:47 ` jason at gcc dot gnu.org
2015-08-03 18:43 ` daniel.gutson at tallertechnologies dot com
2015-08-03 18:53 ` manu at gcc dot gnu.org [this message]
2015-08-17 18:15 ` jason at gcc dot gnu.org
2015-08-17 18:28 ` daniel.gutson at tallertechnologies dot com
2015-08-17 18:55 ` jason at gcc dot gnu.org
2015-09-16 14:18 ` andres.tiraboschi at tallertechnologies dot com
2015-09-16 15:55 ` manu at gcc dot gnu.org
2015-10-20  6:49 ` jason 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-67064-4-iNdY8eaL4S@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).