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] generation of Gimple loops with empty bodies
Date: Tue, 15 Jul 2014 15:19:00 -0000 [thread overview]
Message-ID: <CABGF_gcb3H2z6nc_n4nEY32rXajhO_jk4ZOf1D0dW8MR92MDcQ@mail.gmail.com> (raw)
In-Reply-To: <53C29C5A.1070808@grosser.es>
I've found out that int128_integer_type_node and
long_long_integer_type_node are NULL at the moment of definition of
the graphite_expression_size_type. Maybe we should use
long_long_integer_type_node, because, as you said before, using of
signed 64 has also been proved to be very robust. What do you think
about this?
--
Cheers, Roman Gareev.
next prev parent reply other threads:[~2014-07-15 15:03 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-12 10:13 Dominique Dhumieres
2014-07-13 10:34 ` Roman Gareev
2014-07-13 12:35 ` Dominique Dhumieres
2014-07-13 13:14 ` Dominique Dhumieres
2014-07-13 14:49 ` Tobias Grosser
2014-07-15 15:19 ` Roman Gareev [this message]
[not found] ` <53C54C7E.5050102@grosser.es>
[not found] ` <CAFiYyc1LoP1VDX57CmV_mdULBAObGzvmwtJ1zQxOA78HDbHSKA@mail.gmail.com>
[not found] ` <53C7DB6F.1050707@grosser.es>
2014-07-18 10:52 ` Roman Gareev
2014-07-18 11:28 ` Tobias Grosser
-- strict thread matches above, loose matches on Subject: below --
2014-07-05 7:06 Roman Gareev
2014-07-07 11:11 ` Tobias Grosser
2014-07-08 12:47 ` Roman Gareev
2014-07-08 13:18 ` Tobias Grosser
2014-07-11 9:01 ` Roman Gareev
2014-07-11 9:18 ` Tobias Grosser
2014-07-11 11:11 ` Roman Gareev
2014-07-11 11:15 ` Tobias Grosser
2014-07-11 13:42 ` Roman Gareev
2014-07-11 13:44 ` Tobias Grosser
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_gcb3H2z6nc_n4nEY32rXajhO_jk4ZOf1D0dW8MR92MDcQ@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).