public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "3dw4rd at verizon dot net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/52654] [C++11] Warn on overflow in user-defined literals Date: Sat, 31 Mar 2012 17:04:00 -0000 [thread overview] Message-ID: <bug-52654-4-mkcj9n77rS@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-52654-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52654 --- Comment #5 from Ed Smith-Rowland <3dw4rd at verizon dot net> 2012-03-31 16:57:12 UTC --- Created attachment 27053 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=27053 This test should give no warnings. I think I'm going to have to put off interpreting numbers until the very end inside the call resolution. I think I should completely remove the numeric value from the literal tree. Sigh.
next prev parent reply other threads:[~2012-03-31 16:58 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-03-21 10:48 [Bug c++/52654] New: " marc.glisse at normalesup dot org 2012-03-29 16:42 ` [Bug c++/52654] " paolo.carlini at oracle dot com 2012-03-30 14:39 ` 3dw4rd at verizon dot net 2012-03-30 15:13 ` jakub at gcc dot gnu.org 2012-03-30 17:51 ` 3dw4rd at verizon dot net 2012-03-31 17:04 ` 3dw4rd at verizon dot net [this message] 2012-03-31 17:07 ` 3dw4rd at verizon dot net 2012-03-31 18:30 ` marc.glisse at normalesup dot org 2012-03-31 20:09 ` 3dw4rd at verizon dot net 2012-04-05 19:31 ` 3dw4rd at verizon dot net 2012-04-06 4:52 ` 3dw4rd at verizon dot net 2012-04-06 11:23 ` manu at gcc dot gnu.org 2012-04-06 11:46 ` manu at gcc dot gnu.org 2012-04-06 15:33 ` 3dw4rd at verizon dot net 2012-04-06 15:37 ` manu at gcc dot gnu.org 2012-04-06 16:41 ` manu at gcc dot gnu.org 2012-04-06 17:40 ` 3dw4rd at verizon dot net 2012-04-06 18:39 ` manu at gcc dot gnu.org 2012-06-06 15:04 ` 3dw4rd at verizon dot net 2012-11-28 3:05 ` 3dw4rd at verizon dot net 2012-11-29 2:31 ` emsr at gcc dot gnu.org 2012-11-29 10:33 ` 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-52654-4-mkcj9n77rS@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).