public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mec at google dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/28277] New: __builtin_alloca with no limit in libstdc++
Date: Wed, 05 Jul 2006 20:57:00 -0000 [thread overview]
Message-ID: <bug-28277-11211@http.gcc.gnu.org/bugzilla/> (raw)
libstc++ uses __builtin_alloca in several places:
config/local/gnu/codecvt_members.cc
include/ext/codecvt_specializations.h
include/ext/vstring.cc
include/bits/locale_facets.tcc
include/bits/ostream.tcc
include/bits/fstream.cc
include/std/std_valarray.h
src/valarray-inst.cc
These have data-dependent sizes with no obvious limit, which does not mix well
with threads and small stacks.
--
Summary: __builtin_alloca with no limit in libstdc++
Product: gcc
Version: 4.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libstdc++
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: mec at google dot com
GCC build triplet: i686-pc-linux-gnu
GCC host triplet: i686-pc-linux-gnu
GCC target triplet: i686-pc-linux-gnu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28277
next reply other threads:[~2006-07-05 20:57 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-05 20:57 mec at google dot com [this message]
2006-07-05 21:48 ` [Bug libstdc++/28277] " pcarlini at suse dot de
2006-07-05 22:21 ` mec at google dot com
2006-07-05 22:27 ` Andrew Pinski
2006-07-05 22:27 ` pinskia at physics dot uc dot edu
2006-07-05 22:32 ` pcarlini at suse dot de
2006-07-05 22:43 ` mec at google dot com
2006-07-05 22:48 ` pcarlini at suse dot de
2006-07-05 23:00 ` pcarlini at suse dot de
2006-07-05 23:00 ` pcarlini at suse dot de
2006-07-05 23:17 ` pcarlini at suse dot de
2006-07-08 9:45 ` pcarlini at suse dot de
2006-07-11 11:22 ` paolo at gcc dot gnu dot org
2006-07-15 20:31 ` paolo at gcc dot gnu dot org
2006-07-16 15:39 ` paolo at gcc dot gnu dot org
2006-10-08 1:13 ` paolo at gcc dot gnu dot org
2006-10-09 10:50 ` paolo at gcc dot gnu dot org
2006-10-09 18:04 ` paolo at gcc dot gnu dot org
2006-10-13 9:00 ` paolo at gcc dot gnu dot org
2007-04-09 21:36 ` pcarlini at suse dot de
2007-04-10 10:39 ` paolo at gcc dot gnu dot org
2007-04-12 23:07 ` paolo at gcc dot gnu dot org
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=bug-28277-11211@http.gcc.gnu.org/bugzilla/ \
--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: 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).