public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "kargl at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/45244] Incorrect passing of character string array argument triggers an internal compiler error Date: Tue, 10 Aug 2010 02:37:00 -0000 [thread overview] Message-ID: <20100810023720.26730.qmail@sourceware.org> (raw) In-Reply-To: <bug-45244-19543@http.gcc.gnu.org/bugzilla/> ------- Comment #2 from kargl at gcc dot gnu dot org 2010-08-10 02:37 ------- Created an attachment (id=21444) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=21444&action=view) Reduced testcase Reduced testcase. gdb shows Program received signal SIGSEGV, Segmentation fault. 0x080ed4c0 in compare_actual_formal (ap=0x4969174c, formal=0x495054e8, ranks_must_agree=0, is_elemental=0, where=0x4969171c) at ../../gcc4x/gcc/fortran/interface.c:1606 warning: Source file is more recent than executable. 1606 if (ref->type == REF_ARRAY && ref->u.ar.type == AR_ELEMENT (gdb) bt #0 0x080ed4c0 in compare_actual_formal (ap=0x4969174c, formal=0x495054e8, ranks_must_agree=0, is_elemental=0, where=0x4969171c) at ../../gcc4x/gcc/fortran/interface.c:1606 #1 0x080eec1c in gfc_procedure_use (sym=0x496973c0, ap=0x4969174c, where=0x4969171c) at ../../gcc4x/gcc/fortran/interface.c:2623 #2 0x0812a978 in resolve_call (c=0x49691710) at ../../gcc4x/gcc/fortran/resolve.c:3288 #3 0x0812b341 in resolve_code (code=0x49691710, ns=0x49623200) at ../../gcc4x/gcc/fortran/resolve.c:8617 #4 0x0812c453 in resolve_codes (ns=0x49623200) at ../../gcc4x/gcc/fortran/resolve.c:13052 #5 0x0812c37c in resolve_codes (ns=0x49621d00) at ../../gcc4x/gcc/fortran/resolve.c:13038 #6 0x0812c52c in gfc_resolve (ns=0x49621d00) at ../../gcc4x/gcc/fortran/resolve.c:13079 #7 0x0811f4c7 in gfc_parse_file () at ../../gcc4x/gcc/fortran/parse.c:4379 #8 0x08153e30 in gfc_be_parse_file (set_yydebug=0) at ../../gcc4x/gcc/fortran/f95-lang.c:236 #9 0x0848fc35 in do_compile () at ../../gcc4x/gcc/toplev.c:978 #10 0x084909c6 in toplev_main (argc=2, argv=0xbfbfe57c) at ../../gcc4x/gcc/toplev.c:2374 #11 0x081ada92 in main (argc=4, argv=0x6) at ../../gcc4x/gcc/main.c:36 -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45244
next prev parent reply other threads:[~2010-08-10 2:37 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-08-10 2:07 [Bug fortran/45244] New: " Eric dot Zurcher at csiro dot au 2010-08-10 2:17 ` [Bug fortran/45244] " Eric dot Zurcher at csiro dot au 2010-08-10 2:37 ` kargl at gcc dot gnu dot org [this message] 2010-08-10 17:50 ` kargl at gcc dot gnu dot org 2010-08-10 20:19 ` kargl at gcc dot gnu dot org 2010-08-10 20:43 ` mikael at gcc dot gnu dot org [not found] <bug-45244-4@http.gcc.gnu.org/bugzilla/> 2011-02-12 20:27 ` burnus 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=20100810023720.26730.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).