* [RFA] __restrict_arr
@ 2002-07-18 5:11 Michal Ludvig
2002-07-18 9:47 ` Andrew Cagney
0 siblings, 1 reply; 2+ messages in thread
From: Michal Ludvig @ 2002-07-18 5:11 UTC (permalink / raw)
To: GDB Patches
[-- Attachment #1: Type: text/plain, Size: 329 bytes --]
Hi all,
in GCC 3.1 the symbol __restrict_arr is already defined and doesn't need
to be redegined in include/xregex2.h. So I wrapped it into a condition.
It prevents compiler from complaining. Any objections or can I commit it?
Michal Ludvig
--
* SuSE CR, s.r.o * mludvig@suse.cz
* +420 2 9654 5373 * http://www.suse.cz
[-- Attachment #2: rarr-1.diff --]
[-- Type: text/plain, Size: 777 bytes --]
2002-07-17 Michal Ludvig <mludvig@suse.cz>
* include/xregex2.h: Wrap __restrict_arr between #ifndef/#endif.
Index: include/xregex2.h
===================================================================
RCS file: /cvs/src/src/include/xregex2.h,v
retrieving revision 1.2
diff -u -p -r1.2 xregex2.h
--- include/xregex2.h 19 Jul 2001 00:04:11 -0000 1.2
+++ include/xregex2.h 18 Jul 2002 11:31:36 -0000
@@ -532,7 +532,9 @@ extern int re_exec _RE_ARGS ((const char
/* For now unconditionally define __restrict_arr to expand to nothing.
Ideally we would have a test for the compiler which allows defining
it to restrict. */
+#ifndef __restrict_arr
#define __restrict_arr
+#endif
/* POSIX compatibility. */
extern int regcomp _RE_ARGS ((regex_t *__restrict __preg,
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2002-07-18 16:36 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2002-07-18 5:11 [RFA] __restrict_arr Michal Ludvig
2002-07-18 9:47 ` Andrew Cagney
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox