public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/60958] Initialization of arrays in tr1/regex ill-formed or with undefined behaviour Date: Fri, 25 Apr 2014 15:42:00 -0000 [thread overview] Message-ID: <bug-60958-4-4OfardwtwK@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-60958-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60958 --- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> --- (In reply to Hubert Tong from comment #2) > I am trying to use a code base which used a TR1 regex implementation on > another platform. Your comment led me to find > http://gcc.gnu.org/onlinedocs/libstdc++/manual/status.html#status.iso.tr1, > which does indicate that tr1/regex does not work. It's incomplet and incorrekt. Even with those array initializers fixed that function tries to call a non-existent std::ctype::isspace() function and does (__f | __wt) when it should be (__f & __wt), and only works for char not wchar_t, and probably other issues. > Is the recommendation > (short of switching over to C++11) to use the Boost implementation? Is the > TR1 implementation status of regex in libstdc++ likely to change in the > future? The TR1 code in libstdc++ is not going to change, so if Boost is an option then yes, use that.
next prev parent reply other threads:[~2014-04-25 15:42 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-04-24 20:46 [Bug libstdc++/60958] New: " hstong at ca dot ibm.com 2014-04-25 9:36 ` [Bug libstdc++/60958] " redi at gcc dot gnu.org 2014-04-25 13:27 ` hstong at ca dot ibm.com 2014-04-25 15:42 ` redi at gcc dot gnu.org [this message] 2014-04-25 16:11 ` redi at gcc dot gnu.org 2014-04-25 16:13 ` redi at gcc dot gnu.org 2014-04-28 15:14 ` redi 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-60958-4-4OfardwtwK@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: 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).