From: Paul Richard Thomas <paul.richard.thomas@gmail.com>
To: Richard Guenther <richard.guenther@gmail.com>
Cc: Dominique Dhumieres <dominiq@lps.ens.fr>,
matz@suse.de, gcc-patches@gcc.gnu.org, fortran@gcc.gnu.org
Subject: Re: Implement stack arrays even for unknown sizes
Date: Wed, 13 Apr 2011 13:46:00 -0000 [thread overview]
Message-ID: <BANLkTikSuBmRB4Lgrq=3Wwc-Py7GuGVE+g@mail.gmail.com> (raw)
In-Reply-To: <BANLkTin=O-9Y__Kmue1=sWTCZ-3XiJWOQg@mail.gmail.com>
Dear Richard and Dominique,
> VLAs and malloc based arrays may behave differently with respect to alias
> analysis (I'd have to look at some examples). All effects other than malloc
- hmmm, yes. I was forgetting what might happen with inlining. It's
not evident, is it?
> overhead I would attribute to that. That said, the general idea of the patch
> is sound and I see nothing wrong with it. Both performance improvements
> and regressions are worth looking at - they hint at possible improvements
> in the middle-end parts of the compiler.
I absolutely agree. I realise my input to this thread is possibly a
bit negative but this is far from my reaction to the general idea and
what is evidently within our reach.
Cheers
Paul
next prev parent reply other threads:[~2011-04-13 13:46 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-09 10:08 Dominique Dhumieres
2011-04-09 12:17 ` Paul Richard Thomas
2011-04-10 13:29 ` Dominique Dhumieres
2011-04-11 11:49 ` Michael Matz
2011-04-11 11:58 ` Axel Freyn
2011-04-11 13:35 ` Eric Botcazou
2011-04-11 14:06 ` Dominique Dhumieres
2011-04-11 14:59 ` Michael Matz
2011-04-11 16:04 ` Michael Matz
2011-04-11 16:45 ` Steven Bosscher
2011-04-12 11:54 ` Michael Matz
2011-04-12 12:42 ` N.M. Maclaren
2011-04-11 16:46 ` Dominique Dhumieres
2011-04-11 16:59 ` H.J. Lu
2011-04-11 17:06 ` N.M. Maclaren
2011-04-11 18:28 ` Tobias Burnus
2011-04-11 21:18 ` Dominique Dhumieres
2011-04-12 6:23 ` Paul Richard Thomas
2011-04-12 6:35 ` Dominique Dhumieres
2011-04-13 9:42 ` Paul Richard Thomas
2011-04-13 10:38 ` Richard Guenther
2011-04-13 11:13 ` Richard Guenther
2011-04-14 13:32 ` Dominique Dhumieres
2011-04-13 13:46 ` Paul Richard Thomas [this message]
2011-04-14 13:59 ` Michael Matz
2011-04-14 15:28 ` Michael Matz
2011-04-14 19:29 ` Dominique Dhumieres
2011-04-15 2:01 ` Dominique Dhumieres
2011-04-15 12:38 ` Michael Matz
2011-04-15 14:06 ` Dominique Dhumieres
2011-04-15 15:19 ` Michael Matz
2011-04-15 15:26 ` Jerry DeLisle
2011-04-15 22:41 ` Michael Matz
2011-04-14 20:23 ` Tobias Burnus
2011-04-14 20:30 ` Tobias Burnus
-- strict thread matches above, loose matches on Subject: below --
2011-04-08 21:29 Michael Matz
2011-04-09 8:21 ` N.M. Maclaren
2011-04-09 8:51 ` Magnus Fromreide
2011-04-09 9:02 ` Eric Botcazou
2011-04-09 9:49 ` N.M. Maclaren
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='BANLkTikSuBmRB4Lgrq=3Wwc-Py7GuGVE+g@mail.gmail.com' \
--to=paul.richard.thomas@gmail.com \
--cc=dominiq@lps.ens.fr \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=matz@suse.de \
--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).