public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "jsm28 at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: java-prs@gcc.gnu.org
Subject: [Bug tree-optimization/36218] [4.2/4.3/4.4 regression] VRP causes stack overflow while building libgcj
Date: Sun, 08 Jun 2008 16:15:00 -0000 [thread overview]
Message-ID: <20080608161511.21380.qmail@sourceware.org> (raw)
In-Reply-To: <bug-36218-8837@http.gcc.gnu.org/bugzilla/>
------- Comment #5 from jsm28 at gcc dot gnu dot org 2008-06-08 16:15 -------
Subject: Bug 36218
Author: jsm28
Date: Sun Jun 8 16:14:33 2008
New Revision: 136563
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=136563
Log:
PR tree-optimization/36218
* Makefile.def (flags_to_pass): Add LDFLAGS_FOR_BUILD.
* Makefile.tpl (EXTRA_BUILD_FLAGS): Define.
(all prefix="build-"): Pass them to build-system sub-makes.
* Makefile.in: Regenerate.
config:
* config/mh-mingw (LDFLAGS): Define.
gcc:
* configure.ac: Use LDFLAGS="${LDFLAGS_FOR_BUILD}" when running
configure for the build system.
(BUILD_LDFLAGS): Define.
* configure: Regenerate.
* Makefile.in (BUILD_LDFLAGS): Define to @BUILD_LDFLAGS@.
Modified:
trunk/ChangeLog
trunk/Makefile.def
trunk/Makefile.in
trunk/Makefile.tpl
trunk/config/ChangeLog
trunk/config/mh-mingw
trunk/gcc/ChangeLog
trunk/gcc/Makefile.in
trunk/gcc/configure
trunk/gcc/configure.ac
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36218
next prev parent reply other threads:[~2008-06-08 16:15 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-12 11:01 [Bug libgcj/36218] New: [4.4 regression] libgcj causes stack overflow in jc1.exe aaronavay62 at aaronwl dot com
2008-05-12 11:03 ` [Bug libgcj/36218] " aaronavay62 at aaronwl dot com
2008-05-13 3:52 ` dannysmith at users dot sourceforge dot net
2008-05-22 20:09 ` [Bug tree-optimization/36218] [4.4 regression] VRP causes stack overflow while building libgcj pinskia at gcc dot gnu dot org
2008-05-22 20:10 ` [Bug tree-optimization/36218] [4.2/4.3/4.4 " pinskia at gcc dot gnu dot org
2008-06-06 15:02 ` rguenth at gcc dot gnu dot org
2008-06-08 16:15 ` jsm28 at gcc dot gnu dot org [this message]
2008-06-08 16:37 ` jsm28 at gcc dot gnu dot org
2008-06-11 10:49 ` aph at gcc dot gnu dot org
2008-06-13 21:41 ` mmitchel at gcc dot gnu dot org
2008-06-14 5:59 ` ian at airs dot com
2008-06-14 6:27 ` aph at gcc dot gnu dot org
2008-06-14 10:01 ` dannysmith at users dot sourceforge dot net
2008-06-14 15:43 ` aaronavay62 at aaronwl dot com
2008-07-14 8:03 ` aaronavay62 at aaronwl dot com
2008-07-30 9:23 ` aph at gcc dot gnu dot org
2008-08-22 19:28 ` rguenth at gcc dot gnu dot org
2008-08-23 18:06 ` aaronavay62 at aaronwl dot com
2008-08-27 22:07 ` jsm28 at gcc dot gnu dot org
2008-09-20 15:09 ` [Bug tree-optimization/36218] [4.2/4.3 Regression] " rguenth at gcc dot gnu dot org
2008-09-20 17:32 ` brian at dessent dot net
2008-09-20 17:51 ` rguenth at gcc dot gnu dot org
2009-03-31 20:50 ` [Bug tree-optimization/36218] [4.3 " jsm28 at gcc dot gnu dot org
2009-08-04 12:39 ` rguenth at gcc dot gnu dot org
2010-05-22 18:23 ` 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=20080608161511.21380.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=java-prs@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).