public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "janus at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/42104] [F03] runtime segfault with procedure pointer component Date: Thu, 19 Nov 2009 11:57:00 -0000 [thread overview] Message-ID: <20091119115708.8830.qmail@sourceware.org> (raw) In-Reply-To: <bug-42104-15250@http.gcc.gnu.org/bugzilla/> ------- Comment #4 from janus at gcc dot gnu dot org 2009-11-19 11:57 ------- Let's have a look at the dump for the test case in comment #2. The call to 'func' is translated to: real(kind=4) D.1568; struct array1_real(kind=4) parm.7; static real(kind=4) A.6[2] = {1.00000001490116119384765625e-1, 1.00000001490116119384765625e-1}; static integer(kind=4) C.1562 = 3; parm.7.dtype = 281; parm.7.dim[0].lbound = 1; parm.7.dim[0].ubound = 2; parm.7.dim[0].stride = 1; parm.7.data = (void *) &A.6[0]; parm.7.offset = 0; D.1568 = func (&C.1562, &parm.7); The PPC call to 'funcp%p' looks simlar, except for: D.1576 = _gfortran_internal_pack (&parm.10); D.1578 = funcp.p (&C.1570, D.1576); (i.e. it has an additional _gfortran_internal_pack). -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42104
next prev parent reply other threads:[~2009-11-19 11:57 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-11-19 5:52 [Bug fortran/42104] New: Segmentation fault " m dot a dot hulsen at tue dot nl 2009-11-19 5:53 ` [Bug fortran/42104] " m dot a dot hulsen at tue dot nl 2009-11-19 6:08 ` m dot a dot hulsen at tue dot nl 2009-11-19 10:45 ` [Bug fortran/42104] [F03] runtime segfault " janus at gcc dot gnu dot org 2009-11-19 11:57 ` janus at gcc dot gnu dot org [this message] 2009-11-19 13:25 ` pault at gcc dot gnu dot org 2009-11-19 21:09 ` janus at gcc dot gnu dot org 2009-11-19 21:59 ` janus at gcc dot gnu dot org 2009-11-20 4:59 ` pault at gcc dot gnu dot org 2009-11-20 6:43 ` pault at gcc dot gnu dot org 2009-11-20 6:57 ` janus at gcc dot gnu dot org 2009-11-20 7:58 ` pault at gcc dot gnu dot org 2009-12-03 5:33 ` pault at gcc dot gnu dot 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=20091119115708.8830.qmail@sourceware.org \ --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).