public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bugzilla-gcc at thewrittenword dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/35169] SIGSEGV for stack growth failure while building 4.2.3
Date: Sat, 29 Mar 2008 02:22:00 -0000	[thread overview]
Message-ID: <20080329022125.19028.qmail@sourceware.org> (raw)
In-Reply-To: <bug-35169-6116@http.gcc.gnu.org/bugzilla/>



------- Comment #4 from bugzilla-gcc at thewrittenword dot com  2008-03-29 02:21 -------
(In reply to comment #3)
> (In reply to comment #2)
> > (In reply to comment #1)
> > > ld is running at this time so I doubt this is a GCC bug.
> > 
> > The Pid it is referring to ("Pid 18929 received a SIGSEGV for stack growth
> > failure.") is /opt/build/china/gcc-4.2.3-objdir/./gcc/xgcc.
> 
> 
> Seems to be recursing in cancel_option until stack runs out:
>

All due to a bug in awk on ia64-hpux11.23. Using gawk allows the build to
complete. Here is a selection of a diff from options.c generated with awk and
gawk:
   { "-W",
     "This switch is deprecated; use -Wextra instead",
-    N_OPTS, 1, 0,
+    N_OPTS, 1, -1,
     CL_COMMON | CL_REJECT_NEGATIVE,
     0, CLVC_BOOLEAN, 0 },


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35169


  parent reply	other threads:[~2008-03-29  2:22 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-11 20:30 [Bug bootstrap/35169] New: " bugzilla-gcc at thewrittenword dot com
2008-02-12  1:36 ` [Bug bootstrap/35169] " pinskia at gcc dot gnu dot org
2008-02-12  3:53 ` bugzilla-gcc at thewrittenword dot com
2008-03-28 20:59 ` bugzilla-gcc at thewrittenword dot com
2008-03-29  2:22 ` bugzilla-gcc at thewrittenword dot com [this message]
2008-03-31 11:33 ` rwild at gcc dot gnu dot org
2008-03-31 21:20 ` rwild at gcc dot gnu dot org
2008-04-17 15:10 ` cnstar9988 at gmail dot com
2008-04-28 22:29 ` rwild at gcc dot gnu dot org
2008-05-02  4:09 ` rwild at gcc dot gnu dot org
2008-05-02  4:17 ` rwild at gcc dot gnu dot org
2008-05-02  4:31 ` rwild at gcc dot gnu dot org
2008-05-02  9:20 ` ebotcazou 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=20080329022125.19028.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).