public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "steven at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgcc/56460] _Unwind_Find_FDE is O(n) in the number of frame infos, (and LLVM's JIT will generate many of them)
Date: Tue, 26 Feb 2013 18:27:00 -0000	[thread overview]
Message-ID: <bug-56460-4-9bbuzGeNqv@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-56460-4@http.gcc.gnu.org/bugzilla/>


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

Steven Bosscher <steven at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2013-02-26
                 CC|                            |steven at gcc dot gnu.org
     Ever Confirmed|0                           |1

--- Comment #2 from Steven Bosscher <steven at gcc dot gnu.org> 2013-02-26 18:26:40 UTC ---
Re. patch:
- Why change the sort order?
- Why qsort the whole array, instead of e.g. memmove'ing the bits
that have to be moved? Those are still sorted, after all.

Note, if you have no copyright assignment on file, we cannot do
anything with the patch.


  parent reply	other threads:[~2013-02-26 18:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-26 14:42 [Bug libgcc/56460] New: " cr at progress dot com
2013-02-26 14:43 ` [Bug libgcc/56460] " cr at progress dot com
2013-02-26 18:27 ` steven at gcc dot gnu.org [this message]
2013-02-26 22:57 ` steven at gcc dot gnu.org
2013-02-27 12:16 ` cr at progress dot com
2013-02-27 21:10 ` stevenb.gcc at gmail dot com
2013-02-27 21:15 ` steven at gcc dot gnu.org
2013-02-27 21:17 ` steven at gcc dot gnu.org
2015-04-14 22:30 ` daekharel 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-56460-4-9bbuzGeNqv@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).