public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/26304] [4.2 Regression] 25_algorithms/prev_permutation/1.cc on powerpc{64,}-linux and powerpc-darwin
Date: Thu, 16 Feb 2006 02:59:00 -0000 [thread overview]
Message-ID: <20060216025929.19391.qmail@sourceware.org> (raw)
In-Reply-To: <bug-26304-133@http.gcc.gnu.org/bugzilla/>
------- Comment #9 from pinskia at gcc dot gnu dot org 2006-02-16 02:59 -------
(In reply to comment #8)
> > Which looks more like VRP messing up.
> Can you check something for me. Is sizetype an unsigned type on
> this platform? And what type is ivtmp?
sizetype should be "unsigned long int" but I am not 100% sure.
unsigned int ivtmp.60;
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26304
next prev parent reply other threads:[~2006-02-16 2:59 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-15 14:01 [Bug target/26304] New: 25_algorithms/prev_permutation/1.cc on powerpc64-linux pcarlini at suse dot de
2006-02-15 14:02 ` [Bug target/26304] " pcarlini at suse dot de
2006-02-15 14:07 ` pinskia at gcc dot gnu dot org
2006-02-15 14:14 ` [Bug target/26304] [4.2 Regression] 25_algorithms/prev_permutation/1.cc on powerpc{64,}-linux and powerpc-darwin pinskia at gcc dot gnu dot org
2006-02-15 15:19 ` [Bug tree-optimization/26304] " pinskia at gcc dot gnu dot org
2006-02-15 15:19 ` pinskia at gcc dot gnu dot org
2006-02-15 15:23 ` pinskia at gcc dot gnu dot org
2006-02-15 15:26 ` pinskia at gcc dot gnu dot org
2006-02-15 15:37 ` pinskia at gcc dot gnu dot org
2006-02-15 23:34 ` law at redhat dot com
2006-02-16 2:59 ` pinskia at gcc dot gnu dot org [this message]
2006-02-16 3:52 ` law at redhat dot com
2006-02-17 0:19 ` law at redhat dot com
2006-02-17 1:17 ` pinskia at gcc dot gnu dot org
2006-02-17 2:47 ` law at redhat dot com
2006-02-17 3:37 ` pinskia at gcc dot gnu dot org
2006-02-20 17:50 ` pinskia at gcc dot gnu dot org
2006-03-28 20:20 ` pcarlini at suse dot de
2006-04-18 16:23 ` janis at gcc dot gnu dot org
2006-04-23 23:14 ` pinskia at gcc dot gnu dot org
2006-04-24 1:10 ` Daniel Berlin
2006-04-23 23:15 ` pinskia at gcc dot gnu dot org
2006-04-24 1:10 ` dberlin at dberlin dot org
2006-05-02 5:55 ` pinskia at gcc dot gnu dot org
2006-05-02 6:14 ` pinskia at gcc dot gnu dot org
2006-05-02 7:56 ` rakdver at gcc dot gnu dot org
2006-05-02 8:57 ` rakdver at gcc dot gnu dot org
2006-05-08 11:18 ` rakdver at gcc dot gnu dot org
2006-05-16 6:11 ` pinskia at gcc dot gnu dot org
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=20060216025929.19391.qmail@sourceware.org \
--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).