public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "clyon at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/67843] New: experimental/filesystem/iterators/directory_iterator.cc fails on armv5t
Date: Sun, 04 Oct 2015 18:24:00 -0000	[thread overview]
Message-ID: <bug-67843-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 67843
           Summary: experimental/filesystem/iterators/directory_iterator.c
                    c fails on armv5t
           Product: gcc
           Version: unknown
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: libstdc++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: clyon at gcc dot gnu.org
  Target Milestone: ---

./experimental/filesystem/iterators/directory_iterator.cc fails when compiled
with -march=armv5t:
*** Error in `./directory_iterator.exe': malloc(): memory corruption:
0x40b787f7 ***^M

To reproduce it, you can build an armv7* toolchain, can compile this testcase
with -march=armv5t, and execute the result.

I chose the libstdc++ category for the time being, but it could very well be
target dependent bug (since it works on armv7-a for instance).


             reply	other threads:[~2015-10-04 18:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-04 18:24 clyon at gcc dot gnu.org [this message]
2015-10-05  6:44 ` [Bug libstdc++/67843] " clyon at gcc dot gnu.org
2015-10-05 10:16 ` clyon at gcc dot gnu.org
2015-10-07 22:11 ` redi at gcc dot gnu.org
2015-10-07 22:41 ` redi at gcc dot gnu.org
2015-10-09 13:52 ` clyon 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-67843-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).