linux-kernel - Re: [PATCH] ubi: kill homegrown endian macros

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <6c8c0e6cd0ac95fd1c7d4e822f1e2029@kernel.crashing.org>
Date:	Sat, 19 May 2007 00:00:56 +0200
From:	Segher Boessenkool <segher@...nel.crashing.org>
To:	David Woodhouse <dwmw2@...radead.org>
Cc:	Matthieu CASTET <castet.matthieu@...e.fr>,
	"John Anthony Kazos Jr." <jakj@...-k-j.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] ubi: kill homegrown endian macros

>> Out of curiosity, why would a compiler ever insert padding in a 
>> structure
>> that has all its elements properly-aligned?
>
> Well, it might decide it would be nicer if some elements were aligned 
> to
> 64 bits. Or to a cache line. Or something. I don't care about _why_ --
> the point is that it's _allowed_ to. Hence the original use of
> __attribute__((packed)).

It's not the compiler who decides -- struct layout is
dictated by the ABI you're compiling for.


Segher

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/