From: Roman Gareev <gareevroman@gmail.com>
To: Tobias Grosser <tobias@grosser.es>
Cc: Mircea Namolaru <mircea.namolaru@inria.fr>, gcc-patches@gcc.gnu.org
Subject: Re: [GSoC] Elimination of CLooG library installation dependency
Date: Wed, 13 Aug 2014 08:07:00 -0000 [thread overview]
Message-ID: <CABGF_geMr1sJ3kvG5ZUdQcd4X+nwmWDMeVYL+_exG4hVQ2F04A@mail.gmail.com> (raw)
In-Reply-To: <CABGF_gcpJKNiN+Km=NOeK15j0DSS3nnhNkKD6xnzeNw3PLQ9pg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1444 bytes --]
If I’m not mistaken all tree nodes, which have pointer type, can be
divided into two groups: the type is a is a pointer to data member
(TYPE_PTRMEM_P is true for it), the type is a pointer type, and the
pointee is not a data member (TYPE_PTR_P is true for it). I think that
we’re interested in disabling of the second group handling. It can
also be divided into two groups: the type is a pointer to function
type (TYPE_PTRFN_P is true for it), the type is a pointer to object
type (TYPE_PTROB_P is true for it). In my opinion, the second one is
worth to be considered. It contains, for example, nop_expr (these
nodes are used to represent conversions that do not require any
code-generation) integer_cst (these nodes represent integer
constants), ssa_name. I haven’t found all types, which are contained
in it. However, I think that we could disable other types, if it is
necessary in the future.
> What we should do later is to build a run-time check that ensures
> no pointer overflow is happening and then just create code without it.
I think that it is better to do this when the pointer handling is completed.
I’ve attached a Change_Log, which corresponds to the previous patch.
Are they fine for trunk? Could we give a headsup on the GCC mailing
list and ask other people to try the new isl support in case this
patch is committed?
--
Cheers, Roman Gareev.
[-- Attachment #2: ChangeLog_entry.txt --]
[-- Type: text/plain, Size: 232 bytes --]
2014-07-12 Roman Gareev <gareevroman@gmail.com>
gcc/
* graphite-scop-detection.c:
Add inclusion of cp-tree.h.
(graphite_can_represent_scev): Disables the handling of SSA_NAME nodes
in case they are pointers to object types.
next prev parent reply other threads:[~2014-08-13 8:07 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-06 15:22 Roman Gareev
2014-08-06 15:48 ` Tobias Grosser
2014-08-07 13:18 ` Roman Gareev
2014-08-07 13:35 ` Tobias Grosser
2014-08-08 13:11 ` Roman Gareev
2014-08-08 13:16 ` Tobias Grosser
2014-08-09 7:42 ` Roman Gareev
2014-08-09 7:52 ` Tobias Grosser
2014-08-09 10:05 ` Roman Gareev
2014-08-11 6:26 ` Tobias Grosser
2014-08-11 7:11 ` Roman Gareev
2014-08-11 7:27 ` Tobias Grosser
2014-08-11 14:20 ` Roman Gareev
2014-08-13 8:07 ` Roman Gareev [this message]
2014-08-13 8:56 ` Tobias Grosser
2014-08-13 11:48 ` Roman Gareev
2014-08-13 9:55 ` Richard Biener
2014-08-13 11:49 ` Roman Gareev
2014-08-15 11:13 ` Roman Gareev
2014-08-15 11:45 ` Richard Biener
2014-08-16 5:28 ` Roman Gareev
2014-08-16 10:40 ` Tobias Grosser
2014-08-18 13:00 ` Richard Biener
2014-08-18 15:22 ` Roman Gareev
2014-08-20 3:28 ` Bin.Cheng
2014-08-20 5:24 ` Roman Gareev
2014-08-20 5:47 ` Bin.Cheng
2014-08-21 5:15 ` Bin.Cheng
2014-08-23 16:48 Dominique d'Humières
2014-08-24 7:00 ` Roman Gareev
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=CABGF_geMr1sJ3kvG5ZUdQcd4X+nwmWDMeVYL+_exG4hVQ2F04A@mail.gmail.com \
--to=gareevroman@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=mircea.namolaru@inria.fr \
--cc=tobias@grosser.es \
/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).