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++/66968] Incorrect template argument shown in diagnostic
Date: Sat, 25 Jul 2015 18:44:00 -0000 [thread overview]
Message-ID: <bug-66968-4-4rhTpbouTR@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-66968-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66968
Manuel López-Ibáñez <manu at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |manu at gcc dot gnu.org
--- Comment #1 from Manuel López-Ibáñez <manu at gcc dot gnu.org> ---
A dup of PR99 ?
>From gcc-bugs-return-493331-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jul 25 18:52:00 2015
Return-Path: <gcc-bugs-return-493331-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 25088 invoked by alias); 25 Jul 2015 18:52:00 -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 25020 invoked by uid 55); 25 Jul 2015 18:51:56 -0000
From: "mikael at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/64986] class_to_type_4.f90: valgrind error: Invalid read/write of size 8
Date: Sat, 25 Jul 2015 18:52: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: 5.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mikael at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: mikael at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-64986-4-yj1XyLw4Q7@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-64986-4@http.gcc.gnu.org/bugzilla/>
References: <bug-64986-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-07/txt/msg02221.txt.bz2
Content-length: 598
https://gcc.gnu.org/bugzilla/show_bug.cgi?idd986
--- Comment #17 from Mikael Morin <mikael at gcc dot gnu.org> ---
Author: mikael
Date: Sat Jul 25 18:51:23 2015
New Revision: 226224
URL: https://gcc.gnu.org/viewcvs?rev"6224&root=gcc&view=rev
Log:
Fix gfortran.dg/class_to_type_4.f90 deallocation code misordering failure
PR fortran/64986
gcc/fortran/
* trans-expr.c (gfc_trans_assignment_1): Put component deallocation
code at the beginning of the block.
Modified:
branches/gcc-5-branch/gcc/fortran/ChangeLog
branches/gcc-5-branch/gcc/fortran/trans-expr.c
next prev parent reply other threads:[~2015-07-25 18:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-22 13:37 [Bug c++/66968] New: " redi at gcc dot gnu.org
2015-07-25 18:44 ` manu at gcc dot gnu.org [this message]
2015-07-25 22:10 ` [Bug c++/66968] " redi at gcc dot gnu.org
2021-07-16 20:24 ` redi at gcc dot gnu.org
2021-07-16 22:05 ` cvs-commit at gcc dot gnu.org
2021-07-16 22:11 ` redi at gcc dot gnu.org
2022-07-13 12:34 ` redi at gcc dot gnu.org
2023-02-06 10:18 ` vanyacpp at gmail dot com
2023-02-06 10:20 ` vanyacpp at gmail 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-66968-4-4rhTpbouTR@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).