public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dannysmith at users dot sourceforge dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/41254] [4.5 Regression] crashed compile Qt4 gui library
Date: Mon, 07 Sep 2009 04:02:00 -0000 [thread overview]
Message-ID: <20090907040143.27809.qmail@sourceware.org> (raw)
In-Reply-To: <bug-41254-18091@http.gcc.gnu.org/bugzilla/>
------- Comment #30 from dannysmith at users dot sourceforge dot net 2009-09-07 04:01 -------
(In reply to comment #24)
> Subject: Re: [4.5 Regression] crashed compile Qt4 gui
> library
>
> On Sun, 6 Sep 2009, t66667 at gmail dot com wrote:
>
> >
> >
> > ------- Comment #22 from t66667 at gmail dot com 2009-09-06 22:20 -------
> > (In reply to comment #16)
> > > Try building without the patch but with unlimited stack (ulimit -s unlimited)
> > > and see if the same error appears.
> > >
> >
> > You mean cross compile the "native compiler" from linux by setting the shell
> > with command "ulimit -s unlimited" ?
> > Or you want me to build the cross compiler and native compiler then try and
> > build qt4?
>
> Just the same way as you reported the bug (I understand that this
> was a native compiler issue?). There surely must be a way to increase
> the maximum stack size with windows?
To increase the stack size on windows, add -Wl,--stack=0x20000000 (for eg 32 Mb
stack). This hard codes the exe's stack size into the program header.
>
> Richard.
>
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41254
next prev parent reply other threads:[~2009-09-07 4:02 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-04 7:02 [Bug c++/41254] New: " t66667 at gmail dot com
2009-09-04 7:04 ` [Bug c++/41254] " t66667 at gmail dot com
2009-09-04 10:39 ` rguenth at gcc dot gnu dot org
2009-09-05 7:02 ` t66667 at gmail dot com
2009-09-05 10:23 ` rguenth at gcc dot gnu dot org
2009-09-05 10:53 ` t66667 at gmail dot com
2009-09-05 11:34 ` rguenth at gcc dot gnu dot org
2009-09-05 21:04 ` rguenth at gcc dot gnu dot org
2009-09-05 21:05 ` [Bug middle-end/41254] [4.5 Regression] " rguenth at gcc dot gnu dot org
2009-09-05 21:10 ` rguenth at gcc dot gnu dot org
2009-09-05 21:12 ` rguenth at gcc dot gnu dot org
2009-09-05 22:29 ` rguenth at gcc dot gnu dot org
2009-09-06 0:03 ` t66667 at gmail dot com
2009-09-06 10:13 ` rguenth at gcc dot gnu dot org
2009-09-06 12:55 ` t66667 at gmail dot com
2009-09-06 13:57 ` t66667 at gmail dot com
2009-09-06 13:59 ` t66667 at gmail dot com
2009-09-06 14:07 ` rguenth at gcc dot gnu dot org
2009-09-06 16:51 ` rguenth at gcc dot gnu dot org
2009-09-06 21:59 ` t66667 at gmail dot com
2009-09-06 22:02 ` rguenther at suse dot de
2009-09-06 22:14 ` t66667 at gmail dot com
2009-09-06 22:19 ` rguenth at gcc dot gnu dot org
2009-09-06 22:20 ` t66667 at gmail dot com
2009-09-06 22:22 ` t66667 at gmail dot com
2009-09-06 22:22 ` rguenther at suse dot de
2009-09-06 22:27 ` t66667 at gmail dot com
2009-09-06 22:31 ` t66667 at gmail dot com
2009-09-06 22:42 ` t66667 at gmail dot com
2009-09-06 22:43 ` t66667 at gmail dot com
2009-09-06 22:55 ` t66667 at gmail dot com
2009-09-07 4:02 ` dannysmith at users dot sourceforge dot net [this message]
2009-09-09 9:09 ` t66667 at gmail dot com
2009-09-10 8:53 ` rguenth at gcc dot gnu dot org
2009-09-10 9:24 ` rguenth 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=20090907040143.27809.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: 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).