public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vanboxem.ruben at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/50156] in-tree CLooG is not picked up by toplevel configure
Date: Wed, 24 Aug 2011 19:29:00 -0000	[thread overview]
Message-ID: <bug-50156-4-wJam8BVNx9@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-50156-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50156

--- Comment #2 from Ruben Van Boxem <vanboxem.ruben at gmail dot com> 2011-08-24 19:26:55 UTC ---
Created attachment 25090
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=25090
Patch to allow a non-bootstrap compiler to build with in tree prereqs for
graphite

Attached is a full patch (including manual changes to generated files) that
allow for in-tree CLooG (isl) to be used to build a GCC with Graphite.

This patch was made against GCC 4.6 (SVN) and should apply cleanly for testing
purposes.

I have not "ported" the configure bit for CLooG to configure.ac, the rest (in
configure and makefile.in) should be matched by makefile.def and configure.ac
changes.


  parent reply	other threads:[~2011-08-24 19:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-22 19:08 [Bug bootstrap/50156] New: " vanboxem.ruben at gmail dot com
2011-08-22 19:08 ` [Bug bootstrap/50156] " vanboxem.ruben at gmail dot com
2011-08-24 19:29 ` vanboxem.ruben at gmail dot com [this message]
2011-08-24 20:48 ` vanboxem.ruben at gmail dot com
2014-12-30 12:37 ` manu at gcc dot gnu.org
2014-12-30 12:42 ` manu at gcc dot gnu.org

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=bug-50156-4-wJam8BVNx9@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /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).