From: Paolo Carlini <paolo.carlini@oracle.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [RFC, WIP] tree-ssa-strlen optimization pass
Date: Fri, 02 Sep 2011 18:42:00 -0000 [thread overview]
Message-ID: <4E612381.8080904@oracle.com> (raw)
In-Reply-To: <20110902182314.GV2687@tyan-ft48-01.lab.bos.redhat.com>
Hi,
> I'm fairly sure it is much less common than the narrow versions,
> we don't even handle wprintf and wscanf attributes.
I know. Actually, the reason I decided to say something, is that I
noticed a few times in the past this "inequality" between char and
wchar_t. Frankly, I instinctively think it's unfortunate, if asked, I
would rather recommend systematically working on *pairs* of
optimizations. I don't know if somebody ever discussed this idea in the
open for GCC, as a matter of "policy" so to speak, but I also don't know
what the other compilers are doing, I don't have much more to say at the
moment. I hope somebody will give the general idea a thought.
Thanks,
Paolo.
next prev parent reply other threads:[~2011-09-02 18:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-02 16:51 Jakub Jelinek
2011-09-02 17:15 ` Paolo Carlini
2011-09-02 18:23 ` Jakub Jelinek
2011-09-02 18:42 ` Paolo Carlini [this message]
2011-09-05 8:55 ` Richard Guenther
2011-09-05 9:41 ` Jakub Jelinek
2011-09-05 9:51 ` Richard Guenther
2011-09-05 18:45 ` Jakub Jelinek
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=4E612381.8080904@oracle.com \
--to=paolo.carlini@oracle.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.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).