public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "trippels at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/60058] New: [4.9 Regression] internal compiler error: Segmentation fault
Date: Tue, 04 Feb 2014 13:00:00 -0000	[thread overview]
Message-ID: <bug-60058-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 60058
           Summary: [4.9 Regression] internal compiler error: Segmentation
                    fault
           Product: gcc
           Version: 4.9.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: ipa
          Assignee: unassigned at gcc dot gnu.org
          Reporter: trippels at gcc dot gnu.org

markus@x4 common % cat test.ii
typedef enum {} UErrorCode;
class A {
public:
  virtual A &m_fn1(A &, const A &, UErrorCode &) const;
  void m_fn2();
  A();
  A(int);
};
class __attribute__((visibility("default"))) B : public A {
public:
  B(A &p1) : norm2(p1), set(0) {}
  A &m_fn1(A &, const A &, UErrorCode &) const;
  A &norm2;
  const int &set;
};

UErrorCode a;
A c;
void fn1(A *p1) {
  A b;
  p1->m_fn1(b, 0, a).m_fn2();
}

void fn2() {
  B d(c);
  fn1(&d);
}

markus@x4 common % g++ -c -O2 test.ii
test.ii:27:1: internal compiler error: Segmentation fault
 }
 ^
0xb4d18f crash_signal
        ../../gcc/gcc/toplev.c:337
0x103ef73 contains_struct_check
        ../../gcc/gcc/tree.h:2822
0x103ef73 ipa_get_indirect_edge_target_1
        ../../gcc/gcc/ipa-cp.c:1576
0x9d1360 estimate_edge_devirt_benefit
        ../../gcc/gcc/ipa-inline-analysis.c:2945
0x9d1360 estimate_edge_size_and_time
        ../../gcc/gcc/ipa-inline-analysis.c:2977
0x9d1360 estimate_calls_size_and_time
        ../../gcc/gcc/ipa-inline-analysis.c:3030
0x9d1872 estimate_node_size_and_time
        ../../gcc/gcc/ipa-inline-analysis.c:3117
0x9d4cb7 do_estimate_edge_size(cgraph_edge*)
        ../../gcc/gcc/ipa-inline-analysis.c:3660
0x9d4e62 estimate_edge_size
        ../../gcc/gcc/ipa-inline.h:277
0x9d4e62 estimate_edge_growth
        ../../gcc/gcc/ipa-inline.h:289
0x9d4e62 do_estimate_growth_1
        ../../gcc/gcc/ipa-inline-analysis.c:3771
0x82a4de cgraph_for_node_and_aliases(cgraph_node*, bool (*)(cgraph_node*,
void*), void*, bool)
        ../../gcc/gcc/cgraph.c:2209
0x9d537a do_estimate_growth(cgraph_node*)
        ../../gcc/gcc/ipa-inline-analysis.c:3785
0x105073b estimate_growth
        ../../gcc/gcc/ipa-inline.h:264
0x105073b inline_small_functions
        ../../gcc/gcc/ipa-inline.c:1565
0x105073b ipa_inline
        ../../gcc/gcc/ipa-inline.c:2025
0x105073b execute
        ../../gcc/gcc/ipa-inline.c:2381
Please submit a full bug report,
with preprocessed source if appropriate.

Started with r207447.


             reply	other threads:[~2014-02-04 13:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-04 13:00 trippels at gcc dot gnu.org [this message]
2014-02-04 13:19 ` [Bug ipa/60058] " trippels at gcc dot gnu.org
2014-02-04 14:22 ` rguenth at gcc dot gnu.org
2014-02-04 17:25 ` hubicka at gcc dot gnu.org
2014-02-04 17:26 ` hubicka 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-60058-4@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).