Compiler warning on struct initialization...

**Mohan** · Jul 13 '07, 10:25 AM

Re: Compiler warning on struct initialization. ..

On Jul 13, 2:59 pm, Daniel Rudy <spamt...@spamt his.netwrote:

Hello Group.
>
Please consider the following code:
>
/* this table is used in the wipedevice routine */
static const struct wipe_t
{
uchar wte[3]; /* wipe table entry */
} wipetable[] = {
{0x00, 0x00, 0x00},
{0x92, 0x29, 0x24},
{0x6D, 0xB6, 0xDB},
{0xFF, 0xFF, 0xFF},
{0x92, 0x29, 0x24},
{0x6D, 0xB6, 0xDB},
{0xAA, 0xAA, 0xAA},
{0x92, 0x29, 0x24},
{0x6D, 0xB6, 0xDB},
{0x55, 0x55, 0x55},
{0x92, 0x29, 0x24},
{0x6D, 0xB6, 0xDB},
{0x00, 0x00, 0x00}
};
>
When I compile the module, I'm getting the following error:
>
fs_dev.c:83: warning: missing braces around initializer
fs_dev.c:83: warning: (near initialization for `wipetable[0].wte')
>

An extra set of braces required in the above initialization.
Because the structure has an array member.

wipetable[] = {
{ {0x00, 0x00, 0x00} },
...
};

Mohan

**mark_bluemel@pobox.com** · Jul 13 '07, 10:35 AM

Re: Compiler warning on struct initialization. ..

On 13 Jul, 10:59, Daniel Rudy <spamt...@spamt his.netwrote:

Hello Group.
>
Please consider the following code:
>
/* this table is used in the wipedevice routine */
static const struct wipe_t
{
uchar wte[3]; /* wipe table entry */
} wipetable[] = {
{0x00, 0x00, 0x00},

....

};

This is a somewhat special case of a struct - with only one element.

>
When I compile the module, I'm getting the following error:
>
fs_dev.c:83: warning: missing braces around initializer
fs_dev.c:83: warning: (near initialization for `wipetable[0].wte')

In the line "{0x00, 0x00, 0x00}," the braces wrap the initialization
of the array.
In the context of the larger array of structs, each struct initializer
should also be braced.

When I used "{ {0x00, 0x00, 0x00} }," for the first line of the
initialization, I found that
the error moved on one line, confirming (or at least reinforcing) my
understanding of the issue.

[Over to the language lawyers to correct me]

**Army1987** · Jul 13 '07, 12:05 PM

[OT] Re: Compiler warning on struct initialization. ..

On Fri, 13 Jul 2007 09:59:07 +0000, Daniel Rudy wrote:
[snip]

Any ideas as to what the compiler is complaining about? I'm using

gcc

on FreeBSD. The command line is as follows:
>
gcc -W -Wall -Wshadow -Wpointer-arith -Wcast-align -Wstrict-prototypes
-Wnested-externs -Wwrite-strings -Wfloat-equal -Winline -Wtrigraphs
-ansi -std=c89 -pedantic -ggdb3 -c -o fs_dev.o fs_dev.c

^^ ^^
Aren't those two synonymous?
--
Army1987 (Replace "NOSPAM" with "email")
"Never attribute to malice that which can be adequately explained
by stupidity." -- R. J. Hanlon (?)

**Daniel Rudy** · Jul 13 '07, 04:55 PM

Re: Compiler warning on struct initialization. ..

At about the time of 7/13/2007 3:28 AM, mark_bluemel@po box.com stated
the following:

On 13 Jul, 10:59, Daniel Rudy <spamt...@spamt his.netwrote:

>Hello Group.
>>
>Please consider the following code:
>>
>/* this table is used in the wipedevice routine */
>static const struct wipe_t
> {
> uchar wte[3]; /* wipe table entry */
> } wipetable[] = {
> {0x00, 0x00, 0x00},

...

> };

>
This is a somewhat special case of a struct - with only one element.
>

>When I compile the module, I'm getting the following error:
>>
>fs_dev.c:83: warning: missing braces around initializer
>fs_dev.c:83: warning: (near initialization for `wipetable[0].wte')

>
In the line "{0x00, 0x00, 0x00}," the braces wrap the initialization
of the array.
In the context of the larger array of structs, each struct initializer
should also be braced.

That explains it, and corrects it. Thanks.

When I used "{ {0x00, 0x00, 0x00} }," for the first line of the
initialization, I found that
the error moved on one line, confirming (or at least reinforcing) my
understanding of the issue.
>
[Over to the language lawyers to correct me]
>

--
Daniel Rudy

Email address has been base64 encoded to reduce spam
Decode email address using b64decode or uudecode -m

Why geeks like computers: look chat date touch grep make unzip
strip view finger mount fsck more fsck yes spray umount sleep

**Chris Torek** · Jul 13 '07, 06:45 PM

Re: Compiler warning on struct initialization. ..

In article <L1Ili.21748$RX .4005@newssvr11 .news.prodigy.n et>,
Daniel Rudy <ZGNydWR5QHBhY2 JlbGwubmV0wrote :

[some rearrangement and vertical compression applied]

>#define uchar unsigned char
>static const struct wipe_t {
uchar wte[3]; /* wipe table entry */
} wipetable[] = {

So, "wipetable" has type "array ? of struct ...", where the
question-mark (representing an unknown-as-yet size) will be
filled in by the number of elements initialized.

The struct has type "struct wipe_t", and contains one member,
"wte". This memeber has type "array 3 of unsigned char".

The final opening brace above begins the initializer for the
outermost array, i.e., "wipetable" itself.

{0x00, 0x00, 0x00},

This line has an open brace, a list of values, and a close brace.

The open brace can be applied to the "next available aggregate".
Aggregate types include both arrays and structures, and the next
available one is "struct wipe_t".

That uses up the open brace, so that we just have the three values.
The thing to be initialized at this point is an array, which is
an aggregate, and logically "ought to" have an open brace.

{0x92, 0x29, 0x24},
{0x6D, 0xB6, 0xDB},
{0xFF, 0xFF, 0xFF},
{0x92, 0x29, 0x24},

[etc]

These go on to initialize wipetable[1], wipetable[2], and so on;
all of them have the same set of "missing" braces.

>When I compile the module, I'm getting the following error:
>
>fs_dev.c:83: warning: missing braces around initializer
>fs_dev.c:83: warning: (near initialization for `wipetable[0].wte')

which is what gcc produces when you have a partially-bracketed
initializer (as in this case), and you ask for the warning about
partially-bracketed initializers ("-Wmissing-braces", in at least
some versions, and implied by "-Wall").

>This code appears before the table above, and there is no problem:
>
>/* this table is used to help determine the CHS if the
device does not have or support CHS */
>static const struct chs_xla_t
{
uint32 count;
uint16 cyl;
uint16 head;
uint16 sect;
uint16 block;
} chs_xla[] = {

Here chs_xla has type "array ? of struct chs_xla_t". As before,
the question-mark will be filled in by the initializer. The struct
type has five elements, each an ordinary integer (assuming "the
usual" typedefs for uint32 and uint16 anyway).

{ 13668, 201, 4, 17, 68}, /* 7MB */

The open brace indicates the next available aggregate, i.e.,
the struct making up chs_xla[0]. Now we are down to the list
of values. The next "thing to be initialized" is an ordinary
integer, which does not require a brace, so chs_xla[0].count
is to be set to 13668. This leaves the 201 for chs_xla[0].cyl,
and so forth.

If any members of "struct chs_xla_t" had been aggregates themselves,
you would need more braces (at least, to remove the warning). For
instance:

struct foo {
int a;
int b[2];
int c;
} foo[] = {
{ 1, { 2, 3 }, 4 },
{ 9, { 8, 7 }, 6 },
};

would be fully-bracketed.

Nothing requires initializers in C to be fully-bracketed, although
it is probably usually a good idea anyway.
--
In-Real-Life: Chris Torek, Wind River Systems
Salt Lake City, UT, USA (40°39.22'N, 111°50.29'W) +1 801 277 2603
email: forget about it http://web.torek.net/torek/index.html
Reading email is like searching for food in the garbage, thanks to spammers.

**Keith Thompson** · Jul 13 '07, 08:25 PM

Re: Compiler warning on struct initialization. ..

Mohan <ajmrao@gmail.c omwrites:

On Jul 13, 2:59 pm, Daniel Rudy <spamt...@spamt his.netwrote:

>Please consider the following code:
>>
>/* this table is used in the wipedevice routine */
>static const struct wipe_t
> {
> uchar wte[3]; /* wipe table entry */
> } wipetable[] = {
> {0x00, 0x00, 0x00},
> {0x92, 0x29, 0x24},
> {0x6D, 0xB6, 0xDB},
> {0xFF, 0xFF, 0xFF},
> {0x92, 0x29, 0x24},
> {0x6D, 0xB6, 0xDB},
> {0xAA, 0xAA, 0xAA},
> {0x92, 0x29, 0x24},
> {0x6D, 0xB6, 0xDB},
> {0x55, 0x55, 0x55},
> {0x92, 0x29, 0x24},
> {0x6D, 0xB6, 0xDB},
> {0x00, 0x00, 0x00}
> };
>>
>When I compile the module, I'm getting the following error:
>>
>fs_dev.c:83: warning: missing braces around initializer
>fs_dev.c:83: warning: (near initialization for `wipetable[0].wte')
>>

>
An extra set of braces required in the above initialization.
Because the structure has an array member.
>
wipetable[] = {
{ {0x00, 0x00, 0x00} },
...
};

The extra braces are a good idea, but they're not actually required.
The language rules about braces in initializers are fairly lax. For
example, this:

int arr[2][2][2] = { 1, 2, 3, 4, 5, 6, 7, 8 };

is legal, even though this:

int arr[2][2][2] = { { {1, 2}, {3, 4} },
{ {5, 6}, {7, 8} } };

is clearer. The compiler is merely warning about the "missing" braces
(appropriately, IMHO); there's no constraint violation or syntax
error.

--
Keith Thompson (The_Other_Keit h) kst-u@mib.org <http://www.ghoti.net/~kst>
San Diego Supercomputer Center <* <http://users.sdsc.edu/~kst>
"We must do something. This is something. Therefore, we must do this."
-- Antony Jay and Jonathan Lynn, "Yes Minister"

Compiler warning on struct initialization...

Compiler warning on struct initialization...

Comment

Comment

Comment

Comment

Comment

Comment