public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ro at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/39025] ICE in start_function, at c-decl.c:6225 while configuring libgcc
Date: Mon, 02 Feb 2009 23:43:00 -0000	[thread overview]
Message-ID: <20090202234322.4073.qmail@sourceware.org> (raw)
In-Reply-To: <bug-39025-279@http.gcc.gnu.org/bugzilla/>



------- Comment #1 from ro at gcc dot gnu dot org  2009-02-02 23:43 -------
It turns out that there are two problems here:

* If you invoke cc1 conftest.c (i.e. without -quiet), you get the ICE from the
  assertion failure in c-decl.c:6225:

  /* This is the earliest point at which we might know the assembler
     name of the function.  Thus, if it's set before this, die horribly.  */
  gcc_assert (!DECL_ASSEMBLER_NAME_SET_P (decl1));

  decl1 has an assembler_name of "main" at this point, which is due to this
  change in toplev.c (announce_function):

@@ -419,10 +432,7 @@ announce_function (tree decl)
 {
   if (!quiet_flag)
     {
-      if (rtl_dump_and_exit)
-       fprintf (stderr, "%s ", IDENTIFIER_POINTER (DECL_NAME (decl)));
-      else
-       fprintf (stderr, " %s", lang_hooks.decl_printable_name (decl, 2));
+      fprintf (stderr, "%s ", IDENTIFIER_POINTER (DECL_ASSEMBLER_NAME
(decl)));
       fflush (stderr);
       pp_needs_newline (global_dc->printer) = true;
       diagnostic_set_last_function (global_dc, (diagnostic_info *) NULL);

  Unlike lang_hooks.decl_printable_name, decl_assembler_name sets
assembler_name
  if unset, thus breaking the later assert.  Since announce_functions gards
  this with !quiet_flag, it only breaks without that flag.

* If instead on runs cc1 -g -quiet conftest.c (-g is necessary to trigger the
  bug which breaks configure, -quiet works around the first problem), on gets
  this instead.

> ./cc1 -g -quiet conftest.c
conftest.c:9: internal compiler error: Segmentation Fault

   Running cc1 under gdb reveals

Program received signal SIGSEGV, Segmentation fault.
0x083fdd54 in get_personality_function (decl=0x0) at
/vol/gcc/src/gcc-lto/gcc/expr.h:806
(gdb) where
#0  0x083fdd54 in get_personality_function (decl=0x0) at
/vol/gcc/src/gcc-lto/gcc/expr.h:806
#1  0x08404f08 in output_call_frame_info (for_eh=0) at
/vol/gcc/src/gcc-lto/gcc/dwarf2out.c:2914
#2  0x08405fce in dwarf2out_frame_finish () at
/vol/gcc/src/gcc-lto/gcc/dwarf2out.c:3351
#3  0x0899930a in compile_file () at /vol/gcc/src/gcc-lto/gcc/toplev.c:1023
#4  0x0899acc4 in do_compile () at /vol/gcc/src/gcc-lto/gcc/toplev.c:2220
#5  0x0899ad2b in toplev_main (argc=4, argv=0x80476cc) at
/vol/gcc/src/gcc-lto/gcc/toplev.c:2252
#6  0x0821c2f9 in main (argc=4, argv=0x80476cc) at
/vol/gcc/src/gcc-lto/gcc/main.c:35

  I.e. get_personality_function is called with current_function_decl = NULL.


-- 


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


  reply	other threads:[~2009-02-02 23:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-29 17:13 [Bug bootstrap/39025] New: " ro at gcc dot gnu dot org
2009-02-02 23:43 ` ro at gcc dot gnu dot org [this message]
2009-07-09  5:11 ` [Bug bootstrap/39025] " bje at gcc dot gnu dot org
2009-07-09 18:50 ` ro at gcc dot gnu dot org
2009-07-13  5:50 ` bje 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=20090202234322.4073.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).