public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ktietz at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/65566] thread-local-var-1-lbv.c:34:1: internal compiler error: Segmentation fault
Date: Thu, 26 Mar 2015 12:06:00 -0000	[thread overview]
Message-ID: <bug-65566-4-dfTa7Jldiw@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-65566-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65566

Kai Tietz <ktietz at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|WAITING                     |NEW
                 CC|                            |ktietz at gcc dot gnu.org

--- Comment #2 from Kai Tietz <ktietz at gcc dot gnu.org> ---
Confirmed.

We see an segfault (caused by cfun being NULL).

Program received signal SIGSEGV, Segmentation fault.
0x00cee933 in lower_emutls_function_body (node=<optimized out>)
    at ../../gcc/gcc/tree-emutls.c:644
644       FOR_EACH_BB_FN (d.bb, cfun)
(gdb) print cfun
$1 = (function *) 0x0

(gdb) bt
#0  0x00cee933 in lower_emutls_function_body (node=<optimized out>)
    at ../../gcc/gcc/tree-emutls.c:644
#1  ipa_lower_emutls () at ../../gcc/gcc/tree-emutls.c:810
#2  (anonymous namespace)::pass_ipa_lower_emutls::execute (this=0x800524b0)
    at ../../gcc/gcc/tree-emutls.c:850
#3  0x007354b5 in execute_one_pass (pass=pass@entry=0x800524b0)
    at ../../gcc/gcc/passes.c:2330
#4  0x00736010 in execute_ipa_pass_list (pass=0x800524b0)
    at ../../gcc/gcc/passes.c:2729
#5  0x0074253d in ipa_passes () at ../../gcc/gcc/cgraphunit.c:2154
#6  symbol_table::compile (this=this@entry=0xfff20000)
    at ../../gcc/gcc/cgraphunit.c:2295
#7  0x007447af in symbol_table::finalize_compilation_unit (this=0xfff20000)
    at ../../gcc/gcc/cgraphunit.c:2444
#8  0x0041fbbc in c_write_global_declarations ()
    at ../../gcc/gcc/c/c-decl.c:10801
#9  0x0077dd37 in compile_file () at ../../gcc/gcc/toplev.c:608
#10 0x01199823 in do_compile () at ../../gcc/gcc/toplev.c:2076
#11 toplev::main (this=this@entry=0xc1bab8e, argc=argc@entry=7,
    argv=argv@entry=0xc1babbc) at ../../gcc/gcc/toplev.c:2174
#12 0x012096d2 in main (argc=7, argv=0xc1babbc) at ../../gcc/gcc/main.c:39


      parent reply	other threads:[~2015-03-26 11:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-25 18:27 [Bug target/65566] New: " rainer@emrich-ebersheim.de
2015-03-26 11:05 ` [Bug target/65566] " rguenth at gcc dot gnu.org
2015-03-26 12:06 ` ktietz at gcc dot gnu.org [this message]

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-65566-4-dfTa7Jldiw@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).