public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pcarlini at suse dot de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/21842] [4.1 Regression] 23_containers/bitset/operations/2.cc execution test fails Date: Tue, 31 May 2005 16:49:00 -0000 [thread overview] Message-ID: <20050531164907.31425.qmail@sourceware.org> (raw) In-Reply-To: <20050531163448.21842.jsm28@gcc.gnu.org> ------- Additional Comments From pcarlini at suse dot de 2005-05-31 16:49 ------- Notice that *nothing* changed in the relevant libstdc++-v3 code. Generally, only small, confined changes lately. Either this is a miscompilation or a *very* long standing latent problem. Can you attach the *.log excerpt? Even better, take care of the obvious checks, like compiling at lower optimization level? (I'm also going to do that, anyway: we want to ascertain the miscompilation and recategorize as soon as possible, in case) -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21842
next prev parent reply other threads:[~2005-05-31 16:49 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-05-31 16:36 [Bug libstdc++/21842] New: " jsm28 at gcc dot gnu dot org 2005-05-31 16:49 ` pcarlini at suse dot de [this message] 2005-05-31 16:51 ` [Bug middle-end/21842] " pinskia at gcc dot gnu dot org 2005-05-31 17:01 ` pcarlini at suse dot de 2005-05-31 17:06 ` joseph at codesourcery dot com 2005-05-31 17:15 ` pcarlini at suse dot de 2005-05-31 17:49 ` joseph at codesourcery dot com 2005-05-31 17:56 ` pinskia at gcc dot gnu dot org 2005-06-01 17:53 ` jsm28 at gcc dot gnu dot org 2005-06-01 17:54 ` jsm28 at gcc dot gnu dot 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=20050531164907.31425.qmail@sourceware.org \ --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: linkBe 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).