public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/66705] [5/6 Regression] section is missing linker error with -flto -fipa-pta
Date: Tue, 30 Jun 2015 13:25:00 -0000	[thread overview]
Message-ID: <bug-66705-4-JuJc9N4Rqy@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-66705-4@http.gcc.gnu.org/bugzilla/>

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

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Priority|P3                          |P2
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2015-06-30
   Target Milestone|---                         |5.2
     Ever confirmed|0                           |1

--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
Confirmed.

Breakpoint 1, fatal_error (loc=0, gmsgid=0x1783549 "%s: section %s is missing")
    at /space/rguenther/src/svn/gcc-5-branch/gcc/diagnostic.c:1203
1203      va_start (ap, gmsgid);
Missing separate debuginfos, use: zypper install
libgmp10-debuginfo-6.0.0-71.1.x86_64 libisl13-debuginfo-0.14-25.2.x86_64
libmpc3-debuginfo-1.0.2-38.2.x86_64 libmpfr4-debuginfo-3.1.2-3.1.2.x86_64
(gdb) up
#1  0x0000000000fe0387 in varpool_node::get_constructor (this=0x7ffff6ac4000)
    at /space/rguenther/src/svn/gcc-5-branch/gcc/varpool.c:328
328                      name);
(gdb) l
323       data = lto_get_section_data (file_data, LTO_section_function_body,
324                                    name, &len);
325       if (!data)
326         fatal_error (input_location, "%s: section %s is missing",
327                      file_data->file_name,
328                      name);

(gdb) up
#2  0x0000000000eacc07 in create_variable_info_for (decl=0x7ffff68d7900, 
    name=0x1763482 "NULL")
    at /space/rguenther/src/svn/gcc-5-branch/gcc/tree-ssa-structalias.c:5808
5808              if (vnode->get_constructor ()
(gdb) l
5803              if (!vnode->all_refs_explicit_p ())
5804                make_copy_constraint (vi, nonlocal_id);
5805
5806              /* If this is a global variable with an initializer and we
are in
5807                 IPA mode generate constraints for it.  */
5808              if (vnode->get_constructor ()
5809                  && vnode->definition)

so IPA PTA needs to guard ->get_constructor () somehow?  That is, it
doesn't return NULL_TREE when it cant' get its hands on it?


  parent reply	other threads:[~2015-06-30 13:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-30 12:41 [Bug ipa/66705] New: " trippels at gcc dot gnu.org
2015-06-30 13:03 ` [Bug ipa/66705] " trippels at gcc dot gnu.org
2015-06-30 13:25 ` rguenth at gcc dot gnu.org [this message]
2015-06-30 13:27 ` rguenth at gcc dot gnu.org
2015-07-16  9:11 ` rguenth at gcc dot gnu.org
2015-09-02  9:28 ` rguenth at gcc dot gnu.org
2015-09-02  9:29 ` rguenth at gcc dot gnu.org
2015-09-03  9:25 ` rguenth at gcc dot gnu.org
2015-09-03  9:26 ` rguenth at gcc dot gnu.org
2015-09-03  9:35 ` rguenth at gcc dot gnu.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=bug-66705-4-JuJc9N4Rqy@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).