From: Marc Glisse <marc.glisse@inria.fr>
To: Jeff Law <law@redhat.com>
Cc: Richard Biener <rguenther@suse.de>,
gcc-patches@gcc.gnu.org, Jakub Jelinek <jakub@redhat.com>
Subject: Re: [PATCH][RFC] Improve get_qualified_type linear list walk
Date: Wed, 17 Apr 2019 20:36:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.21.1904180005400.17087@stedding.saclay.inria.fr> (raw)
In-Reply-To: <52598ebb-fe58-fa8f-976e-8c21f5980055@redhat.com>
On Wed, 17 Apr 2019, Jeff Law wrote:
>> * tree.c (get_qualified_type): Put found type variants at the
>> head of the variant list.
> Seems quite reasonable to me. I just hope we don't find a case where
> this is the exact worst case behavior ;-)
That seems unlikely. Competitive analysis of the list update problem shows
that the move-to-front strategy is 2-competitive. Here we also have
insertions so the problem is different, but still close.
--
Marc Glisse
prev parent reply other threads:[~2019-04-17 20:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-16 13:01 Richard Biener
2019-04-16 16:14 ` Michael Matz
2019-04-16 16:21 ` Jakub Jelinek
2019-04-16 17:47 ` Richard Biener
2019-04-17 12:10 ` Michael Matz
2019-04-16 17:00 ` Richard Biener
2019-04-17 11:04 ` Richard Biener
2019-04-17 11:55 ` Michael Matz
2019-04-17 18:25 ` Jeff Law
2019-04-17 20:36 ` Marc Glisse [this message]
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=alpine.DEB.2.21.1904180005400.17087@stedding.saclay.inria.fr \
--to=marc.glisse@inria.fr \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=law@redhat.com \
--cc=rguenther@suse.de \
/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).