public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pault at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/38602] [regression 4.4] segfault - optional arguments, generics, interface problem, iso_varying_string ?? Date: Mon, 22 Dec 2008 19:40:00 -0000 [thread overview] Message-ID: <20081222193936.15046.qmail@sourceware.org> (raw) In-Reply-To: <bug-38602-17105@http.gcc.gnu.org/bugzilla/> ------- Comment #8 from pault at gcc dot gnu dot org 2008-12-22 19:39 ------- Created an attachment (id=16969) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=16969&action=view) patch for the PR This is a patch that I cannot commit until January 3rd at the earliest. Please could you do the honours, Jerry? It runs all of alloc_comp*.f90 correctly but I have NOT regtested it. Paul 2008-12-22 Paul Thomas <pault@gcc.gnu.org> PR fortran/35780 * trans-decl.c (init_intent_out_dt): Allow for optional args. 2008-12-22 Paul Thomas <pault@gcc.gnu.org> PR fortran/35780 * gfortran.dg/alloc_comp_optional_1.f90: New test. ! { dg-do run } ! Tests the fix for PR38602, a regression caused by a modification ! to the nulling of INTENT_OUT dummies with allocatable components ! that caused a segfault with optional arguments. ! ! Contributed by David Kinniburgh <davidkinniburgh@yahoo.co.uk> ! program test_iso type ivs character(LEN=1), dimension(:), allocatable :: chars end type ivs type(ivs) :: v_str integer :: i call foo(v_str, i) if (v_str%chars(1) .ne. "a") call abort if (i .ne. 0) call abort call foo(flag = i) if (i .ne. 1) call abort contains subroutine foo (arg, flag) type(ivs), optional, intent(out) :: arg integer :: flag if (present(arg)) then arg = ivs([(char(i+96), i = 1,10)]) flag = 0 else flag = 1 end if end subroutine end -- pault at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|unassigned at gcc dot gnu |pault at gcc dot gnu dot org |dot org | Status|NEW |ASSIGNED http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38602
next prev parent reply other threads:[~2008-12-22 19:40 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-12-21 22:39 [Bug fortran/38602] New: run time error (crash) " davidgkinniburgh at yahoo dot co dot uk 2008-12-21 23:40 ` [Bug fortran/38602] " mikael at gcc dot gnu dot org 2008-12-22 0:30 ` [Bug fortran/38602] [regression 4.4] segfault " kargl at gcc dot gnu dot org 2008-12-22 0:32 ` kargl at gcc dot gnu dot org 2008-12-22 5:19 ` jvdelisle at gcc dot gnu dot org 2008-12-22 18:52 ` mikael at gcc dot gnu dot org 2008-12-22 18:55 ` mikael at gcc dot gnu dot org 2008-12-22 19:00 ` mikael at gcc dot gnu dot org 2008-12-22 19:40 ` pault at gcc dot gnu dot org [this message] 2008-12-22 20:04 ` pault at gcc dot gnu dot org 2008-12-22 20:54 ` jvdelisle at gcc dot gnu dot org 2008-12-22 23:40 ` jvdelisle at gcc dot gnu dot org 2008-12-23 0:19 ` mikael at gcc dot gnu dot org 2008-12-23 1:13 ` jvdelisle at verizon dot net 2008-12-23 1:35 ` jvdelisle at gcc dot gnu dot org 2008-12-23 1:36 ` jvdelisle at gcc dot gnu dot org 2008-12-23 2:12 ` jvdelisle at gcc dot gnu dot org 2008-12-23 9:27 ` pault at gcc dot gnu dot org 2009-01-24 10:56 ` rguenth 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=20081222193936.15046.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).