All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Andreas Schwab <schwab@suse.de>
Cc: Dmitry Mishin <dim@openvz.org>,
	dev@openvz.org, netfilter-devel@lists.netfilter.org,
	"David S. Miller" <davem@davemloft.net>
Subject: Re: [RFC][PATCH] compat_uint64_t type
Date: Mon, 17 Apr 2006 19:12:21 +0200	[thread overview]
Message-ID: <4443CC75.4040703@trash.net> (raw)
In-Reply-To: <jehd4sdvh1.fsf@sykes.suse.de>

Andreas Schwab wrote:
> Patrick McHardy <kaber@trash.net> writes:
> 
>>I'm not sure if we should really introduce this new type, it is
>>misleading for at least x86. IIRC the situation there is:
>>
>>- gcc < 4.0 always aligns u64 types to 4byte
> 
> 
> Are you sure about that? I can't reproduce that with gcc 3.3.3.

I mixed up the versions, the change was between 2.x and 3.x:

gcc-2.95 -O2:
basic type:     align 4
embedded type:  align 4
gcc-3.3 -O2:
basic type:     align 8
embedded type:  align 4

It only shows with optimization, with -O0 gcc-2.95 also uses 8 for
the basic type.

>>So there is no one compat_uint64_t type, but it depends on the
>>situation.
> 
> 
> The alignment of standalone objects is uninteresting, what is important is
> getting compatible layout of aggregates.

I couldn't come up with a realistic example where people would make
mistakes because of this, so I guess I have to agree, although my
feeling still disagrees :)

      parent reply	other threads:[~2006-04-17 17:12 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-14 17:12 compat_xt_counters is not compatible Andreas Schwab
2006-04-15 14:11 ` Dmitry Mishin
2006-04-15 14:16   ` Andreas Schwab
2006-04-15 16:14     ` Dmitry Mishin
2006-04-15 17:32       ` Andreas Schwab
2006-04-15 18:38         ` Dmitry Mishin
2006-04-15 22:09           ` Andreas Schwab
2006-04-16  6:28             ` Dmitry Mishin
2006-04-16 11:41               ` Andreas Schwab
2006-04-17 20:13               ` David S. Miller
2006-04-15 16:37 ` Patrick McHardy
2006-04-15 17:31   ` Andreas Schwab
2006-04-15 17:52     ` Patrick McHardy
2006-04-16  7:24       ` David S. Miller
2006-04-16 15:07         ` Patrick McHardy
2006-04-17  5:24           ` David S. Miller
2006-04-17 10:59             ` [RFC][PATCH] compat_uint64_t type Dmitry Mishin
2006-04-17 11:51               ` Andreas Schwab
2006-04-17 12:04                 ` Dmitry Mishin
2006-04-17 14:05                   ` Andreas Schwab
2006-04-17 15:47               ` Patrick McHardy
2006-04-17 16:03                 ` Patrick McHardy
2006-04-17 20:20                   ` David S. Miller
2006-04-21  0:07                     ` Patrick McHardy
     [not found]                 ` <jehd4sdvh1.fsf@sykes.suse.de>
2006-04-17 17:12                   ` Patrick McHardy [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=4443CC75.4040703@trash.net \
    --to=kaber@trash.net \
    --cc=davem@davemloft.net \
    --cc=dev@openvz.org \
    --cc=dim@openvz.org \
    --cc=netfilter-devel@lists.netfilter.org \
    --cc=schwab@suse.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.