public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "arjen.markus895 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/67779] New: Strange ordering with strings in extended object
Date: Wed, 30 Sep 2015 10:58:00 -0000	[thread overview]
Message-ID: <bug-67779-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67779

            Bug ID: 67779
           Summary: Strange ordering with strings in extended object
           Product: gcc
           Version: 4.9.3
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: fortran
          Assignee: unassigned at gcc dot gnu.org
          Reporter: arjen.markus895 at gmail dot com
  Target Milestone: ---

Created attachment 36421
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=36421&action=edit
Source file demonstrating the problem

The attached program constructs a small array of integers and strings and then
sorts them. The output is:
 Sorting ...
 Result:
           1
           2
           3
           4
           5
           6
           7
           8
           9
          10
 String = 10         
 String = 1          
 String = 2          
 String = 3          
 String = 4          
 String = 5          
 String = 6          
 String = 7          
 String = 8          
 String = 9           

What is unexpected is the fact that "String = 10" comes before "String = 1". I
have not been able to reduce the code (other than removing the derived type
with integers) and still exhibit the odd ordering. The ten integers show that
the quicksort routine does its job, though. When comparing the strings in a
small program, "String = 10" definitely comes after "String = 1" as I would
expect.


             reply	other threads:[~2015-09-30 10:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-30 10:58 arjen.markus895 at gmail dot com [this message]
2015-10-01 18:46 ` [Bug fortran/67779] " gerhard.steinmetz.fortran@t-online.de
2015-10-09 13:46 ` dominiq at lps dot ens.fr
2015-10-09 13:56 ` arjen.markus895 at gmail dot com
2015-10-09 16:04 ` dominiq at lps dot ens.fr
2015-10-10  8:08 ` dominiq at lps dot ens.fr
2015-10-11  9:05 ` dominiq at lps dot ens.fr
2015-10-12  9:53 ` arjen.markus895 at gmail dot com

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-67779-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).