public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/55618] New: [4.6/4.7/4.8 Regression] Failures with ISO_Varying_String test suite
Date: Fri, 07 Dec 2012 19:14:00 -0000	[thread overview]
Message-ID: <bug-55618-4@http.gcc.gnu.org/bugzilla/> (raw)


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

             Bug #: 55618
           Summary: [4.6/4.7/4.8 Regression] Failures with
                    ISO_Varying_String test suite
    Classification: Unclassified
           Product: gcc
           Version: 4.8.0
            Status: UNCONFIRMED
          Keywords: wrong-code
          Severity: normal
          Priority: P3
         Component: fortran
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: burnus@gcc.gnu.org
                CC: pault@gcc.gnu.org


The test suite is available at
http://quatramaran.ens.fr/~coudert/gfortran/vst.tar.bz2

The following test succeed with GCC 4.4 and fail with GCC 4.5/4.6/4.7/4.8. As
all versions use - here - the same libgfortran, the bug is in the compiler
itself.


a) gfortran iso_varying_string.f90 auxmod.f95 Vst17.f95

 *ERROR* elemental SPLIT(string_array,word_array,CHAR(set),separator_array) 
  set=ic}
      back=absent


b) gfortran iso_varying_string.f90 auxmod.f95 vst30.f95 

 *ERROR* elemental REPLACE(string_array,CHAR(target),substring_array) 
 element=  1  1
          result=-&?(   3)
       exp.reslt=-" ++'$?(   8)
etc.


c) gfortran iso_varying_string.f90 auxmod.f95 vst31.f95

 *ERROR* elemental REPLACE(char_array,CHAR(target),subchar_array) 
 element=  1  1
          result=&?36/*#837=                             (  40)
       exp.reslt=&8,/" ++'$=                              =                    
        (  71)

etc.


             reply	other threads:[~2012-12-07 19:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-07 19:14 burnus at gcc dot gnu.org [this message]
2012-12-07 21:14 ` [Bug fortran/55618] " burnus at gcc dot gnu.org
2012-12-10  9:46 ` burnus at gcc dot gnu.org
2012-12-10 11:43 ` burnus at gcc dot gnu.org
2013-01-06 18:48 ` pault at gcc dot gnu.org
2013-01-06 21:12 ` pault at gcc dot gnu.org
2013-01-07 23:42 ` dominiq at lps dot ens.fr
2013-01-08  6:14 ` pault at gcc dot gnu.org
2013-01-13  7:51 ` [Bug fortran/55618] [4.6/4.7 " pault at gcc dot gnu.org
2013-01-14 17:59 ` [Bug fortran/55618] [4.6 " pault at gcc dot gnu.org
2013-01-14 18:45 ` [Bug fortran/55618] [4.6, 4.7, 4.8 " pault 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=bug-55618-4@http.gcc.gnu.org/bugzilla/ \
    --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).