public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "joerg.richter@pdv-fs.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/59603] std::random_shuffle tries to swap element with itself
Date: Sun, 09 Feb 2014 17:31:00 -0000 [thread overview]
Message-ID: <bug-59603-4-I1d8lWV331@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-59603-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59603
--- Comment #4 from Jörg Richter <joerg.richter@pdv-fs.de> ---
Are you sure that this is not a iter_swap problem? I have found nothing in the
standard that iter_swap( x, x ) is undefined.
I always thought types do not have to be prepared to handle self move
assignment.
>From gcc-bugs-return-443131-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Feb 09 17:32:47 2014
Return-Path: <gcc-bugs-return-443131-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 17998 invoked by alias); 9 Feb 2014 17:32:46 -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 17640 invoked by uid 55); 9 Feb 2014 17:32:42 -0000
From: "janus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/58803] Proc-pointer component: free_components deallocates twice pointer p->tb at symbol.c:2068
Date: Sun, 09 Feb 2014 17:32: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: 4.8.2
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: janus at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
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-58803-4-PCpW7zTBkD@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-58803-4@http.gcc.gnu.org/bugzilla/>
References: <bug-58803-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: 2014-02/txt/msg00888.txt.bz2
Content-length: 909
http://gcc.gnu.org/bugzilla/show_bug.cgi?idX803
--- Comment #4 from janus at gcc dot gnu.org ---
Author: janus
Date: Sun Feb 9 17:32:07 2014
New Revision: 207644
URL: http://gcc.gnu.org/viewcvs?rev 7644&root=gcc&view=rev
Log:
2014-02-09 Janus Weil <janus@gcc.gnu.org>
Backport from mainline
2013-10-21 Tobias Burnus <burnus@net-b.de>
PR fortran/58803
PR fortran/59395
* decl.c (match_ppc_decl): Prevent later double free.
2014-02-09 Janus Weil <janus@gcc.gnu.org>
Backport from mainline
2013-10-21 Tobias Burnus <burnus@net-b.de>
PR fortran/58803
PR fortran/59395
* gfortran.dg/proc_ptr_comp_38.f90: New.
Added:
branches/gcc-4_8-branch/gcc/testsuite/gfortran.dg/proc_ptr_comp_38.f90
Modified:
branches/gcc-4_8-branch/gcc/fortran/ChangeLog
branches/gcc-4_8-branch/gcc/fortran/decl.c
branches/gcc-4_8-branch/gcc/testsuite/ChangeLog
next prev parent reply other threads:[~2014-02-09 17:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-26 16:36 [Bug libstdc++/59603] New: " fab at orlen dot de
2013-12-26 16:37 ` [Bug libstdc++/59603] " fab at orlen dot de
2014-02-04 8:38 ` joerg.richter@pdv-fs.de
2014-02-04 13:10 ` redi at gcc dot gnu.org
2014-02-08 20:19 ` redi at gcc dot gnu.org
2014-02-09 17:31 ` joerg.richter@pdv-fs.de [this message]
2014-02-10 19:00 ` redi at gcc dot gnu.org
2014-09-12 11:45 ` redi at gcc dot gnu.org
2014-09-12 13:31 ` redi at gcc dot gnu.org
2014-09-12 13:35 ` redi at gcc dot gnu.org
2014-12-06 20:38 ` redi at gcc dot gnu.org
2014-12-06 22:04 ` redi at gcc dot gnu.org
2015-09-16 11:37 ` TonyELewis at hotmail 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-59603-4-I1d8lWV331@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).