From: Andi Kleen <ak@muc.de>
To: Jakub Jelinek <jakub@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Use __attribute__((malloc)) for gcc 3.2
Date: 30 Sep 2002 02:04:02 +0200 [thread overview]
Message-ID: <m3ptuw5onh.fsf@averell.firstfloor.org> (raw)
In-Reply-To: <20020929160113.K5659@devserv.devel.redhat.com>
Jakub Jelinek <jakub@redhat.com> writes:
> On Sun, Sep 29, 2002 at 05:27:31PM +0200, Andi Kleen wrote:
> >
> > gcc 3.2 has an __attribute__((malloc)) function attribute. It tells gcc
> > that a function returns newly allocated memory and that the return pointer
> > cannot alias with any other pointer in the parent function. This often
> > allows gcc to generate better code because the optimizer doesn't need take
> > pointer aliasing in account.
>
> Does this matter when the kernel is compiled with -fno-strict-aliasing?
I don't know. But it's certainly worth trying, isn't it ? Giving the
compiler more information can't be a bad thing.
-Andi
next prev parent reply other threads:[~2002-09-30 0:00 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 [this message]
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
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=m3ptuw5onh.fsf@averell.firstfloor.org \
--to=ak@muc.de \
--cc=jakub@redhat.com \
--cc=linux-kernel@vger.kernel.org \
/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.