From: Falk Hueffner <falk.hueffner@student.uni-tuebingen.de>
To: linux-kernel@vger.kernel.org
Subject: Re: [Lse-tech] gcc 2.95 vs 3.21 performance
Date: 10 Feb 2003 21:49:19 +0100 [thread overview]
Message-ID: <87isvrhne8.fsf@student.uni-tuebingen.de> (raw)
In-Reply-To: <1044908011.3133.123.camel@cube>
Albert Cahalan <albert@users.sourceforge.net> writes:
> BTW, in case any gcc hacker is paying attention, the documentation
> fails to mention the gcc version required for this or any other
> attribute. Also it would be nice to have an option to ditch the
> (char*) exception; it's junk when you have __may_alias__.
I don't think a switch that makes standard compliant source break in
potentially very subtle ways is a good idea. Just use "restrict".
--
Falk
next prev parent reply other threads:[~2003-02-10 20:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-10 20:13 Albert Cahalan
2003-02-10 20:49 ` Falk Hueffner [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-02-03 23:05 Martin J. Bligh
2003-02-03 23:22 ` [Lse-tech] " Andi Kleen
2003-02-04 12:20 ` Dave Jones
2003-02-04 15:50 ` Martin J. Bligh
2003-02-10 12:13 ` Momchil Velikov
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=87isvrhne8.fsf@student.uni-tuebingen.de \
--to=falk.hueffner@student.uni-tuebingen.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®