From: Jeffrey A Law <law@cygnus.com>
To: Robert Lipe <robertlipe@usa.net>
Cc: "Kaveh R. Ghazi" <ghazi@caip.rutgers.edu>, egcs@egcs.cygnus.com
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: <22850.936688821@upchuck.cygnus.com> (raw)
Message-ID: <19990930180200.cnH0E3ideNSDI-QRd-GWgwW1K4eS7Oyjf5KTFFfQvDA@z> (raw)
In-Reply-To: <19990906170243.C11191@rjlhome.sco.com>
In message < 19990906170243.C11191@rjlhome.sco.com >you write:
> Instead of adding more attributes, isn't this the very type of
> functionality what C9X calls "restrict"?
I do not believe they are identical, but I'd have to go back and read the
various "restrict" threads to be sure.
Mark as the resident expert, can "restrict" be used to tell the aliasing code
that the return value from certain functions can never alias anything else
in the program?
jeff
next prev parent reply other threads:[~1999-09-30 18:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
1999-09-07 9:05 ` Should we create an attribute malloc for supposed aliasbenefits? Mark Mitchell
1999-09-30 18:02 ` Mark Mitchell
1999-09-07 17:09 ` Mark Mitchell
1999-09-30 18:02 ` Mark Mitchell
1999-09-30 18:02 ` Should we create an attribute malloc for supposed alias benefits? 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
1999-09-08 13:27 Kaveh R. Ghazi
1999-09-08 13:44 ` Mark Mitchell
1999-09-30 18:02 ` Mark Mitchell
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=22850.936688821@upchuck.cygnus.com \
--to=law@cygnus.com \
--cc=egcs@egcs.cygnus.com \
--cc=ghazi@caip.rutgers.edu \
--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).