Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michal Ludvig <mludvig@suse.cz>
To: GDB Patches <gdb-patches@sources.redhat.com>
Subject: [RFA] __restrict_arr
Date: Thu, 18 Jul 2002 05:11:00 -0000	[thread overview]
Message-ID: <3D36AA1B.1000103@suse.cz> (raw)

[-- 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,

             reply	other threads:[~2002-07-18 11:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-18  5:11 Michal Ludvig [this message]
2002-07-18  9:47 ` Andrew Cagney

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=3D36AA1B.1000103@suse.cz \
    --to=mludvig@suse.cz \
    --cc=gdb-patches@sources.redhat.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