All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v6 3/3] Add an BR2_GCC_ENABLE_GRAPHITE flag for the buildroot toolchain
Date: Fri, 30 May 2014 09:30:59 -0300	[thread overview]
Message-ID: <53887A03.90001@zacarias.com.ar> (raw)
In-Reply-To: <BLU436-SMTP1389119D64FEA33BF25D8E5A8320@phx.gbl>

On 05/19/2014 04:48 PM, Steve Thomas wrote:
> +ifeq ($(BR2_GCC_ENABLE_GRAPHITE),y)
> +HOST_GCC_COMMON_DEPENDENCIES += \
> +   host-isl \
> +   host-cloog
> +
> +#This is needed as with-isl doesn't work
> +HOST_GCC_COMMON_CONF_OPT += \
> +   --disable-isl-version-check
> +endif

Hi.
Hidden option?
How about adding something like:

config BR2_GCC_ENABLE_GRAPHITE
        bool "Enable graphite loop optimizations"
        depends on BR2_GCC_SUPPORTS_GRAPHITE
        help
          Enable the support for the framework for loop optimizations
          based on a polyhedral intermediate representation.

...to package/gcc/Config.in.host before BR2_GCC_ENABLE_TLS ?
Regards.

  reply	other threads:[~2014-05-30 12:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1400528893-4483-1-git-send-email-scjthm@live.com>
2014-05-19 19:48 ` [Buildroot] [PATCH v6 1/3] isl: new package Steve Thomas
2014-06-09  9:53   ` Thomas Petazzoni
2014-05-19 19:48 ` [Buildroot] [PATCH v6 2/3] cloog: " Steve Thomas
2014-06-09  9:57   ` Thomas Petazzoni
2014-05-19 19:48 ` [Buildroot] [PATCH v6 3/3] Add an BR2_GCC_ENABLE_GRAPHITE flag for the buildroot toolchain Steve Thomas
2014-05-30 12:30   ` Gustavo Zacarias [this message]
2014-06-09  9:58   ` Thomas Petazzoni

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=53887A03.90001@zacarias.com.ar \
    --to=gustavo@zacarias.com.ar \
    --cc=buildroot@busybox.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.