public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "gregoryk at edifecs dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/31368] basic_string and unsigned short leads to memory fault Date: Tue, 27 Mar 2007 17:20:00 -0000 [thread overview] Message-ID: <20070327172009.13303.qmail@sourceware.org> (raw) In-Reply-To: <bug-31368-14317@http.gcc.gnu.org/bugzilla/> [-- Warning: decoded text below may be mangled, UTF-8 assumed --] [-- Attachment #1: Type: text/plain, Size: 396 bytes --] ------- Comment #7 from gregoryk at edifecs dot com 2007-03-27 18:20 ------- Unfortunately I do not have possibility to run my test case using latest GCC compiler. Im limited in hardware and software choice. Besides Im not sure what do you mean to fix testcase. If you could fix it then it will be accepted in any way by me. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31368
next prev parent reply other threads:[~2007-03-27 17:20 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-03-26 20:51 [Bug libstdc++/31368] New: " gregoryk at edifecs dot com 2007-03-26 21:11 ` [Bug libstdc++/31368] " pcarlini at suse dot de 2007-03-26 21:28 ` gregoryk at edifecs dot com 2007-03-26 21:52 ` pcarlini at suse dot de 2007-03-26 22:14 ` gregoryk at edifecs dot com 2007-03-26 22:25 ` pcarlini at suse dot de 2007-03-27 17:07 ` pcarlini at suse dot de 2007-03-27 17:20 ` gregoryk at edifecs dot com [this message] 2007-03-27 17:24 ` pcarlini at suse dot de 2007-03-27 17:37 ` pcarlini at suse dot de 2007-03-27 17:39 ` gregoryk at edifecs dot com 2007-03-27 17:40 ` gregoryk at edifecs dot com 2007-03-27 18:22 ` pcarlini at suse dot de 2007-03-27 18:25 ` pcarlini at suse dot de 2007-03-27 18:25 ` pcarlini at suse dot de 2007-03-27 18:51 ` gregoryk at edifecs dot com 2007-03-27 18:53 ` pcarlini at suse dot de
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=20070327172009.13303.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).