public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "manu at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/47707] Loss of step type precision leads to bad scalar evolution
Date: Sat, 12 Feb 2011 12:01:00 -0000 [thread overview]
Message-ID: <bug-47707-4-efajswNt7Y@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-47707-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47707
Manuel López-Ibáñez <manu at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |manu at gcc dot gnu.org
--- Comment #2 from Manuel López-Ibáñez <manu at gcc dot gnu.org> 2011-02-12 10:24:34 UTC ---
(In reply to comment #1)
> Yeah, signed_type_for isn't really suitable for middle-end use.
And kids, this is what happens when you don't have modularity...
next prev parent reply other threads:[~2011-02-12 10:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-11 20:53 [Bug tree-optimization/47707] New: " xinliangli at gmail dot com
2011-02-11 21:07 ` [Bug tree-optimization/47707] " rguenth at gcc dot gnu.org
2011-02-12 12:01 ` manu at gcc dot gnu.org [this message]
2011-02-14 19:51 ` xinliangli at gmail dot com
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=bug-47707-4-efajswNt7Y@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/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).