This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH] noclobber & noescape annotations for function arguments

On 05/07/2010 11:48 AM, Richard Guenther wrote:
> On Fri, 7 May 2010, Tobias Burnus wrote:
>   
>> I think one could split library functions called for READ and WRITE,
>> which would allow for a more useful annotation.
>>     
> The most immediate useful annotation would be to assert that the
> arguments do not escape.  Which is not true for async I/O.
> Is it true at the moment (as async I/O is not implemented)?
>   

That's true - asynchronous I/O is not implemented.* However, as we plan
to break the ABI for the new array descriptor, one could at the same
time split the transfer function for read and write.

Tobias

* To be more precise: Asynchronous I/O according to Fortran standard is
implemented; however, all I/O is actually performed synchronously - as
allowed by the standard. Janne is working on true AIO, but as written,
one can and should call different library routines for those.
Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]