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/66673] swapping variables via chained xor fails
Date: Thu, 25 Jun 2015 19:56:00 -0000 [thread overview]
Message-ID: <bug-66673-4-wOeobDqFvP@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-66673-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66673
--- Comment #6 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
(In reply to joe.carnuccio from comment #2)
> -Wall produces no warnings...
Oh, you're using too old GCC. Please try a newer version.
next prev parent reply other threads:[~2015-06-25 19:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-25 19:23 [Bug c/66673] New: " joe.carnuccio at qlogic dot com
2015-06-25 19:29 ` [Bug c/66673] " mpolacek at gcc dot gnu.org
2015-06-25 19:41 ` joe.carnuccio at qlogic dot com
2015-06-25 19:42 ` joe.carnuccio at qlogic dot com
2015-06-25 19:46 ` joe.carnuccio at qlogic dot com
2015-06-25 19:54 ` trippels at gcc dot gnu.org
2015-06-25 19:56 ` mpolacek at gcc dot gnu.org [this message]
2015-06-25 21:09 ` [Bug c/66673] Wsequence-point warning missing when swapping variables via chained xor trippels 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-66673-4-wOeobDqFvP@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: link
Be 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).