This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [GSoC] How to get started with the isl code generation


Hi Tobias,

I made a separate patch and rebased the previous one. They are
attached to this letter.


> I am surprised. Are all these includes really needed to get _this_ patch
> compile? (I asked this before).

I saw your previous comment related to this and the following includes
were removed: isl/list.h, isl/constraint.h, isl/ilp.h, isl/aff.h,
diagnostic-core.h, tree-ssa-loop-manip.h, tree-into-ssa.h,
tree-chrec.h, tree-scalar-evolution.h.

However, it seems that if we want to use the struct scop_p from
graphite-poly.h, we have to include sese.h, which requires
tree-data-ref.h, cfgloop.h, tree-ssa-loop.h, gimple-iterator.h,
gimple.h, is-a.h, gimple-expr.h, internal-fn.h, tree-ssa-alias.h,
basic-block.h, tree.h, coretypes.h, system.h, config.h

We also have to include tree-pass.h, if we want to use timevar_push,
timevar_pop to to measure elapsed time (it was used previously by
graphite-clast-to-gimple.c).

> This is ugly, but there is little we can do about it. Maybe you can ask
> on the mailing list if there is a way to write this in multiple lines?

The patch was reduced, but I didn't found out how to make the regexp
easier to read. I wrote about this to the community.


-- 
                                   Cheers, Roman Gareev

Attachment: ChangeLog_entry1
Description: Binary data

Attachment: ChangeLog_entry2
Description: Binary data

Attachment: patch1
Description: Binary data

Attachment: patch2
Description: Binary data


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]