public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/50347] unexpected -Wconversion error from gcc builtin Date: Thu, 27 Mar 2014 15:59:00 -0000 [thread overview] Message-ID: <bug-50347-4-r4FExg2jMJ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-50347-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50347 --- Comment #5 from Marek Polacek <mpolacek at gcc dot gnu.org> --- Author: mpolacek Date: Thu Mar 27 15:59:07 2014 New Revision: 208870 URL: http://gcc.gnu.org/viewcvs?rev=208870&root=gcc&view=rev Log: PR c/50347 * doc/extend.texi (ffs Builtins): Change unsigned types to signed types. Modified: trunk/gcc/ChangeLog trunk/gcc/doc/extend.texi
prev parent reply other threads:[~2014-03-27 15:59 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-09-10 8:45 [Bug c/50347] New: " gcc.hall at gmail dot com 2011-09-10 10:19 ` [Bug c/50347] " gcc.hall at gmail dot com 2011-09-11 0:38 ` gcc.hall at gmail dot com 2012-06-07 14:02 ` manu at gcc dot gnu.org 2014-03-25 20:53 ` mpolacek at gcc dot gnu.org 2014-03-27 15:59 ` mpolacek at gcc dot gnu.org 2014-03-27 15:59 ` mpolacek at gcc dot gnu.org [this message]
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-50347-4-r4FExg2jMJ@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).