public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Sebastian Mach <phresnel@googlemail.com>
To: Dave Korn <dave.korn.cygwin@googlemail.com>
Cc: gcc@gcc.gnu.org
Subject: Re: New g++ template stress/regression test?
Date: Fri, 06 Nov 2009 16:56:00 -0000	[thread overview]
Message-ID: <7f0369b60911060856l41ef7e61jc10f4260b130e87c@mail.gmail.com> (raw)
In-Reply-To: <4AF44D10.7010100@gmail.com>

2009/11/6 Dave Korn <dave.korn.cygwin@googlemail.com>:
>
> [  You should send these emails to the list so that people with maintainer
> rights see the thread - I can't approve contributions myself.  ]

[ facepalm, this is the second time this happens to me, sorry. I will
re-quote for sake of completeness; errors in the following quotes go
at my cost]

>> DaveK wrote:
>>> How big is it?  It might be suitable to go in the contrib/ dir, we already
>>>keep a copy of the paranoia FP tests in there, so your template package and
>>>maybe a testscript to run it and record stats might make a nice little
>>>addition in the same spirit.
>>>
>>>
>Sebastian Mach wrote:
>>Pardon for the inprecise answer (I am relocating at the moment and am
>>posting this from my occupation box), but afair it is somewhere
>>between 1000 or 2000 lines of code, currently it's all in one file,
>>and only invokes standard headers (the output is in ppm format, but
>>arbitrary outputs can be added in a glimpse (like a type-id-name
>>output, e.g.)).
>>
>>Of course the performance is extremely snaily, but I have a small bash
>>script that can utilize all cores and which subdivides the compile
>>into many pieces (as said, performance degrades superlinear w.r.t.
>>type-id count), but still a render of 250x250 pixels took about 26
>>hours. Smaller ones of less than 50x50 can be obtained (as far as I
>>remember) in < 1 hr.
>>
>>

DaveK wrote:
>  It doesn't seem like an excessively large file to me, it's the same scale as
> paranoia.cc; maybe you should just whip it up into a patch and submit it to
> the -patches list.  Add in the script you have, and if you wanted to be really
> comprehensive, include some sample timing runs in the comments showing the
> difference between 4.4 and the (we hope) improvements on HEAD.
>
>    cheers,
>

Many thanks for your help.

So I will see to get that thing ready in the next days (or, who knows,
weeks). Those might be pretty interesting results as for the mentioned
quadratic runtime in 4.4 vs. linear 4.5.

  parent reply	other threads:[~2009-11-06 16:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-06 10:14 Sebastian Mach
2009-11-06 15:12 ` Dave Korn
     [not found]   ` <7f0369b60911060753l1fcd4be1k79ebcb20b24310a1@mail.gmail.com>
     [not found]     ` <4AF44D10.7010100@gmail.com>
2009-11-06 16:56       ` Sebastian Mach [this message]
2009-11-18 20:47   ` Gerald Pfeifer

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=7f0369b60911060856l41ef7e61jc10f4260b130e87c@mail.gmail.com \
    --to=phresnel@googlemail.com \
    --cc=dave.korn.cygwin@googlemail.com \
    --cc=gcc@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).