public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Jędrzej Dudkiewicz" <jedrzej.dudkiewicz@gmail.com>
To: gcc-help@gcc.gnu.org
Subject: Re: strict aliasing: how to swap pointers
Date: Wed, 30 Apr 2008 13:31:00 -0000	[thread overview]
Message-ID: <ab4f06660804300313o2a0e1213h9b13e2ec97a8f5@mail.gmail.com> (raw)
In-Reply-To: <4818432E.90604@redhat.com>

>  > #define SWAP(TYPE, A, B) do { TYPE tmp = a; b = b; b = tmp; } while (0)
>
>  Err,
>  #define SWAP(TYPE, A, B) do { TYPE tmp = a; a = b; b = tmp; } while (0)

Seems that

#define SWAP(TYPE, A, B) do { TYPE tmp = A; A = B; B = tmp; } while (0)

would be even better.
-- 
Jędrzej Dudkiewicz

I really hate this damn machine, I wish that they would sell it.
It never does just what I want, but only what I tell it.

  reply	other threads:[~2008-04-30 10:13 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-29 23:58 Evan Jones
2008-04-30  1:00 ` Rupert Wood
2008-04-30  1:17   ` OT Rant on why C++ Sucks (Was Re: strict aliasing: how to swap pointers) Robert William Fuller
2008-04-30  3:03     ` Gareth Buxton
2008-04-30  7:59     ` me22
2008-04-30 10:21       ` Rupert Wood
2008-04-30  4:46   ` strict aliasing: how to swap pointers Evan Jones
2008-04-30 10:13     ` Andrew Haley
2008-04-30 11:45       ` Andrew Haley
2008-04-30 13:31         ` Jędrzej Dudkiewicz [this message]
2008-04-30 14:29           ` Andrew Haley
2008-04-30 14:43       ` Evan Jones
2008-04-30 14:49         ` John Love-Jensen
2008-04-30 15:15           ` Evan Jones
2008-04-30 15:33             ` Andrew Haley
2008-04-30 18:01               ` Evan Jones
2008-04-30 20:38                 ` Andrew Haley
2008-04-30 21:49                 ` Sergei Organov
2008-04-30 15:22         ` Andrew Haley
2008-05-03  0:45           ` Matthew Woehlke
2008-05-03  9:10             ` Andrew Haley
2008-04-30  9:03 ` Sergei Organov

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=ab4f06660804300313o2a0e1213h9b13e2ec97a8f5@mail.gmail.com \
    --to=jedrzej.dudkiewicz@gmail.com \
    --cc=gcc-help@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).