From: Chen Gang <gang.chen.5i5j@gmail.com>
To: Antonio Quartulli <antonio@meshcoding.com>
Cc: James Hogan <james.hogan@imgtec.com>,
mareklindner@neomailbox.ch, netdev <netdev@vger.kernel.org>,
b.a.t.m.a.n@lists.open-mesh.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux-metag@vger.kernel.org, Greg KH <gregkh@linuxfoundation.org>,
David Miller <davem@davemloft.net>,
Dan Carpenter <dan.carpenter@oracle.com>
Subject: Re: [B.A.T.M.A.N.] [PATCH linux-next] net: batman-adv: use "__packed __aligned(2)" for each structure instead of "__packed(2)" region
Date: Sun, 19 Jan 2014 17:51:25 +0800 [thread overview]
Message-ID: <52DBA01D.6040000@gmail.com> (raw)
In-Reply-To: <52DB9B39.9090502@meshcoding.com>
On 01/19/2014 05:30 PM, Antonio Quartulli wrote:
> On 19/01/14 02:10, James Hogan wrote:
>>
>> It appears that the following gcc patch adds support for #pragma pack:
>> http://gcc.gnu.org/ml/gcc-patches/2006-10/msg01115.html
>>
>> I gave it a quick spin on metag gcc (which is unfortunately stuck on an old
>> version) and it seems to fix my simple test case so that #pragma pack(2)
>> becomes equivalent to __packed __aligned(2) (for sizeof and __alignof__).
>>
>
> Then I personally think that it is better to fix metag gcc instead of
> changing the kernel.
>
> Actually there are many different spots where "#pragma pack" is used.
> batman-adv is just the only one having compile time checks for structure
> sizes.
>
What Antonio said sounds reasonable to me.
>>
>> However, the __packed and __aligned are linux specific macros to abstract
>> compiler details, whereas #pragma pack appears to be a compiler-specific WIN32
>> style equivalent to GCC's __attribute__((packed)) and
>> __attribute__((aligned(2))) (these are what __packed and __aligned use in
>> compiler-gcc.h).
>>
>> Therefore I believe using the Linux abstractions is still more correct here.
>
> If you really think so, I'd suggest to grep in the kernel and catch all
> the other occurrences of "#pragma pack" and change them all (assuming
> that using __attribute__((aligned(2))) is the way to go).
>
Thanks.
--
Chen Gang
Open, share and attitude like air, water and life which God blessed
WARNING: multiple messages have this Message-ID (diff)
From: Chen Gang <gang.chen.5i5j@gmail.com>
To: Antonio Quartulli <antonio@meshcoding.com>
Cc: James Hogan <james.hogan@imgtec.com>,
David Miller <davem@davemloft.net>,
mareklindner@neomailbox.ch, sw@simonwunderlich.de,
b.a.t.m.a.n@lists.open-mesh.org, netdev <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux-metag@vger.kernel.org,
Dan Carpenter <dan.carpenter@oracle.com>,
Greg KH <gregkh@linuxfoundation.org>
Subject: Re: [PATCH linux-next] net: batman-adv: use "__packed __aligned(2)" for each structure instead of "__packed(2)" region
Date: Sun, 19 Jan 2014 17:51:25 +0800 [thread overview]
Message-ID: <52DBA01D.6040000@gmail.com> (raw)
In-Reply-To: <52DB9B39.9090502@meshcoding.com>
On 01/19/2014 05:30 PM, Antonio Quartulli wrote:
> On 19/01/14 02:10, James Hogan wrote:
>>
>> It appears that the following gcc patch adds support for #pragma pack:
>> http://gcc.gnu.org/ml/gcc-patches/2006-10/msg01115.html
>>
>> I gave it a quick spin on metag gcc (which is unfortunately stuck on an old
>> version) and it seems to fix my simple test case so that #pragma pack(2)
>> becomes equivalent to __packed __aligned(2) (for sizeof and __alignof__).
>>
>
> Then I personally think that it is better to fix metag gcc instead of
> changing the kernel.
>
> Actually there are many different spots where "#pragma pack" is used.
> batman-adv is just the only one having compile time checks for structure
> sizes.
>
What Antonio said sounds reasonable to me.
>>
>> However, the __packed and __aligned are linux specific macros to abstract
>> compiler details, whereas #pragma pack appears to be a compiler-specific WIN32
>> style equivalent to GCC's __attribute__((packed)) and
>> __attribute__((aligned(2))) (these are what __packed and __aligned use in
>> compiler-gcc.h).
>>
>> Therefore I believe using the Linux abstractions is still more correct here.
>
> If you really think so, I'd suggest to grep in the kernel and catch all
> the other occurrences of "#pragma pack" and change them all (assuming
> that using __attribute__((aligned(2))) is the way to go).
>
Thanks.
--
Chen Gang
Open, share and attitude like air, water and life which God blessed
next prev parent reply other threads:[~2014-01-19 9:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-18 11:31 [B.A.T.M.A.N.] [PATCH linux-next] net: batman-adv: use "__packed __aligned(2)" for each structure instead of "__packed(2)" region Chen Gang
2014-01-18 11:31 ` Chen Gang
2014-01-18 11:31 ` Chen Gang
2014-01-18 13:03 ` [B.A.T.M.A.N.] " Antonio Quartulli
2014-01-18 13:03 ` Antonio Quartulli
2014-01-18 13:03 ` Antonio Quartulli
2014-01-19 1:10 ` [B.A.T.M.A.N.] " James Hogan
2014-01-19 1:10 ` James Hogan
2014-01-19 9:30 ` [B.A.T.M.A.N.] " Antonio Quartulli
2014-01-19 9:30 ` Antonio Quartulli
2014-01-19 9:30 ` Antonio Quartulli
2014-01-19 9:51 ` Chen Gang [this message]
2014-01-19 9:51 ` Chen Gang
2014-01-20 11:28 ` [B.A.T.M.A.N.] " James Hogan
2014-01-20 11:28 ` James Hogan
2014-01-20 11:28 ` James Hogan
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=52DBA01D.6040000@gmail.com \
--to=gang.chen.5i5j@gmail.com \
--cc=antonio@meshcoding.com \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=dan.carpenter@oracle.com \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=james.hogan@imgtec.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-metag@vger.kernel.org \
--cc=mareklindner@neomailbox.ch \
--cc=netdev@vger.kernel.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 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.