public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dberlin at dberlin dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/19794] [meta-bug] Jump threading related bugs
Date: Wed, 06 Apr 2005 02:05:00 -0000 [thread overview]
Message-ID: <20050406020514.514.qmail@sourceware.org> (raw)
In-Reply-To: <20050206175258.19794.kazu@cs.umass.edu>
------- Additional Comments From dberlin at gcc dot gnu dot org 2005-04-06 02:05 -------
Subject: Re: [meta-bug] Jump threading
related bugs
On Wed, 2005-04-06 at 00:25 +0000, law at redhat dot com wrote:
> ------- Additional Comments From law at redhat dot com 2005-04-06 00:25 -------
> Just more notes on the huge perl speedup with the threading changes...
>
Have you tried on non-x86 to see if the results bear out on other
platforms?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19794
next prev parent reply other threads:[~2005-04-06 2:05 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-06 17:53 [Bug tree-optimization/19794] New: " kazu@cs.umass.edu
2005-02-06 17:55 ` [Bug tree-optimization/19794] " kazu@cs.umass.edu
2005-02-07 1:52 ` kazu at cs dot umass dot edu
2005-02-07 1:52 ` kazu at cs dot umass dot edu
2005-02-07 1:54 ` kazu at cs dot umass dot edu
2005-02-07 1:58 ` kazu at cs dot umass dot edu
2005-02-07 2:04 ` kazu at cs dot umass dot edu
2005-02-07 2:05 ` kazu at cs dot umass dot edu
2005-02-07 2:08 ` pinskia at gcc dot gnu dot org
2005-02-07 15:30 ` kazu at cs dot umass dot edu
2005-02-14 0:19 ` kazu at cs dot umass dot edu
2005-02-14 0:49 ` kazu at cs dot umass dot edu
2005-02-25 22:48 ` kazu at cs dot umass dot edu
2005-03-16 19:25 ` law at redhat dot com
2005-03-22 17:12 ` law at redhat dot com
2005-04-02 1:31 ` law at redhat dot com
2005-04-06 0:26 ` law at redhat dot com
2005-04-06 2:05 ` dberlin at dberlin dot org [this message]
2005-04-06 3:22 ` law at redhat dot com
2005-04-06 6:38 ` pinskia at gcc dot gnu dot org
2005-04-06 17:41 ` law at redhat dot com
2005-04-06 19:21 ` law at redhat dot com
2005-04-08 18:19 ` law at redhat dot com
2005-04-19 17:59 ` law at redhat dot com
2005-04-22 18:30 ` law at redhat dot com
2005-04-23 16:47 ` steven at gcc dot gnu dot org
2005-04-23 16:58 ` steven at gcc dot gnu dot org
2005-04-25 4:57 ` law at redhat dot com
2005-04-25 4:58 ` law at redhat dot com
2005-04-25 5:05 ` law at redhat dot com
2005-04-25 5:07 ` law at redhat dot com
2005-05-08 18:05 ` pinskia at gcc dot gnu dot org
[not found] <20050206175258.19794.kazu@gcc.gnu.org>
2005-07-25 17:13 ` pinskia at gcc dot gnu dot org
[not found] <bug-19794-4@http.gcc.gnu.org/bugzilla/>
2013-09-17 20:46 ` law at redhat dot com
2013-11-19 22:19 ` law at redhat dot com
2013-11-19 22:23 ` law at redhat dot com
2013-11-22 19:32 ` law at redhat dot com
2013-11-27 12:15 ` jgreenhalgh at gcc dot gnu.org
2014-12-06 19:24 ` spop at gcc dot gnu.org
2021-03-29 21:16 ` msebor at gcc dot gnu.org
2022-11-20 4:16 ` law at gcc dot gnu.org
2024-02-20 14:02 ` rguenth at gcc dot gnu.org
2024-03-16 23:48 ` pinskia at gcc dot gnu.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=20050406020514.514.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).