public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "markus at trippelsdorf dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/54837] New: [4.8 Regression] lto bootstrap error: ICE in expand_debug_source_expr, at cfgexpand.c:3538
Date: Sat, 06 Oct 2012 17:26:00 -0000	[thread overview]
Message-ID: <bug-54837-4@http.gcc.gnu.org/bugzilla/> (raw)


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

             Bug #: 54837
           Summary: [4.8 Regression] lto bootstrap error: ICE in
                    expand_debug_source_expr, at cfgexpand.c:3538
    Classification: Unclassified
           Product: gcc
           Version: 4.8.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: bootstrap
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: markus@trippelsdorf.de


With:
~/gcc/configure --disable-werror --disable-multilib --enable-languages=c,c++
--enable-checking=yes --with-build-config=lto-bootstrap

I get:
In file included from :36:0:
/home/markus/gcc/gcc/vec.h: In member function
‘_ZN5vec_tIcE3popEPKcjS2_.local.27.constprop.53’:
/home/markus/gcc/gcc/vec.h:810:1: internal compiler error: in
expand_debug_source_expr, at cfgexpand.c:3538
 vec_t<T>::pop (ALONE_VEC_CHECK_DECL)
 ^
0x5755a8 expand_debug_source_expr
        /home/markus/gcc/gcc/cfgexpand.c:3537
0x575a78 expand_debug_locations
        /home/markus/gcc/gcc/cfgexpand.c:3622
0x578496 gimple_expand_cfg
        /home/markus/gcc/gcc/cfgexpand.c:4487
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.

Reduced:

markus@x4 gcc % cat test.ii
struct A
{
    int num_;
};
template < typename T > struct B
{
    T & pop (const char *);
    A prefix_;
    T vec_[];
};
char *a;
B < int >*b;
void fn1 (char *, const char *) __attribute__ ((__noreturn__));
template < typename T > T & B < T >::pop (const char *p1)
{
    prefix_.num_ ? : (fn1 (a, p1), 0);
    return vec_[-prefix_.num_];
}

int main ()
{
    b->pop (__FUNCTION__);
    b->pop (__FUNCTION__);
    b->pop (__FUNCTION__);
}

markus@x4 gcc % /var/tmp/gcc_build_dir/./prev-gcc/g++
-B/var/tmp/gcc_build_dir/./prev-gcc/ test.ii -nodefaultlibs -g -O2 -flto
In file included from :1:0:
test.ii: In member function ‘_ZN1BIiE3popEPKc.local.0.constprop.1’:
test.ii:14:29: internal compiler error: in expand_debug_source_expr, at
cfgexpand.c:3538
 template < typename T > T & B < T >::pop (const char *p1)
                             ^
0x5755a8 expand_debug_source_expr
        /home/markus/gcc/gcc/cfgexpand.c:3537
0x575a78 expand_debug_locations
        /home/markus/gcc/gcc/cfgexpand.c:3622
0x578496 gimple_expand_cfg
        /home/markus/gcc/gcc/cfgexpand.c:4487
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.


             reply	other threads:[~2012-10-06 17:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-06 17:26 markus at trippelsdorf dot de [this message]
2012-10-08 10:51 ` [Bug bootstrap/54837] " rguenth at gcc dot gnu.org
2012-10-08 13:57 ` hjl.tools at gmail dot com
2012-10-09 14:15 ` rguenth at gcc dot gnu.org
2012-10-09 14:40 ` rguenth at gcc dot gnu.org
2012-10-09 15:15 ` 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-54837-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).