All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@muc.de>
To: Andi Kleen <ak@muc.de>, "David S. Miller" <davem@redhat.com>,
	jakub@redhat.com, torvalds@transmeta.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Use __attribute__((malloc)) for gcc 3.2
Date: Mon, 7 Oct 2002 14:27:44 +0200	[thread overview]
Message-ID: <20021007122744.GA24820@averell> (raw)
In-Reply-To: <20021007044506.D3910@twiddle.net>

On Mon, Oct 07, 2002 at 01:45:06PM +0200, Richard Henderson wrote:
> On Mon, Oct 07, 2002 at 12:56:22PM +0200, Andi Kleen wrote:
> > I retested it on gcc 3.2 and it unfortunately doesn't make any difference
> > (resulting kernel is byte-for-byte identical). So it looks like with
> > current gcc it isn't worth the effort.
> 
> *shrug* It's still good documentation of intent.  And one of
> these days we might get around to writing some aliasing code
> that doesn't suck quite so much.  ;-)

I'll resubmit the patch then.

Thanks for the feedback.

-Andi

  reply	other threads:[~2002-10-07 12:22 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-29 15:27 [PATCH] Use __attribute__((malloc)) for gcc 3.2 Andi Kleen
2002-09-29 16:24 ` Adrian Bunk
2002-09-29 17:26 ` Christoph Hellwig
2002-09-30  0:11   ` David S. Miller
2002-09-30  0:29     ` Andi Kleen
2002-09-29 20:01 ` Jakub Jelinek
2002-09-30  0:04   ` Andi Kleen
2002-10-07 10:05   ` Richard Henderson
2002-10-07 10:29     ` David S. Miller
2002-10-07 10:56       ` Andi Kleen
2002-10-07 11:07         ` Arjan van de Ven
2002-10-07 11:45         ` Richard Henderson
2002-10-07 12:27           ` Andi Kleen [this message]
2002-09-29 23:51 ` Anton Blanchard
2002-09-30  0:31   ` Andi Kleen
2002-09-30  1:07     ` Daniel Jacobowitz
2002-10-02 13:46     ` Pavel Machek
     [not found] <20020929152731.GA10631@averell.suse.lists.linux.kernel>
     [not found] ` <20020929182643.C8564@infradead.org.suse.lists.linux.kernel>
2002-09-29 19:09   ` Andi Kleen
2002-09-29 20:20     ` Adrian Bunk
2002-09-30  0:21     ` David S. Miller

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=20021007122744.GA24820@averell \
    --to=ak@muc.de \
    --cc=davem@redhat.com \
    --cc=jakub@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.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.