public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dominiq at lps dot ens dot fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/43539] internal compiler error: in gfc_typenode_for_spec, at fortran/trans-types.c:995
Date: Fri, 26 Mar 2010 20:35:00 -0000 [thread overview]
Message-ID: <20100326203504.10144.qmail@sourceware.org> (raw)
In-Reply-To: <bug-43539-12313@http.gcc.gnu.org/bugzilla/>
------- Comment #1 from dominiq at lps dot ens dot fr 2010-03-26 20:35 -------
Reduced test
program sizetest1
use ISO_C_BINDING
implicit none
type contains_pointer
integer data
type(contains_pointer), pointer :: next
end type contains_pointer
type(contains_pointer) sp
write(*,'(a,i0)') 'In f08: ', C_SIZEOF(sp)
end program sizetest1
(gdb) bt
#0 fancy_abort (file=0x10098f878 "../../p_work/gcc/fortran/trans-types.c",
line=995, function=0x1009f8b00 "gfc_typenode_for_spec") at
../../p_work/gcc/diagnostic.c:762
#1 0x00000001000f61c8 in gfc_typenode_for_spec (spec=0x14181e1d0) at
../../p_work/gcc/fortran/trans-types.c:995
#2 0x00000001000f696b in gfc_sym_type (sym=0x14181e1b0) at
../../p_work/gcc/fortran/trans-types.c:1770
#3 0x00000001000f65fd in gfc_get_function_type (sym=0x14181e1b0) at
../../p_work/gcc/fortran/trans-types.c:2397
#4 0x00000001000bd9ce in gfc_get_extern_function_decl (sym=0x14181e1b0) at
../../p_work/gcc/fortran/trans-decl.c:1503
#5 0x00000001000cf828 in gfc_conv_procedure_call (se=0x7fff5fbfd460,
sym=0x14181e1b0, arg=<value temporarily unavailable, due to optimizations>,
expr=0x14181e350, append_args=0x0) at
../../p_work/gcc/fortran/trans-expr.c:1678
#6 0x00000001000cfbc5 in gfc_conv_function_expr (se=0x7fff5fbfd460,
expr=<value temporarily unavailable, due to optimizations>) at
../../p_work/gcc/fortran/trans-expr.c:3911
#7 0x00000001000ca219 in gfc_conv_expr_reference (se=0x7fff5fbfd460,
expr=<value temporarily unavailable, due to optimizations>) at
../../p_work/gcc/fortran/trans-expr.c:4698
#8 0x00000001000e2464 in gfc_trans_transfer (code=0x14181e4d0) at
../../p_work/gcc/fortran/trans-io.c:2259
#9 0x00000001000a7478 in trans_code (code=0x14181e4d0, cond=0x1417d0188) at
../../p_work/gcc/fortran/trans.c:1251
#10 0x00000001000e00b9 in build_dt (function=0x141df0100, code=0x14181e6e0) at
../../p_work/gcc/fortran/trans-io.c:1830
#11 0x00000001000a7498 in trans_code (code=0x14181e6e0, cond=0x0) at
../../p_work/gcc/fortran/trans.c:1223
#12 0x00000001000c3c8f in gfc_generate_function_code (ns=<value temporarily
unavailable, due to optimizations>) at
../../p_work/gcc/fortran/trans-decl.c:4380
#13 0x0000000100069b8f in gfc_parse_file () at
../../p_work/gcc/fortran/parse.c:4226
#14 0x00000001000a291c in gfc_be_parse_file (set_yydebug=<value temporarily
unavailable, due to optimizations>) at ../../p_work/gcc/fortran/f95-lang.c:239
#15 0x00000001006d6b5a in toplev_main (argc=3, argv=0x7fff5fbfd9d8) at
../../p_work/gcc/toplev.c:1053
#16 0x00000001000019e4 in start ()
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43539
next prev parent reply other threads:[~2010-03-26 20:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-26 13:48 [Bug fortran/43539] New: " dominiq at lps dot ens dot fr
2010-03-26 20:35 ` dominiq at lps dot ens dot fr [this message]
2010-03-27 7:55 ` [Bug fortran/43539] " pault at gcc dot gnu dot org
2010-05-07 18:13 ` dfranke 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=20100326203504.10144.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: 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).