public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "paolo dot carlini at oracle dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/33485] parallel v3: use VLAs in some places Date: Tue, 09 Feb 2010 11:14:00 -0000 [thread overview] Message-ID: <20100209111425.29626.qmail@sourceware.org> (raw) In-Reply-To: <bug-33485-102@http.gcc.gnu.org/bugzilla/> ------- Comment #18 from paolo dot carlini at oracle dot com 2010-02-09 11:14 ------- Ok, I changed Summary and Severity. Somebody should also double check whether VLAs are still triggering warnings or not. -- paolo dot carlini at oracle dot com changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|normal |enhancement Summary|parallel v3: do not use |parallel v3: use VLAs in |__builtin_alloca, use VLA |some places http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33485
prev parent reply other threads:[~2010-02-09 11:14 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-09-19 2:29 [Bug libstdc++/33485] New: parallel v3: do not use __builtin_alloca, use VLA bangerth at dealii dot org 2007-09-19 2:37 ` [Bug libstdc++/33485] " pinskia at gcc dot gnu dot org 2007-09-19 2:43 ` bangerth at math dot tamu dot edu 2007-09-19 17:05 ` bkoz at gcc dot gnu dot org 2007-09-19 17:09 ` pinskia at gcc dot gnu dot org 2007-09-26 19:06 ` pinskia at gcc dot gnu dot org 2007-09-26 20:44 ` bkoz at gcc dot gnu dot org 2007-10-08 14:56 ` bangerth at dealii dot org 2007-10-08 16:34 ` Andrew Pinski 2007-10-08 16:34 ` pinskia at gmail dot com 2007-10-08 18:11 ` bkoz at gcc dot gnu dot org 2007-10-08 19:15 ` bangerth at dealii dot org 2007-10-08 19:55 ` bkoz at gcc dot gnu dot org 2007-10-08 22:25 ` bangerth at dealii dot org 2007-10-09 21:51 ` bkoz at gcc dot gnu dot org 2009-01-13 8:42 ` bkoz at gcc dot gnu dot org 2009-01-13 10:06 ` bkoz at gcc dot gnu dot org 2010-02-08 11:19 ` paolo dot carlini at oracle dot com 2010-02-09 10:49 ` singler at kit dot edu 2010-02-09 11:14 ` paolo dot carlini at oracle dot com [this message]
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=20100209111425.29626.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: linkBe 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).