From: "Dave Korn" <dk@artimi.com>
To: "'Diego Novillo'" <dnovillo@redhat.com>
Cc: "'Tal Agmon'" <Tal.Agmon@nsc.com>,
"'Richard Guenther'" <richard.guenther@gmail.com>,
<gcc@gcc.gnu.org>
Subject: RE: A gcc-cris bug?
Date: Wed, 06 Oct 2004 12:48:00 -0000 [thread overview]
Message-ID: <NUTMEGG14dvQO3I9EOl000002b3@NUTMEG.CAM.ARTIMI.COM> (raw)
In-Reply-To: <1097064169.26172.25.camel@localhost.localdomain>
> -----Original Message-----
> From: Diego Novillo
> Sent: 06 October 2004 13:03
> On Wed, 2004-10-06 at 07:45, Dave Korn wrote:
>
> > dk@mace /artimi> time ./foo.exe
> > foo is: 0, i is: 0
> >
> > real 0m3.370s
> > user 0m3.343s
> > sys 0m0.015s
> > dk@mace /artimi>
> >
> Apparently fixed in mainline:
>
> $ time ./a
> foo is: 0, i is: 1
>
> real 0m0.002s
> user 0m0.001s
> sys 0m0.001s
Heh, yeh, I was able to infer from Andrew's source listing that it wasn't
going to take long to execute! :)
Hmm. Bad timing in the release cycle to bring this up though. Might be
worth looking at in time for 3.3.6, though, would be nice to knock it on the
head before the branch gets closed.
cheers,
DaveK
--
Can't think of a witty .sigline today....
next prev parent reply other threads:[~2004-10-06 12:23 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-06 11:37 Tal Agmon
2004-10-06 11:46 ` Richard Guenther
2004-10-06 12:02 ` Tal Agmon
2004-10-06 12:33 ` Dave Korn
2004-10-06 12:36 ` Andrew Pinski
2004-10-06 12:46 ` Diego Novillo
2004-10-06 12:48 ` Dave Korn [this message]
2004-10-06 13:47 ` Richard Guenther
2004-10-06 13:48 ` Andrew Pinski
2004-10-06 13:52 ` Tal Agmon
2004-10-06 13:54 ` Richard Guenther
2004-10-06 13:56 ` Daniel Jacobowitz
2004-10-06 14:48 ` Richard Guenther
2004-10-06 15:00 ` Dave Korn
2004-10-06 15:21 ` Andrew Pinski
2004-10-06 15:33 ` Andrew Pinski
2004-10-06 15:59 ` Dave Korn
2004-10-06 16:57 ` Graham Stott
2004-10-06 18:22 ` Dave Korn
2004-10-06 19:25 ` Graham Stott
2004-10-07 10:30 ` Paolo Bonzini
2004-10-07 10:33 ` Paolo Bonzini
2004-10-07 10:30 ` Richard Guenther
2004-10-15 7:23 ` Hans-Peter Nilsson
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=NUTMEGG14dvQO3I9EOl000002b3@NUTMEG.CAM.ARTIMI.COM \
--to=dk@artimi.com \
--cc=Tal.Agmon@nsc.com \
--cc=dnovillo@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=richard.guenther@gmail.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).