public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "vehre at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/64787] Invalid code on sourced allocation of class(*) character string Date: Mon, 26 Jan 2015 10:08:00 -0000 [thread overview] Message-ID: <bug-64787-4-bS9Oa0nTQj@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-64787-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64787 vehre at gcc dot gnu.org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |vehre at gcc dot gnu.org --- Comment #1 from vehre at gcc dot gnu.org --- This bug does not depend on the optimization level. It segfaults reliably with -O0 (-g), too. The reason for the segfault from looking at the tree dump seems to be, that the vptr->copy() routine is called with two arguments only, but the routine stored in vptr->copy for copying a character-array is expecting 4 arguments (the pointers to the array starts and the length of the data).
next parent reply other threads:[~2015-01-26 10:08 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-64787-4@http.gcc.gnu.org/bugzilla/> 2015-01-26 10:08 ` vehre at gcc dot gnu.org [this message] 2015-01-26 12:21 ` dominiq at lps dot ens.fr 2015-03-19 15:27 ` vehre at gcc dot gnu.org 2015-03-24 10:34 ` vehre at gcc dot gnu.org 2015-03-25 10:02 ` vehre 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-64787-4-bS9Oa0nTQj@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).