public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/17202] ice-on-valid-code, trans-array.c:217: gfc_conv_descriptor_dtype Assertion failed Date: Sun, 05 Jun 2005 09:01:00 -0000 [thread overview] Message-ID: <20050605085940.13630.qmail@sourceware.org> (raw) In-Reply-To: <20040826145805.17202.c.lemmen@fz-juelich.de> ------- Additional Comments From cvs-commit at gcc dot gnu dot org 2005-06-05 08:59 ------- Subject: Bug 17202 CVSROOT: /cvs/gcc Module name: gcc Branch: gcc-4_0-branch Changes by: pault@gcc.gnu.org 2005-06-05 08:59:18 Modified files: gcc/fortran : ChangeLog trans-array.c trans-expr.c Log message: 005-05-31 Paul Thomas <pault@gcc.gnu.org> PR fortran/18109 PR fortran/18283 PR fortran/19107 PR fortran/16939 PR fortran/17192 PR fortran/17193 PR fortran/17202 PR fortran/18689 PR fortran/18890 * fortran/trans-array.c (gfc_conv_expr_descriptor): Obtain the string length from the expression typespec character length value and set temp_ss->stringlength and backend_decl. Obtain the tree expression from gfc_conv_expr rather than gfc_conv_expr_val. Dereference the expression to obtain the character. * fortran/trans-array.c (gfc_conv_resolve_dependencies): Add string length to temp_ss for character pointer array assignments. * fortran/trans-expr.c (gfc_conv_component_ref): Remove the dereference of scalar character pointer structure components. * fortran/trans-expr.c (gfc_trans_subarray_assign): Obtain the string length for the structure component from the component expression. * fortran/trans-expr.c (gfc_conv_variable): Correct errors in dereferencing of characters and character pointers. * fortran/trans-expr.c (gfc_conv_function_call): Provide string length as return argument for various kinds of handling of return. Return a char[]* temporary for character pointer functions and dereference the temporary upon return. Patches: http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/fortran/ChangeLog.diff?cvsroot=gcc&only_with_tag=gcc-4_0-branch&r1=1.335.2.66&r2=1.335.2.67 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/fortran/trans-array.c.diff?cvsroot=gcc&only_with_tag=gcc-4_0-branch&r1=1.39.2.3&r2=1.39.2.4 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/fortran/trans-expr.c.diff?cvsroot=gcc&only_with_tag=gcc-4_0-branch&r1=1.38.2.4&r2=1.38.2.5 -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17202
next prev parent reply other threads:[~2005-06-05 9:00 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-08-26 14:58 [Bug fortran/17202] New: " c dot lemmen at fz-juelich dot de 2004-08-26 15:02 ` [Bug fortran/17202] " c dot lemmen at fz-juelich dot de 2004-08-26 15:03 ` pinskia at gcc dot gnu dot org 2004-09-20 9:41 ` reichelt at gcc dot gnu dot org 2004-11-04 9:08 ` c dot lemmen at fz-juelich dot de 2005-01-25 0:20 ` pinskia at gcc dot gnu dot org 2005-03-27 22:20 ` pinskia at gcc dot gnu dot org 2005-05-29 16:03 ` cvs-commit at gcc dot gnu dot org 2005-06-05 9:01 ` cvs-commit at gcc dot gnu dot org [this message] 2005-06-05 22:44 ` pault at gcc dot gnu dot org 2005-06-05 22:45 ` pault at gcc dot gnu dot org 2005-06-05 22:51 ` pinskia at gcc dot gnu dot org 2005-06-11 22:45 ` pinskia 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=20050605085940.13630.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).