From: "Daniel Berlin" <dberlin@dberlin.org>
To: "Sebastian Pop" <sebpop@gmail.com>
Cc: "Dorit Nuzman" <DORIT@il.ibm.com>, gcc@gcc.gnu.org
Subject: Re: Some thoughts about steerring commitee work
Date: Mon, 18 Jun 2007 18:10:00 -0000 [thread overview]
Message-ID: <4aca3dc20706181045x5b60460dya6bb008b550c03c9@mail.gmail.com> (raw)
In-Reply-To: <cb9d34b20706181033p727c14fx3513de0081e5c835@mail.gmail.com>
On 6/18/07, Sebastian Pop <sebpop@gmail.com> wrote:
> On 6/18/07, Dorit Nuzman <DORIT@il.ibm.com> wrote:
> > > I can hand you more than the testcases i've given so far. There is
> > > tons of code out there that would benefit from straight line
> >
> > Interesting. I wasn't aware of this potential. Please do send some of this
> > code. thanks!
> >
>
> I'm thinking about loops whose bodies contain a call that is not
> inlined, so the code in that function looks like stright line code,
> but in fact is called from inside a loop. This could happen even
> because the compiler decided to outline the body of some loop, as
> the case for the openMP code gen, or autoparallelization.
>
This is in fact, most of the code i will send to dorit.
It is, IMHO, not reasonable, to say that we should inline everything
that may ever turn out to be vectorizable :)
If you throw virtual functions into the mix, it may not even be possible ;)
next prev parent reply other threads:[~2007-06-18 17:45 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-17 13:59 Ira Rosen
2007-06-17 16:11 ` Daniel Berlin
2007-06-18 10:59 ` Dorit Nuzman
2007-06-18 12:01 ` Daniel Berlin
2007-06-18 12:53 ` Dorit Nuzman
2007-06-18 17:57 ` Sebastian Pop
2007-06-18 18:10 ` Daniel Berlin [this message]
2007-06-18 20:54 ` Jagasia, Harsha
-- strict thread matches above, loose matches on Subject: below --
2007-06-25 13:07 Mircea Namolaru
2007-06-18 17:16 Devang Patel
2007-06-16 2:03 J.C. Pizarro
2007-06-16 2:43 ` Ian Lance Taylor
2007-06-16 3:32 ` Richard Kenner
2007-06-16 19:08 ` Joe Buck
2007-06-14 10:37 Diego Novillo appointed middle-end maintainer and non-algorithmic GWP David Edelsohn
2007-06-15 12:49 ` Some thoughts about steerring commitee work Vladimir N. Makarov
2007-06-15 13:05 ` Richard Kenner
2007-06-15 13:58 ` Vladimir N. Makarov
2007-06-15 17:07 ` Joe Buck
2007-06-15 17:48 ` Vladimir N. Makarov
2007-06-15 17:56 ` Joe Buck
2007-09-09 20:24 ` Gerald Pfeifer
2007-06-15 18:43 ` Ian Lance Taylor
2007-06-15 19:28 ` Vladimir N. Makarov
2007-06-15 19:41 ` Ian Lance Taylor
2007-06-15 20:55 ` Vladimir N. Makarov
2007-06-15 21:08 ` Eric Botcazou
2007-06-15 21:13 ` Daniel Berlin
2007-06-15 21:43 ` Eric Botcazou
2007-06-15 22:16 ` Vladimir N. Makarov
2007-06-15 23:04 ` Richard Kenner
2007-06-15 21:36 ` Vladimir N. Makarov
2007-06-16 0:51 ` Tobias Burnus
2007-06-17 14:33 ` Paolo Bonzini
2007-06-16 1:43 ` Ian Lance Taylor
2007-06-16 2:02 ` H. J. Lu
2007-06-16 2:19 ` Andrew Pinski
2007-06-16 13:25 ` H. J. Lu
2007-06-16 3:33 ` Vladimir N. Makarov
2007-06-16 15:04 ` H. J. Lu
2007-06-16 16:13 ` Dorit Nuzman
2007-06-17 0:48 ` H. J. Lu
2007-06-17 1:16 ` Tim Prince
2007-06-17 8:30 ` Dorit Nuzman
2007-06-16 15:53 ` Dorit Nuzman
2007-06-16 16:46 ` Daniel Berlin
2007-06-16 15:29 ` Dorit Nuzman
2007-06-16 23:59 ` Ryan Hill
2007-06-17 10:44 ` Dorit Nuzman
2007-06-17 14:52 ` Ryan Hill
2007-06-18 10:47 ` Dorit Nuzman
2007-06-16 3:08 ` Vladimir N. Makarov
2007-06-16 3:36 ` Richard Kenner
2007-06-16 1:54 ` Ian Lance Taylor
2007-06-16 3:28 ` Vladimir N. Makarov
2007-06-16 3:45 ` Richard Kenner
2007-06-16 15:20 ` Joel Sherrill
2007-06-18 23:12 ` Mark Mitchell
2007-06-19 21:01 ` Toon Moene
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=4aca3dc20706181045x5b60460dya6bb008b550c03c9@mail.gmail.com \
--to=dberlin@dberlin.org \
--cc=DORIT@il.ibm.com \
--cc=gcc@gcc.gnu.org \
--cc=sebpop@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).