public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "paolo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/56085] Unsafe negation in C++03 pow(complex,int) Date: Thu, 24 Jan 2013 12:21:00 -0000 [thread overview] Message-ID: <bug-56085-4-8HtRjo18PV@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-56085-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56085 --- Comment #3 from paolo at gcc dot gnu.org <paolo at gcc dot gnu.org> 2013-01-24 12:21:06 UTC --- Author: paolo Date: Thu Jan 24 12:20:57 2013 New Revision: 195421 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=195421 Log: 2013-01-24 Paolo Carlini <paolo.carlini@oracle.com> PR libstdc++/56085 * include/std/complex (pow(const complex<>&, int)): Avoid __n signed overflow. Modified: trunk/libstdc++-v3/ChangeLog trunk/libstdc++-v3/include/std/complex
next prev parent reply other threads:[~2013-01-24 12:21 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-01-23 16:01 [Bug libstdc++/56085] New: " glisse at gcc dot gnu.org 2013-01-23 16:46 ` [Bug libstdc++/56085] " rguenth at gcc dot gnu.org 2013-01-24 11:20 ` paolo.carlini at oracle dot com 2013-01-24 12:21 ` paolo at gcc dot gnu.org [this message] 2013-01-24 12:22 ` paolo at gcc dot gnu.org 2013-01-24 12:22 ` paolo.carlini at oracle dot com
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-56085-4-8HtRjo18PV@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).