public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "janus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/46408] [OOP] Segfault when running gfortran.dg/class_allocate_6.f03 Date: Sun, 02 Jan 2011 21:02:00 -0000 [thread overview] Message-ID: <bug-46408-4-6JHeX4QlvF@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-46408-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46408 --- Comment #9 from janus at gcc dot gnu.org 2011-01-02 21:01:53 UTC --- Author: janus Date: Sun Jan 2 21:01:50 2011 New Revision: 168409 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=168409 Log: 2011-01-02 Janus Weil <janus@gcc.gnu.org> PR fortran/46408 * class.c (gfc_find_derived_vtab): Use EXEC_INIT_ASSIGN for __copy_ routine. 2011-01-02 Janus Weil <janus@gcc.gnu.org> PR fortran/46408 * gfortran.dg/class_19.f03: Adjust counting of __builtin_free. Modified: trunk/gcc/fortran/ChangeLog trunk/gcc/fortran/class.c trunk/gcc/testsuite/ChangeLog trunk/gcc/testsuite/gfortran.dg/class_19.f03
next prev parent reply other threads:[~2011-01-02 21:02 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-11-10 10:39 [Bug fortran/46408] New: " burnus at gcc dot gnu.org 2010-11-10 13:05 ` [Bug fortran/46408] " janus at gcc dot gnu.org 2010-11-11 10:09 ` burnus at gcc dot gnu.org 2010-11-20 22:02 ` danglin at gcc dot gnu.org 2011-01-02 15:58 ` janus at gcc dot gnu.org 2011-01-02 16:24 ` janus at gcc dot gnu.org 2011-01-02 17:51 ` janus at gcc dot gnu.org 2011-01-02 19:02 ` janus at gcc dot gnu.org 2011-01-02 19:24 ` janus at gcc dot gnu.org 2011-01-02 21:02 ` janus at gcc dot gnu.org [this message] 2011-01-02 21:20 ` janus 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-46408-4-6JHeX4QlvF@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: linkBe 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).