public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Biener <richard.guenther@gmail.com>
To: Richard Sandiford <richard.sandiford@arm.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: Replace match.pd DEFINE_MATH_FNs with auto-generated lists
Date: Tue, 10 Nov 2015 20:24:00 -0000	[thread overview]
Message-ID: <37FBF7EA-03D3-4C49-A69C-534CA996266F@gmail.com> (raw)
In-Reply-To: <87bnb1mx3u.fsf@e105548-lin.cambridge.arm.com>

On November 10, 2015 9:13:25 PM GMT+01:00, Richard Sandiford <richard.sandiford@arm.com> wrote:
>Richard Biener <richard.guenther@gmail.com> writes:
>> On Sat, Nov 7, 2015 at 2:23 PM, Richard Sandiford
>> <richard.sandiford@arm.com> wrote:
>>> diff --git a/gcc/genmatch.c b/gcc/genmatch.c
>>> index cff32b0..7139476 100644
>>> --- a/gcc/genmatch.c
>>> +++ b/gcc/genmatch.c
>>> @@ -4638,6 +4638,11 @@ main (int argc, char **argv)
>>>    cpp_callbacks *cb = cpp_get_callbacks (r);
>>>    cb->error = error_cb;
>>>
>>> +  /* Add the build directory to the #include "" search path.  */
>>> +  cpp_dir *dir = XCNEW (cpp_dir);
>>> +  dir->name = ASTRDUP (".");
>>> +  cpp_set_include_chains (r, dir, NULL, false);
>>
>> Does that work on non-UNIX hosts?
>
>Bah, hadn't thought about that.
>
>> I wonder if there is sth
>> better we can use by passing some -DXXX=... to the genmatch
>> build command from the Makefile?
>
>toplev.c has:
>
>      src_pwd = getpwd ();
>      if (!src_pwd)
>	src_pwd = ".";
>
>where getpwd is a libiberty function.  Maybe we can use that?

Looks like so.

Richard.

>Thanks,
>Richard


  reply	other threads:[~2015-11-10 20:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-07 13:23 Richard Sandiford
2015-11-10 11:24 ` Richard Biener
2015-11-10 20:13   ` Richard Sandiford
2015-11-10 20:24     ` Richard Biener [this message]
2015-11-17  9:23       ` Richard Sandiford
2015-11-17 14:32         ` Richard Biener

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=37FBF7EA-03D3-4C49-A69C-534CA996266F@gmail.com \
    --to=richard.guenther@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=richard.sandiford@arm.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).