All of lore.kernel.org
 help / color / mirror / Atom feed
From: Aaron Lehmann <aaronl@vitelus.com>
To: "David S. Miller" <davem@redhat.com>
Cc: wli@holomorphy.com, alexander.riesen@synopsys.COM,
	scrosby@cs.rice.edu, linux-kernel@vger.kernel.org
Subject: Re: Algoritmic Complexity Attacks and 2.4.20 the dcache code
Date: Sat, 31 May 2003 11:40:23 -0700	[thread overview]
Message-ID: <20030531184023.GA14878@vitelus.com> (raw)
In-Reply-To: <20030530.234529.88485326.davem@redhat.com>

On Fri, May 30, 2003 at 11:45:29PM -0700, David S. Miller wrote:
>    From: William Lee Irwin III <wli@holomorphy.com>
>    Date: Fri, 30 May 2003 23:41:38 -0700
>    
>    If it's literally that trivial I'll put digging around the machine
>    descriptions on my TODO list.
> 
> Look at TARGET_RTX_COSTS, thats where all of this happens.

Reading the code that handles this stuff (expmed.c) always cracks me up.


  /* We might want to refine this now that we have division-by-constant
     optimization.  Since expand_mult_highpart tries so many variants, it is
     not straightforward to generalize this.  Maybe we should make an array
     of possible modes in init_expmed?  Save this for GCC 2.7.  */
 
        /* We could just as easily deal with negative constants here,
           but it does not seem worth the trouble for GCC 2.6.  */

        /* This is extremely similar to the code for the unsigned case
           above.  For 2.7 we should merge these variants, but for
           2.6.1 I don't want to touch the code for unsigned since that
           get used in C.  The signed case will only be used by other
           languages (Ada).  */

Sometimes I wish the gcc code was tame enough for me to work on.

  reply	other threads:[~2003-05-31 18:27 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-29 20:42 Algoritmic Complexity Attacks and 2.4.20 the dcache code Scott A Crosby
2003-05-30  3:57 ` David S. Miller
2003-05-30  4:29   ` Ingo Molnar
2003-05-30 18:16     ` Timothy Miller
2003-05-30 18:53       ` Scott A Crosby
2003-05-30  5:04   ` Scott A Crosby
2003-05-30  6:24     ` David S. Miller
2003-05-30  6:46       ` Scott A Crosby
2003-05-30  6:56         ` David S. Miller
2003-05-30  8:59       ` Alex Riesen
2003-05-30  9:00         ` David S. Miller
2003-05-30 15:05           ` Scott A Crosby
2003-05-31  6:18             ` David S. Miller
2003-05-31  8:02               ` Willy TARREAU
2003-05-31  8:12                 ` David S. Miller
2003-05-31  8:56                   ` Willy Tarreau
2003-05-31  8:58                     ` David S. Miller
2003-05-31  8:58                   ` David Schwartz
2003-05-31  9:01                     ` David S. Miller
2003-05-31  6:30           ` William Lee Irwin III
2003-05-31  6:33             ` David S. Miller
2003-05-31  6:41               ` William Lee Irwin III
2003-05-31  6:45                 ` David S. Miller
2003-05-31 18:40                   ` Aaron Lehmann [this message]
2003-05-30  4:02 ` Ingo Molnar
2003-05-30  4:42   ` Scott A Crosby
2003-05-30  5:01     ` David S. Miller
2003-05-30 13:48 ` Nikita Danilov
2003-06-01  1:15 ` Daniel Phillips

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=20030531184023.GA14878@vitelus.com \
    --to=aaronl@vitelus.com \
    --cc=alexander.riesen@synopsys.COM \
    --cc=davem@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=scrosby@cs.rice.edu \
    --cc=wli@holomorphy.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.