From: Mark Mitchell <mark@codesourcery.com>
To: ghazi@caip.rutgers.edu
Cc: law@cygnus.com, egcs@egcs.cygnus.com, robertlipe@usa.net
Subject: Re: Should we create an attribute malloc for supposed alias benefits?
Date: Thu, 30 Sep 1999 18:02:00 -0000 [thread overview]
Message-ID: <19990908134735L.mitchell@codesourcery.com> (raw)
Message-ID: <19990930180200.goJ5nSw9tJzQeX0xfh4X6A3gO-38rJ0f9VYmYXmF2Bk@z> (raw)
In-Reply-To: <199909082025.QAA25496@caip.rutgers.edu>
>>>>> "Kaveh" == Kaveh R Ghazi <ghazi@caip.rutgers.edu> writes:
Kaveh> Sorry, does that mean an attribute malloc would be useful
Kaveh> or not? :-)
I dunno. If there are malloc-like functions in other languages that
do no have any way of saying `restrict', but do support attributes,
then it would be useful.
Kaveh> Does gcc support c9x restrict today? (Even if it does,
Kaveh> would there be a -c89 mode, like -traditional in which case
Kaveh> `restrict' wouldn't work and so we would want an attribute
Kaveh> malloc anyway?)
We support __restrict__ in all modes.
Kaveh> I went ahead and wrote something which seems to work.
Kaveh> Should I bother submitting it?
I dunno.
--
Mark Mitchell mark@codesourcery.com
CodeSourcery, LLC http://www.codesourcery.com
next prev parent reply other threads:[~1999-09-30 18:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-08 13:27 Kaveh R. Ghazi
1999-09-08 13:44 ` Mark Mitchell [this message]
1999-09-30 18:02 ` Mark Mitchell
1999-09-30 18:02 ` Kaveh R. Ghazi
-- strict thread matches above, loose matches on Subject: below --
1999-09-06 12:40 Kaveh R. Ghazi
1999-09-06 14:36 ` Jeffrey A Law
1999-09-06 15:03 ` Robert Lipe
1999-09-07 0:22 ` Jeffrey A Law
1999-09-30 18:02 ` Jeffrey A Law
1999-09-30 18:02 ` Robert Lipe
1999-09-30 18:02 ` Jeffrey A Law
1999-09-30 18:02 ` Kaveh R. Ghazi
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=19990908134735L.mitchell@codesourcery.com \
--to=mark@codesourcery.com \
--cc=egcs@egcs.cygnus.com \
--cc=ghazi@caip.rutgers.edu \
--cc=law@cygnus.com \
--cc=robertlipe@usa.net \
/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).