public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ebotcazou at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/30280] SIGSEGV on operator==(valarray<bool>, bool) Date: Fri, 22 Dec 2006 22:17:00 -0000 [thread overview] Message-ID: <20061222221720.10322.qmail@sourceware.org> (raw) In-Reply-To: <bug-30280-1186@http.gcc.gnu.org/bugzilla/> ------- Comment #4 from ebotcazou at gcc dot gnu dot org 2006-12-22 22:17 ------- No SIGSEGV for me with 4.1.1: gax% ./pr30280 Assertion failed: a == false, file pr30280.C, line 7 zsh: IOT instruction (core dumped) ./pr30280 Please provide the missing info as per http://gcc.gnu.org/bugs.html -- ebotcazou at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |WAITING http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30280
next prev parent reply other threads:[~2006-12-22 22:17 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-12-22 19:46 [Bug libstdc++/30280] New: " sebor at roguewave dot com 2006-12-22 19:52 ` [Bug libstdc++/30280] " pinskia at gcc dot gnu dot org 2006-12-22 20:22 ` sebor at roguewave dot com 2006-12-22 21:42 ` pcarlini at suse dot de 2006-12-22 22:17 ` ebotcazou at gcc dot gnu dot org [this message] 2006-12-22 22:25 ` sebor at roguewave dot com 2006-12-22 23:01 ` pcarlini at suse dot de 2006-12-23 8:05 ` ebotcazou at gcc dot gnu dot org 2006-12-23 11:17 ` gdr at integrable-solutions dot net 2006-12-23 18:50 ` Andrew Pinski 2006-12-23 18:50 ` pinskia at gmail dot com 2006-12-23 20:46 ` sebor at roguewave dot com 2006-12-24 4:56 ` pinskia at gcc dot gnu dot org 2006-12-24 5:02 ` [Bug target/30280] " pinskia at gcc dot gnu dot org 2006-12-24 5:23 ` gdr at integrable-solutions dot net 2007-04-08 22:52 ` pinskia at gcc dot gnu dot org 2008-11-30 9:45 ` ebotcazou 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=20061222221720.10322.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).