From: Richard Guenther <richard.guenther@gmail.com>
To: Paul Brook <paul@codesourcery.com>
Cc: gcc@gcc.gnu.org, "Paulo J. Matos" <pocmatos@gmail.com>,
Ian Lance Taylor <iant@google.com>
Subject: Re: Clustering switch cases
Date: Wed, 01 Sep 2010 08:39:00 -0000 [thread overview]
Message-ID: <AANLkTinUUndLEh5exJs+0_b6ueSBoJLWwUh3zMssYVAd@mail.gmail.com> (raw)
In-Reply-To: <201009010034.18924.paul@codesourcery.com>
On Wed, Sep 1, 2010 at 1:34 AM, Paul Brook <paul@codesourcery.com> wrote:
>> > In fact we might want to move switch optimization up to the tree level
>> > (just because it's way easier to deal with there). Thus, lower switch
>> > to a mixture of binary tree & jump-tables (possibly using perfect
>> > hashing).
>>
>> Doing the optimisation at the tree-level was exactly my initial idea.
>> By splitting the switches at the tree-level, before expand_case, would
>> then allow for expand_case to transform it either to a jump table or
>> binary tree depending on the situation.
>
> I'd kinda hope that doing the optimization at the tree level means expand_case
> doesn't have to handle both types. The tree code converts sparse case ranges
> to explicit conditionals (or a switch on a compact perfect hash), so anything
> left to RTL expansion must be a jump table.
Yes, that was my idea.
Richard.
> Paul
>
next prev parent reply other threads:[~2010-09-01 8:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-27 13:49 Paulo J. Matos
2010-08-27 15:03 ` Ian Lance Taylor
2010-08-27 15:09 ` Paulo J. Matos
2010-08-27 15:27 ` Richard Guenther
2010-08-28 0:21 ` Xinliang David Li
2010-08-28 11:08 ` Paulo J. Matos
2010-08-31 15:59 ` Rahul Kharche
[not found] ` <201009010034.18924.paul@codesourcery.com>
2010-09-01 8:39 ` Richard Guenther [this message]
2010-09-01 9:15 ` Paulo J. Matos
2010-09-01 9:33 ` Richard Guenther
2010-09-01 12:37 ` Paulo J. Matos
[not found] ` <D84AB18A31AC674EBE9B5300634A800601BF0B0932@EXCHANGEVS.IceraSemi.local>
[not found] ` <AANLkTinFhrgJw3Wz8aLhBU6PMYpJzBFTRxLUH3eoz4M0@mail.gmail.com>
[not found] ` <4D60B0700D1DB54A8C0C6E9BE691637008965A28@EXCHANGEVS.IceraSemi.local>
[not found] ` <AANLkTinkjc4Y9baHXXK7v3ibQNwMtwGhA_oGmaFbykkA@mail.gmail.com>
2010-09-03 10:29 ` Rahul Kharche
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=AANLkTinUUndLEh5exJs+0_b6ueSBoJLWwUh3zMssYVAd@mail.gmail.com \
--to=richard.guenther@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=iant@google.com \
--cc=paul@codesourcery.com \
--cc=pocmatos@gmail.com \
/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).