public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Michael S. Zick <mszick@goquest.com>
To: kenner@vlsi1.ultra.nyu.edu (Richard Kenner), mszick@goquest.com
Cc: gcc@gcc.gnu.org
Subject: Re: [tree-ssa] Out of SSA status and issues
Date: Sat, 17 May 2003 17:19:00 -0000	[thread overview]
Message-ID: <03051712013700.00962@wolf686> (raw)
In-Reply-To: <10305131528.AA14941@vlsi1.ultra.nyu.edu>

On Tuesday 13 May 2003 10:28 am, Richard Kenner wrote:
>     Consider instead that '*p' is just the name given a register's
>     contents.  Neither 'i' nor '9' are processor internal.  Both are
>     external to the cpu.  The memory reference for 'i' is source code
>     implicit, the memory reference for '*p' is source code explicit.
>
> True, but given caching effects, it's hard to see how *p could be less
> expensive than 'i'.

Six of one and half a dozen of the other.  Its a Union.

I am using "Union" in the general sense of either the union of two or
more data structures OR two or more code structures.
In this usage of "Union", an assignment statement is a "Union" -
including the assignment of a function result.

Our terminology and viewpoint differ, but we are talking about the
same thing.

As to the subject of this thread, a link you may find interesting:
<http://www.sac-home.org/>

Not for the specialization of "C" that the compiler processes, but for the
compiler options that allow it to be stopped and dump its internals.

Clipped from the help menu:

OPTIMIZATION OPTIONS:

         -ssa           use optimizations based on ssa-form.
         -no <opt>      disable optimization technique <opt>
         -do <opt>      enable optimization technique <opt>

        The following optimization techniques are currently supported:

                CF      constant folding
                INL     function inlining
                LUR     loop unrolling
                WLUR    with-loop unrolling
                LUS     loop unswitching
                DCR     dead code removal
                DFR     dead function removal
                LIR     loop invariant removal
                CSE     common subexpression elimination
                WLT     with-loop transformation
                WLF     with-loop folding
                DLAW    application of the distributive law
                IVE     index vector elimination
                AE      array elimination
                RCO     refcount optimization
                UIP     update-in-place
                AP      array padding
                APL     array placement
                TSI     tile size inference (blocking)
                TSP     tile size pragmas (blocking)
                MTO     multi-thread optimization
                SBE     syncronisation barrier elimination
                PHM     private heap management
                APS     arena preselection           (in conjunction with PHM)
                RCAO    refcount allocation optimiz. (in conjunction with PHM)
                MSCA    memory size cache adjustment (in conjunction with PHM)

                OPT     enables/disables all optimizations at once.

        Lower case letters may be used to indicate optimization techniques.

        Command line arguments are evaluated from left to right, i.e.,
        "-no OPT -do INL" disables all optimizations except for
        function inlining.

Mike

  parent reply	other threads:[~2003-05-17 17:09 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-13 15:23 Richard Kenner
2003-05-13 18:50 ` Geoff Keating
2003-05-13 23:28   ` Michael S. Zick
2003-05-17 17:19 ` Michael S. Zick [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-13 13:42 Richard Kenner
2003-05-13 13:17 Richard Kenner
2003-05-13 13:27 ` Diego Novillo
2003-05-13 13:40 ` Michael Matz
2003-05-13 15:08 ` Michael S. Zick
2003-05-12 14:42 Andrew MacLeod
2003-05-12 15:38 ` Diego Novillo
2003-05-12 15:57   ` Andrew MacLeod
2003-05-12 16:05     ` Michael Matz
2003-05-12 16:10       ` Andrew MacLeod
2003-05-12 16:16       ` law
2003-05-12 17:08     ` law
2003-05-12 17:12       ` Andrew MacLeod
2003-05-12 17:26         ` law
2003-05-12 18:57 ` Andrew MacLeod
2003-05-13  9:07   ` Michael Matz
2003-05-13 12:42     ` Diego Novillo
2003-05-13 12:50       ` Andrew MacLeod
2003-05-13 13:05         ` Diego Novillo
2003-05-13 13:29           ` Andrew MacLeod
2003-05-13 13:57             ` Diego Novillo
2003-05-13 12:57       ` Michael Matz
2003-05-13 13:11         ` Diego Novillo
2003-05-13 13:18           ` Andrew MacLeod
2003-05-14 17:19             ` Jan Vroonhof
2003-05-14 18:05               ` Andrew MacLeod
2003-05-14 18:33               ` Diego Novillo
2003-05-14 19:11                 ` Daniel Berlin
2003-05-13 15:01         ` Daniel Berlin
2003-05-13 12:33   ` Diego Novillo
2003-05-13 12:49     ` Andrew MacLeod
2003-05-13 12:58       ` Diego Novillo

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=03051712013700.00962@wolf686 \
    --to=mszick@goquest.com \
    --cc=gcc@gcc.gnu.org \
    --cc=kenner@vlsi1.ultra.nyu.edu \
    /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).