public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/35629] [4.4 Regression] gcc.dg/tree-ssa/loop-25.c scan-tree-dump-times profile fails
Date: Sun, 20 Apr 2008 20:39:00 -0000 [thread overview]
Message-ID: <20080420203835.14316.qmail@sourceware.org> (raw)
In-Reply-To: <bug-35629-15715@http.gcc.gnu.org/bugzilla/>
--
rguenth at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P2
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35629
next prev parent reply other threads:[~2008-04-20 20:39 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-18 21:03 [Bug c++/35629] New: " jrp at dial dot pipex dot com
2008-03-18 21:33 ` [Bug tree-optimization/35629] [4.4 Regression] " rguenth at gcc dot gnu dot org
2008-03-18 21:33 ` [Bug tree-optimization/35629] " rguenth at gcc dot gnu dot org
2008-03-19 3:07 ` [Bug tree-optimization/35629] [4.4 Regression] " hp at gcc dot gnu dot org
2008-03-19 6:59 ` ubizjak at gmail dot com
2008-03-19 13:23 ` hjl dot tools at gmail dot com
2008-03-19 22:58 ` danglin at gcc dot gnu dot org
2008-03-19 23:07 ` hubicka at ucw dot cz
2008-04-10 0:04 ` hp at gcc dot gnu dot org
2008-04-16 2:45 ` hp at gcc dot gnu dot org
2008-04-20 20:39 ` rguenth at gcc dot gnu dot org [this message]
2008-12-04 12:37 ` jakub at gcc dot gnu dot org
2009-01-30 8:01 ` hubicka at gcc dot gnu dot org
2009-04-21 16:02 ` [Bug tree-optimization/35629] [4.4/4.5 " jakub at gcc dot gnu dot org
2009-07-22 10:33 ` jakub at gcc dot gnu dot org
2009-10-15 12:54 ` jakub at gcc dot gnu dot org
2010-01-21 13:18 ` jakub at gcc dot gnu dot org
2010-04-30 8:59 ` [Bug tree-optimization/35629] [4.4/4.5/4.6 " jakub 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=20080420203835.14316.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).