From: Sebastian Pop <sebpop@gmail.com>
To: Aditya K <hiraditya@msn.com>
Cc: David Edelsohn <dje.gcc@gmail.com>,
Aditya Kumar <aditya.k7@samsung.com>,
Sebastian Pop <s.pop@samsung.com>,
GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH 1/2] [graphite] Move codegen related functions to graphite-isl-ast-to-gimple.c
Date: Thu, 19 Nov 2015 20:37:00 -0000 [thread overview]
Message-ID: <20151119203733.GA395@f1.c.bardezibar.internal> (raw)
In-Reply-To: <BLU179-W597C1632A71D1398F738DCB61B0@phx.gbl>
Fixed in r230625.
David, please test on your systems, we were not able to reproduce the fails on
x86_64-linux: the linker does optimize away the functions that are not used.
Thanks,
Sebastian
Aditya K wrote:
> Thanks for the update. I'll fix that asap.
>
>
> -Aditya
>
>
> ----------------------------------------
> > Date: Thu, 19 Nov 2015 08:36:58 -0500
> > Subject: Re: [PATCH 1/2] [graphite] Move codegen related functions to graphite-isl-ast-to-gimple.c
> > From: dje.gcc@gmail.com
> > To: hiraditya@msn.com; aditya.k7@samsung.com; s.pop@samsung.com
> > CC: gcc-patches@gcc.gnu.org
> >
> > This patch broke bootstrap when ISL is not enabled.
> >
> > graphite-isl-ast-to-gimple.c is protected by HAVE_isl but
> > get_false_edge_from_guard_bb() is used outside of Graphite, including
> > sese.c, which is not restricted to HAVE_isl.
> >
> > Please fix.
> >
> > Thanks, David
>
next prev parent reply other threads:[~2015-11-19 20:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-19 13:37 David Edelsohn
2015-11-19 15:03 ` Aditya K
2015-11-19 20:37 ` Sebastian Pop [this message]
2015-11-20 4:42 ` David Edelsohn
-- strict thread matches above, loose matches on Subject: below --
2015-11-14 21:36 A.K.
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=20151119203733.GA395@f1.c.bardezibar.internal \
--to=sebpop@gmail.com \
--cc=aditya.k7@samsung.com \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hiraditya@msn.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).