Programming This forum is for all programming questions.
The question does not have to be directly related to Linux and any language is fair game. |
| Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
 |
GNU/Linux Basic Guide
This 255-page guide will provide you with the keys to understand the philosophy of free software, teach you how to use and handle it, and give you the tools required to move easily in the world of GNU/Linux. Many users and administrators will be taking their first steps with this GNU/Linux Basic guide and it will show you how to approach and solve the problems you encounter.
Click Here to receive this Complete Guide absolutely free. |
|
 |
|
06-14-2004, 08:46 PM
|
#1
|
|
LQ Newbie
Registered: Dec 2003
Posts: 25
Rep:
|
What's this: __attribute__((packed))
I see some code about Hostap project,in these codes,I found some structure which have such signs: __attribute__((packed)),I don't know what does this mean. So soon I found more such signs in Linux Kernel Souce code.Who can tell me what does this mean exactly and how I use it?Thanks
|
|
|
|
06-14-2004, 09:59 PM
|
#2
|
|
Member
Registered: Aug 2003
Location: Planet Earth
Distribution: Ubuntu
Posts: 207
Rep:
|
Here is how I think it works (please correct me if I'm wrong!)
__attribute__((packed)) ensures that structure fields align on one-byte boundaries. If you want to ensure that your structures have the same size on all processors, the packed attribute is how you tell gcc.
As an example, let's define this structure:
Code:
struct s {
char aChar;
int anInt;
};
A processor that aligns on eight-byte boundaries may compile this so that aChar is in the first byte, followed by seven bytes of unused space, then starting anInt in the ninth byte.
A processor that aligns on four-byte boundaries may compile this so that aChar is in the first byte, followed by three bytes of unused space, then starting anInt in the fifth byte.
To force anInt to begin immediately after aChar, you would define the structure like this:
Code:
struct s {
char aChar;
int anInt __attribute__((packed));
};
To test these ideas out, I ran this code on an old Pentium 166:
Code:
#include <stdio.h>
struct s1 {
char a;
int i;
};
struct s2 {
char a;
int i __attribute__((packed));
};
int main( int argc, char* argv[] ) {
struct s1 s_1;
struct s2 s_2;
printf( "sizeof s1 is %d\n" , sizeof(s_1) );
printf( "sizeof s2 is %d\n" , sizeof(s_2) );
return( 0 );
}
And got these results:
Code:
eric.r.turner@turing:~/lab/packed$ ./foo
sizeof s1 is 8
sizeof s2 is 5
Looks like this processor aligns on four-byte boundaries.
Last edited by eric.r.turner; 06-14-2004 at 10:14 PM.
|
|
|
1 members found this post helpful.
|
06-14-2004, 11:58 PM
|
#3
|
|
LQ Newbie
Registered: Dec 2003
Posts: 25
Original Poster
Rep:
|
thanks a lot!
|
|
|
|
06-15-2004, 12:54 AM
|
#4
|
|
LQ Newbie
Registered: Dec 2003
Posts: 25
Original Poster
Rep:
|
But when I wirte the progarm like this:
struct s1 {
void *a;
char b[2];
int i;
};
struct s2 {
void *a
char b[2];
int i ;
}__attribute__((packed));
and got the result like this:
sizeof s1 is 12
sizeof s2 is 10
WHY? I think sizeof s2 should be 11!
|
|
|
|
06-15-2004, 01:56 AM
|
#5
|
|
Senior Member
Registered: Jan 2003
Posts: 2,786
|
Why would it be 11?
void *a => 32-bit processor means this is 32 bits wide (or 4 bytes)
char b[2] => a char is typically 1 byte. You have two of them. So b occupies 2 bytes
int i => most 32-bit machines also default to 32 bits for plain integers (again, 4 bytes)
So sizeof(a) + sizeof(b) + sizeof(i) = 4 + 2 + 4 = 10
For your non-packed structure, you processor is aligning to 4-byte boundaries. Thus, a fills one full 4-byte block, b fills two bytes of the next block (leaving 2 other bytes unused), and i occupies the next full 4-byte block. So, in that case:
sizeof(a) + sizeof(b) + sizeof(wasted space) + sizeof(i) = 4 + 2 + 2 + 4 = 12
|
|
|
|
06-15-2004, 03:20 AM
|
#6
|
|
LQ Newbie
Registered: Dec 2003
Posts: 25
Original Poster
Rep:
|
thanks,I made a mistake.
|
|
|
|
03-16-2011, 02:50 AM
|
#7
|
|
LQ Newbie
Registered: Mar 2011
Posts: 2
Rep:
|
struct s2 {
char a;
int i __attribute__ ((packed));
char b;
int i1;
};
(on 32-bit machine)
Its showing the size of this structure is 12. Can you plz tell me why ?
|
|
|
|
03-16-2011, 03:00 AM
|
#8
|
|
LQ Newbie
Registered: Mar 2011
Posts: 2
Rep:
|
Yup.. I found it..
Its allocating as follows,
1 byte + 4 bytes + 1 byte + 2 bytes + 4 bytes
char a, int i, char b, zeroes, int i1
|
|
|
|
03-16-2011, 07:16 AM
|
#9
|
|
Member
Registered: Aug 2003
Location: Planet Earth
Distribution: Ubuntu
Posts: 207
Rep:
|
Quote:
Originally Posted by vijayviji
Yup.. I found it..
|
LOL, this thread is nearly seven years old!
|
|
|
|
03-16-2011, 03:52 PM
|
#10
|
|
LQ Newbie
Registered: Mar 2011
Distribution: Fedora
Posts: 1
Rep:
|
I found this thread helpful. Thanks for the __attribute__ ((packed)) explaination.
|
|
|
|
09-11-2012, 01:52 AM
|
#11
|
|
LQ Newbie
Registered: Sep 2012
Posts: 1
Rep: 
|
hi ,
struct s2 {
char a;
int i __attribute__ ((packed));
char b;
int i1;
};
here sizeof(s2) = 12.
But actually size should be 10 ( 1 byte+4 bytes + 1 byte + 4 bytes ),how ?
how it would be ( 1 byte+4 bytes + 1 byte + 2 bytes + 4 bytes ) =
sizeof(a)+ sizeof(i) +sizeof(b)+ 2 zeros + sizeof(i1))
here what is this another 2 bytes ( 2 zeros ) ? Can anyone ,please explain ?
Thanks in advance .
regards,
Rajesh.
|
|
|
|
09-11-2012, 02:47 AM
|
#12
|
|
Senior Member
Registered: Oct 2011
Location: Budapest
Distribution: Debian/GNU/Linux, AIX
Posts: 1,034
|
You might want to use two packed's:
Code:
struct s2 {
char a;
int i __attribute__ ((packed));
char b;
int i1 __attribute__ ((packed));
};
But please note that this packed stuff:
- is a non-standard extension
- slows down the processing
- should be avoided
|
|
|
|
09-11-2012, 08:32 AM
|
#13
|
|
Member
Registered: Aug 2003
Location: Planet Earth
Distribution: Ubuntu
Posts: 207
Rep:
|
Quote:
Originally Posted by rajesh180186
hi ,
struct s2 {
char a;
int i __attribute__ ((packed));
char b;
int i1;
};
here sizeof(s2) = 12.
But actually size should be 10 ( 1 byte+4 bytes + 1 byte + 4 bytes ),how ?
how it would be ( 1 byte+4 bytes + 1 byte + 2 bytes + 4 bytes ) =
sizeof(a)+ sizeof(i) +sizeof(b)+ 2 zeros + sizeof(i1))
here what is this another 2 bytes ( 2 zeros ) ? Can anyone ,please explain ?
Thanks in advance .
regards,
Rajesh.
|
The processor is adding an extra two bytes after b so that the next integer starts on an 8 byte boundary. If you want the integer to start immediately after the char, you have to tell the processor to pack it.
|
|
|
|
09-11-2012, 09:03 AM
|
#14
|
|
Senior Member
Registered: Oct 2011
Location: Budapest
Distribution: Debian/GNU/Linux, AIX
Posts: 1,034
|
it's four, actually, not eight
|
|
|
|
09-11-2012, 09:37 AM
|
#15
|
|
Member
Registered: Feb 2005
Location: Sunnyvale, CA
Distribution: Ubuntu
Posts: 205
Rep:
|
Why not use the pack pragma to set the alignment around the structure? IE:
Code:
#pragma pack(1)
struct s2 {
char a;
int i;
char b;
int i1;
};
#pragma pack()
sizeof(struct s2): 10
Whereas:
Code:
struct s2 {
char a;
int i;
char b;
int i1;
};
sizeof(struct s2): 16
|
|
|
|
| Thread Tools |
Search this Thread |
|
|
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
All times are GMT -5. The time now is 02:07 PM.
|
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|