public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Sebastian Pop <sebpop@gmail.com>
To: David Edelsohn <dje.gcc@gmail.com>
Cc: Sebastian Pop <s.pop@samsung.com>,
	Richard Biener <richard.guenther@gmail.com>,
		GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] GCC system.h and Graphite header order
Date: Sun, 22 Nov 2015 07:34:00 -0000	[thread overview]
Message-ID: <CAFk3UF9B0vhhM+KynhEs+OVaH-vZMPsOBCXMPhF8BUokJd-WkQ@mail.gmail.com> (raw)
In-Reply-To: <CAGWvnynOFtvdx=h7HnGf+G4wfJMSrUVZZoGnJaB8hHJKM8UAtw@mail.gmail.com>

On Sat, Nov 21, 2015 at 4:03 PM, David Edelsohn <dje.gcc@gmail.com> wrote:
> Graphite relies on the ISL library and includes multiple ISL headers.
> The ISL headers refer to identifiers that are poisoned for use in GCC.
> The source files for Graphite were organized to include the ISL
> headers first, to avoid the identifier poisoning, which breaks some
> platforms because GCC header features are disabled.
>
> This patch reorganizes the graphite*.c header file inclusion order to
> list ISL header files near the end, just before the graphite header
> files on which they rely.  A new macro, USES_ISL, is defined, which
> skips the relevant identifier poisoning, similar to logic for Flex and
> Bison.
>
> This patch also removes early inclusion of stddef.h for ISL because it
> now should be provided by GCC system.h
>
> This has been bootstrapped on powerpc-ibm-aix7.1.0.0
>
> Okay for trunk?
>
> Thanks, David
>
> * system.h: Don't poison calloc and strdup if USES_ISL is defined.
> * graphite-dependences.c: Define USES_ISL.  Include ISL header files
> after GCC header files and before graphite header files.
> * graphite-dependences.c: Same.
> * graphite-isl-ast-to-gimple.c: Same.
> * graphite-optimize-isl.c: Same.
> * graphite-poly.c: Same.
> * graphite-scop-detection.c: Same.
> * graphite-sese-to-poly.c: Same.
> * graphite.c: Same.

The patch looks good to me.  Thanks David for fixing this.

Sebastian

  reply	other threads:[~2015-11-22  3:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-21 22:17 David Edelsohn
2015-11-22  7:34 ` Sebastian Pop [this message]
2015-11-23 10:28   ` Richard Biener
2015-11-24 10:39     ` Alan Lawrence
2015-11-27 16:40       ` Thomas Schwinge
2015-11-27 17:05         ` David Edelsohn
2015-11-30  8:30           ` Thomas Schwinge

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=CAFk3UF9B0vhhM+KynhEs+OVaH-vZMPsOBCXMPhF8BUokJd-WkQ@mail.gmail.com \
    --to=sebpop@gmail.com \
    --cc=dje.gcc@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=richard.guenther@gmail.com \
    --cc=s.pop@samsung.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).