From: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>
To: Ajit Kumar Agarwal
<ajit.kumar.agarwal@xilinx.com>,"law@redhat.com"
<law@redhat.com>,GCC Patches <gcc-patches@gcc.gnu.org>
Cc: Vinod Kathail <vinodk@xilinx.com>,Shail Aditya Gupta
<shailadi@xilinx.com>,Vidhumouli Hunsigida
<vidhum@xilinx.com>,Nagaraju Mekala <nmekala@xilinx.com>
Subject: RE: [Patch,tree-optimization]: Add new path Splitting pass on tree ssa representation
Date: Tue, 30 Jun 2015 10:51:00 -0000 [thread overview]
Message-ID: <CD7E7C87-8900-429B-AFE6-69848C119B45@gmail.com> (raw)
In-Reply-To: <37378DC5BCD0EE48BA4B082E0B55DFAA41F3F634@XAP-PVEXMBX02.xlnx.xilinx.com>
On June 30, 2015 12:38:13 PM GMT+02:00, Ajit Kumar Agarwal <ajit.kumar.agarwal@xilinx.com> wrote:
>>6. Added 2 tests.
>> a) compilation check tests.
>> b) execution tests.
>
>>>The 2 tests seem to be identical, so why do you have both?
>>>Also, please remove cleanup-tree-dump, this is now done
>automatically.
>
>The testcase path-split-1.c is to check for execution which is present
>in gcc.dg top directory . The one
>present in the gcc.dg/tree-ssa/path-split-2.c is to check the
>compilation as the action item is compilation. For the
>execution tests path-split-1.c the action is compile and run.
One is a superset of the other, no?
Doesn't make sense to me, fwiw.
next prev parent reply other threads:[~2015-06-30 10:43 UTC|newest]
Thread overview: 72+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-30 8:34 Ajit Kumar Agarwal
2015-06-30 10:38 ` Bernhard Reutner-Fischer
2015-06-30 10:43 ` Ajit Kumar Agarwal
2015-06-30 10:51 ` Bernhard Reutner-Fischer [this message]
2015-06-30 11:39 ` Richard Biener
2015-06-30 12:07 ` Ajit Kumar Agarwal
2015-07-04 12:40 ` Ajit Kumar Agarwal
2015-07-07 8:50 ` Richard Biener
2015-07-07 13:22 ` Ajit Kumar Agarwal
2015-07-16 11:20 ` Richard Biener
2015-07-29 7:44 ` Ajit Kumar Agarwal
2015-08-15 23:13 ` Ajit Kumar Agarwal
2015-08-19 19:47 ` Jeff Law
2015-08-20 15:40 ` Ajit Kumar Agarwal
2015-08-20 15:49 ` Jeff Law
2015-08-27 6:00 ` Ajit Kumar Agarwal
2015-09-09 21:45 ` Jeff Law
2015-09-12 12:05 ` Ajit Kumar Agarwal
2015-10-20 16:05 ` Ajit Kumar Agarwal
2015-11-11 7:01 ` Jeff Law
2015-08-19 21:53 ` Jeff Law
2015-08-20 15:41 ` Ajit Kumar Agarwal
2015-09-04 18:07 ` Ajit Kumar Agarwal
2015-11-11 20:38 ` Jeff Law
2015-11-12 10:58 ` Richard Biener
2015-11-12 17:05 ` Jeff Law
2015-11-12 18:33 ` Jeff Law
2015-11-12 19:40 ` Richard Biener
2015-11-12 19:52 ` Jeff Law
2015-11-12 21:58 ` Jeff Law
2015-11-13 10:13 ` Richard Biener
2015-11-13 16:26 ` Jeff Law
2015-11-13 18:09 ` Richard Biener
2015-11-13 20:23 ` Jeff Law
2015-11-13 23:36 ` Jeff Law
2015-11-18 7:44 ` Tom de Vries
2015-11-18 14:24 ` Ajit Kumar Agarwal
2015-12-03 14:38 ` Richard Biener
2015-12-03 14:45 ` Richard Biener
2015-12-10 20:12 ` Jeff Law
2015-12-03 15:46 ` Jeff Law
2015-12-10 20:08 ` Jeff Law
2015-12-11 9:11 ` Ajit Kumar Agarwal
2015-12-23 6:36 ` Jeff Law
2015-12-25 8:40 ` Ajit Kumar Agarwal
2016-01-02 7:32 ` Jeff Law
2016-01-04 14:32 ` Ajit Kumar Agarwal
2016-01-13 8:10 ` Jeff Law
[not found] ` <56976289.3080203@redhat.com! >
2016-01-14 8:55 ` Jeff Law
2016-01-15 23:02 ` Jeff Law
2016-01-18 18:27 ` Ajit Kumar Agarwal
2016-01-27 7:17 ` Jeff Law
2016-01-27 17:21 ` Ajit Kumar Agarwal
2016-01-15 22:38 ` Jeff Law
2016-01-16 6:32 ` Jeff Law
2016-01-18 9:13 ` Ajit Kumar Agarwal
2016-01-27 7:13 ` Jeff Law
2016-01-27 9:35 ` Ajit Kumar Agarwal
2016-02-04 8:57 ` Jeff Law
2015-12-11 10:06 ` Richard Biener
2015-12-15 23:50 ` Jeff Law
2015-12-16 7:44 ` Ajit Kumar Agarwal
2015-12-16 9:57 ` Richard Biener
2015-12-16 10:13 ` Ajit Kumar Agarwal
2015-12-17 10:38 ` Ajit Kumar Agarwal
2015-12-17 23:41 ` Jeff Law
2015-12-18 15:43 ` Zamyatin, Igor
2015-11-13 13:19 ` Ajit Kumar Agarwal
2015-06-30 12:39 ` Ajit Kumar Agarwal
2015-06-30 22:18 ` Joseph Myers
2015-07-02 3:52 ` Ajit Kumar Agarwal
2015-07-06 20:08 ` Jeff Law
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=CD7E7C87-8900-429B-AFE6-69848C119B45@gmail.com \
--to=rep.dot.nop@gmail.com \
--cc=ajit.kumar.agarwal@xilinx.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=law@redhat.com \
--cc=nmekala@xilinx.com \
--cc=shailadi@xilinx.com \
--cc=vidhum@xilinx.com \
--cc=vinodk@xilinx.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).