public inbox for libc-hacker@sourceware.org
 help / color / mirror / Atom feed
From: Andreas Jaeger <aj@suse.de>
To: GNU libc hacker <libc-hacker@sourceware.cygnus.com>
Subject: Another problem in <aio.h>
Date: Thu, 16 Dec 1999 09:59:00 -0000	[thread overview]
Message-ID: <u8aena94l2.fsf@gromit.rhein-neckar.de> (raw)

I just got:
/opt/gcc-2.95/bin/gcc -ggdb -Wall -Waggregate-return -Wcast-align -Wimplicit -Wmissing-prototypes -Wnested-externs -Wno-parentheses -DAIO -DFIFO -DMMAP -D__linux__ -D_BSD_SOURCE -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64   -c dttape.c -o dttape.o
In file included from dt.h:913,
                 from dttape.c:59:
/usr/include/aio.h:175: invalid use of `restrict'
/usr/include/aio.h:189: invalid use of `restrict'

The restrict declarations are wrong - compare these declarations with
the other declarations of lio_listio  and aio_suspend.

The patch is necessary for glibc 2.1.3 and glibc 2.2.

Andreas

1999-12-16  Andreas Jaeger  <aj@suse.de>

	* rt/aio.h: Remove erroneous __restrict declarations.

============================================================
Index: rt/aio.h
--- rt/aio.h	1999/10/09 21:23:31	1.9
+++ rt/aio.h	1999/12/16 17:28:17
@@ -170,7 +170,7 @@
 		       aio_write64);
 
 extern int __REDIRECT (lio_listio,
-		       (int __mode, struct aiocb *__const __restrict __list[],
+		       (int __mode, struct aiocb *__const __list[],
 			int __nent, struct sigevent *__restrict __sig) __THROW,
 		       lio_listio64);
 
@@ -184,7 +184,7 @@
 		       aio_cancel64);
 
 extern int __REDIRECT (aio_suspend,
-		       (__const struct aiocb *__const __restrict __list[],
+		       (__const struct aiocb *__const __list[],
 			int __nent,
 			__const struct timespec *__restrict __timeout) __THROW,
 		       aio_suspend64);

-- 
 Andreas Jaeger
  SuSE Labs aj@suse.de
   private aj@arthur.rhein-neckar.de

                 reply	other threads:[~1999-12-16  9:59 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=u8aena94l2.fsf@gromit.rhein-neckar.de \
    --to=aj@suse.de \
    --cc=libc-hacker@sourceware.cygnus.com \
    /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).