public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: bkoz@gcc.gnu.org
To: bkoz@redhat.com, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
	geoffk@gcc.gnu.org, geoffk@geoffk.org, jason@redhat.com,
	pcarlini@unitus.it
Subject: Re: other/9274: [pch] cannot create libstdc++-v3 pch
Date: Thu, 10 Apr 2003 21:51:00 -0000	[thread overview]
Message-ID: <20030410215114.24140.qmail@sources.redhat.com> (raw)

Synopsis: [pch] cannot create libstdc++-v3 pch

State-Changed-From-To: open->analyzed
State-Changed-By: bkoz
State-Changed-When: Thu Apr 10 21:51:14 2003
State-Changed-Why:
    This still isn't fixed, contrary to current check ins.
    
    On x86-linux, with pch enabled, on gcc-2003-04-10 I get:
                    === libstdc++-v3 Summary ===
     
    # of expected passes            1650
    # of unexpected failures        52
    # of unexpected successes       1
    # of expected failures          1
    
    where the fails looks like this:
    
     Executing on host: /mnt/hd/bld/gcc/gcc/g++ -shared-libgcc -B/mnt/hd/bld/gcc/gcc/ -nostdinc++ -L/mnt/hd/bld/gcc/i686-pc-linux-gnu/libstdc++-v3/src -L/mnt/hd/bld/gcc/i686-pc-linux-gnu/libstdc++-v3/src/.libs -B/mnt/hd/bld/H-x86-gcc/i686-pc-linux-gnu/bin/ -B/mnt/hd/bld/H-x86-gcc/i686-pc-linux-gnu/lib/ -isystem /mnt/hd/bld/H-x86-gcc/i686-pc-linux-gnu/include -isystem /mnt/hd/bld/H-x86-gcc/i686-pc-linux-gnu/sys-include -Winvalid-pch -include /mnt/hd/bld/gcc/i686-pc-linux-gnu/libstdc++-v3/include/stdc++.h -g -O2 -ffunction-sections -fdata-sections -fmessage-length=0 -DLOCALEDIR="/mnt/hd/bld/gcc/i686-pc-linux-gnu/libstdc++-v3/po/share/locale" -nostdinc++ -I/mnt/hd/bld/gcc/i686-pc-linux-gnu/libstdc++-v3/include/i686-pc-linux-gnu -I/mnt/hd/bld/gcc/i686-pc-linux-gnu/libstdc++-v3/include -I/mnt/hd/src/gcc/libstdc++-v3/libsupc++ -I/mnt/hd/src/gcc/libstdc++-v3/libio -I/mnt/hd/src/gcc/libstdc++-v3/include/backward -I/mnt/hd/src/gcc/libstdc++-v3/testsuite /mnt/hd/src/gcc/libstdc++-v3/testsuite/22_locale/money_get/get/char/wrapped_env.cc   -DDEBUG_ASSERT  -L/mnt/hd/bld/gcc/i686-pc-linux-gnu//libstdc++-v3/testsuite -lv3test -lm   -o ./wrapped_env.exe    (timeout = 300)
    /mnt/hd/src/gcc/libstdc++-v3/testsuite/22_locale/money_get/get/char/wrapped_env.cc: In member function `void std::_STL_mutex_lock::_M_release_lock()':
    
    /mnt/hd/src/gcc/libstdc++-v3/testsuite/22_locale/money_get/get/char/wrapped_env.cc:71: internal compiler error: in gen_subprogram_die, at dwarf2out.c:10899
    
    Please submit a full bug report,
    
    with preprocessed source if appropriate.
    
    See <URL:http://gcc.gnu.org/bugs.html> for instructions.
    
    compiler exited with status 1

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9274


             reply	other threads:[~2003-04-10 21:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-10 21:51 bkoz [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-04-16  0:30 geoffk
2003-04-15 22:56 Paolo Carlini
2003-04-15 22:46 Benjamin Kosnik
2003-04-15 20:56 Geoff Keating
2003-04-15 15:46 Benjamin Kosnik
2003-04-14 22:06 Geoff Keating
2003-04-14 19:16 bkoz
2003-03-25 18:06 bkoz
2003-02-22  0:46 Geoffrey Keating
2003-02-06 21:25 bkoz

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=20030410215114.24140.qmail@sources.redhat.com \
    --to=bkoz@gcc.gnu.org \
    --cc=bkoz@redhat.com \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=geoffk@gcc.gnu.org \
    --cc=geoffk@geoffk.org \
    --cc=jason@redhat.com \
    --cc=pcarlini@unitus.it \
    /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).