public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/51845] [4.7 regression] 23_containers/unordered_multimap/erase/24061-multimap.cc segfault
Date: Fri, 13 Jan 2012 20:37:00 -0000	[thread overview]
Message-ID: <bug-51845-4-lRHgYUZDfE@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-51845-4@http.gcc.gnu.org/bugzilla/>

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

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |wrong-code
             Target|                            |mips64-linux-gnu and
                   |                            |s390-linux-gnu

--- Comment #9 from Andrew Pinski <pinskia at gcc dot gnu.org> 2012-01-13 20:25:19 UTC ---
It also fails for mips64 with the N32 ABI:
http://gcc.gnu.org/ml/gcc-testresults/2012-01/msg01203.html

And valgrind is not supported on mips64 yet either.


  parent reply	other threads:[~2012-01-13 20:27 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-13  9:29 [Bug libstdc++/51845] New: [4.6 " krebbel at gcc dot gnu.org
2012-01-13  9:53 ` [Bug libstdc++/51845] [4.7 " rguenth at gcc dot gnu.org
2012-01-13 10:57 ` paolo.carlini at oracle dot com
2012-01-13 11:44 ` dominiq at lps dot ens.fr
2012-01-13 12:43 ` krebbel at gcc dot gnu.org
2012-01-13 12:45 ` krebbel at gcc dot gnu.org
2012-01-13 12:57 ` paolo.carlini at oracle dot com
2012-01-13 13:40 ` krebbel at gcc dot gnu.org
2012-01-13 17:27 ` jakub at gcc dot gnu.org
2012-01-13 20:37 ` pinskia at gcc dot gnu.org [this message]
2012-01-13 23:01 ` ebotcazou at gcc dot gnu.org
2012-01-15 14:05 ` schwab@linux-m68k.org
2012-01-15 17:22 ` krebbel at gcc dot gnu.org
2012-01-15 21:47 ` fdumont at gcc dot gnu.org
2012-01-15 22:42 ` schwab@linux-m68k.org
2012-01-15 23:17 ` dominiq at lps dot ens.fr
2012-01-16  0:07 ` paolo.carlini at oracle dot com
2012-01-18 19:31 ` jakub at gcc dot gnu.org
2012-01-18 21:14 ` fdumont at gcc dot gnu.org
2012-01-18 22:01 ` jakub at gcc dot gnu.org
2012-01-19 10:51 ` jakub at gcc dot gnu.org
2012-01-19 11:04 ` jakub 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-51845-4-lRHgYUZDfE@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).