public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/65479] sanitizer stack trace missing frames past #0 on powerpc64
Date: Fri, 10 Apr 2015 02:14:00 -0000 [thread overview]
Message-ID: <bug-65479-4-EupXTHXkpR@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-65479-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65479
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target|powerpc64*-linux-* |
--- Comment #3 from Martin Sebor <msebor at gcc dot gnu.org> ---
The bug in backtrace_qsort is actually worse than the regression introduced in
r208403. There is a fundamental problem with relying on the addresses of the
array elements to maintain stability. Either the algorithm needs to be
replaced with a stable one like Merge Sort, or a new data member needs to be
introduced into struct line to reflect their initial order. I suspect the
latter alternative will be cheaper in terms of resources (i.e., less memory and
faster sort time).
This also means that the aspect of the bug isn't powerpc specific. It only
happens to manifest in the testsuite runs on that target.
next prev parent reply other threads:[~2015-04-10 2:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-19 23:02 [Bug sanitizer/65479] New: " msebor at gcc dot gnu.org
2015-03-20 2:49 ` [Bug sanitizer/65479] " msebor at gcc dot gnu.org
2015-04-01 1:14 ` msebor at gcc dot gnu.org
2015-04-10 2:14 ` msebor at gcc dot gnu.org [this message]
2015-04-10 6:27 ` jakub at gcc dot gnu.org
2015-04-10 15:31 ` msebor at gcc dot gnu.org
2015-04-10 15:39 ` jakub at gcc dot gnu.org
2015-04-12 23:46 ` msebor at gcc dot gnu.org
2015-04-13 18:32 ` msebor at gcc dot gnu.org
2015-04-20 1:38 ` msebor at gcc dot gnu.org
2015-06-12 0:02 ` msebor 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-65479-4-EupXTHXkpR@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).