public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "paul dot thomas at jet dot uk" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/24813] ICE with scalarization LEN of character types
Date: Mon, 24 Apr 2006 09:10:00 -0000	[thread overview]
Message-ID: <20060424091028.17231.qmail@sourceware.org> (raw)
In-Reply-To: <bug-24813-11701@http.gcc.gnu.org/bugzilla/>



------- Comment #5 from paul dot thomas at jet dot uk  2006-04-24 09:10 -------
(In reply to comment #4)
> This looks to be fixable at trans-intrinsic.c(gfc_conv_intrinsic_len), here a
> special switch branch for constructors is needed.
> I will make it so.
> Paul

This is indeed the case; the ICE comes about because none of the trappings of
the scalarizer have been invoked to translate the array constructor.  Rather
than do this, I have called trans-array.c (get_array_ctor_strlen) to obtain the
string length directly.  This clears the bug; I will regtest tonight and will
submit tomorrow.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24813


  parent reply	other threads:[~2006-04-24  9:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-11 20:55 [Bug fortran/24813] New: internal compiler error in gfortran dbs at hpcrdm dot lbl dot gov
2005-11-11 20:57 ` [Bug fortran/24813] " pinskia at gcc dot gnu dot org
2005-11-11 21:10 ` pinskia at gcc dot gnu dot org
2006-01-01  6:26 ` [Bug fortran/24813] ICE on LEN on a parameter character array pinskia at gcc dot gnu dot org
2006-01-02  2:42 ` [Bug fortran/24813] ICE with constructer of character pinskia at gcc dot gnu dot org
2006-04-23  6:03 ` [Bug fortran/24813] ICE with scalarization LEN of character types pault at gcc dot gnu dot org
2006-04-24  9:10 ` paul dot thomas at jet dot uk [this message]
2006-04-28  8:00 ` patchapp at dberlin dot org
2006-05-07  5:46 ` pault at gcc dot gnu dot org
2006-05-08  5:02 ` pault at gcc dot gnu dot org
2006-05-08  6:25 ` 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=20060424091028.17231.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).