From: "Anatoly Sokolov" <aesok@post.ru>
To: "Richard Guenther" <richard.guenther@gmail.com>
Cc: <gcc-patches@gcc.gnu.org>, <java-patches@gcc.gnu.org>
Subject: Re: Remove build_int_cst_wide_type function.
Date: Mon, 10 May 2010 11:47:00 -0000 [thread overview]
Message-ID: <830AA1A9F7C14F1AB2FE926D7AF412E7@Vista> (raw)
In-Reply-To: <AANLkTileuJOIIVIv5ndBSdH9tEKRf2ec94RnlIvGSoct@mail.gmail.com>
----- Original Message -----
From: "Richard Guenther" <richard.guenther@gmail.com>
To: "Anatoly Sokolov" <aesok@post.ru>
Cc: <gcc-patches@gcc.gnu.org>; <java-patches@gcc.gnu.org>
Sent: Monday, May 10, 2010 3:35 PM
Subject: Re: Remove build_int_cst_wide_type function.
> The callers with NULL type should probably be reviewed separately.
> Some of them might want to use the simpler size_int interface
> (even if that changes the type from integer_type_node to
> size_type_node). Some obvious ones indeed explicitly want
> integer_type_node.
>
> Lumping both changes together will make it hard to track down
> those persisting errors. NULL_TREE at least tells us that this
> is a suspicious case.
Ok. I'm working on these patches.
Anatoly.
next prev parent reply other threads:[~2010-05-10 11:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-07 18:59 Anatoly Sokolov
2010-05-07 20:31 ` Richard Guenther
2010-05-10 9:24 ` Anatoly Sokolov
2010-05-10 9:34 ` Richard Guenther
2010-05-10 10:24 ` Anatoly Sokolov
2010-05-10 10:34 ` Richard Guenther
2010-05-10 11:17 ` Anatoly Sokolov
2010-05-10 11:35 ` Richard Guenther
2010-05-10 11:47 ` Anatoly Sokolov [this message]
2010-05-19 20:00 ` Re[2]: " Anatoly Sokolov
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=830AA1A9F7C14F1AB2FE926D7AF412E7@Vista \
--to=aesok@post.ru \
--cc=gcc-patches@gcc.gnu.org \
--cc=java-patches@gcc.gnu.org \
--cc=richard.guenther@gmail.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).