topic Re: C compiler warning in Operating System - Linux

C compiler warning

Nivel — Thu, 10 Apr 2008 14:28:44 GMT

I am trying to clear C compiler warnings. For the attached program extract (a function StringsToArray, used to place a variable number of strings into an array), 3 compiler warnings are issued for each line:
str = (char *)va_arg(pvar,char *)
The warnings are all the same "Casting from loose to strict alignment".
When ANSI migration warnings are asked for instead, a different warning for the same lines is issued "Large unsuffixed integer constant will be type unsigned integer in ANSI-C".
Can anyone help?

Re: C compiler warning

Steven Schweda — Thu, 10 Apr 2008 16:46:52 GMT

HP-UX, C compiler versions?
Actual compiler command(s)?

Re: C compiler warning

Dennis Handly — Fri, 11 Apr 2008 00:37:33 GMT

>3 compiler warnings are issued for each line: str = va_arg(pvar,char*)
>"Casting from loose to strict alignment".

I only see one per line.

>When ANSI migration warnings are asked for instead, "Large unsuffixed integer constant will be type unsigned integer in ANSI-C".

These are known problems in , even on 11.31:
JAGag11411: Warning 706 when using varargs.h +M0
JAGae16638: Warnings 530 on va_arg using varargs.h

I don't see any patches for this header.
I do see it incorrectly listed on:
PHSS_36092 PHSS_36089 PHSS_36086 PHSS_28706

You can of course just edit your copy of . :-)

>Steven: C compiler versions?

These are PA header file problems with .

Re: C compiler warning

Nivel — Fri, 11 Apr 2008 12:17:44 GMT

Compiler: HP C/HP UX Version B.11.11.16
Compiler command:
cc +w1 -DSYSV -Aa -D_HPUX_SOURCE -DXOPEN_CATALOG -DXT_CODE

Included NOT

Re: C compiler warning

Steven Schweda — Fri, 11 Apr 2008 14:35:32 GMT

> HP-UX, C compiler versions?

> Compiler: HP C/HP UX Version B.11.11.16

That's a start. Should I need to guess the
HP-UX version (and hardware architecture), or
did you think that I knew enough to infer it
from the compiler version? (Ha!)

Re: C compiler warning

Torsten. — Fri, 11 Apr 2008 14:44:28 GMT

I would guess its 11.11 and PA-RISC because of this ...

;-))

Re: C compiler warning

Dennis Handly — Fri, 11 Apr 2008 19:25:33 GMT

>HP C/HP UX Version B.11.11.16
>Included NOT

Yes but is just a wrapper around .

>Steven: Should I need to guess the HP-UX version

No need. ALL PA versions are broken.
But you have a very valid point, answers to both questions should be supplied, even though redundant in this case.

>did you think that I knew enough to infer it
from the compiler version?

Yes, it is encoded. And anyone who can answer Nev's question would know this. :-)

Re: C compiler warning

Nivel — Mon, 14 Apr 2008 07:02:55 GMT

Thanks Dennis.
HP-UX version is 11i v1 (11.11i)
Workstation is C8000 (PA-RISC)
Interesting that the warnings I have seen (530 and 706) are the two that you have indicated occur because of the known problems with varargs.h

Re: C compiler warning

Dennis Handly — Mon, 14 Apr 2008 09:20:18 GMT

>Interesting that the warnings I have seen (530 and 706) are the two that you have indicated occur because of the known problems with varargs.h.

Why should be interesting? If you never supply a patch, it will never be fixed for customers.

Re: C compiler warning

Nivel — Tue, 15 Apr 2008 08:52:48 GMT

I have installed patch PHSS_36086 (the only one relevant to my compiler / HP UX version). The warnings as described in my original post are still issued.
Any more ideas?
Thanks in advance.

Re: C compiler warning

Dennis Handly — Tue, 15 Apr 2008 09:02:19 GMT

>I have installed patch PHSS_36086

I have already said that the patch document is incorrect, it doesn't fix the problem because it doesn't supply .

>>I don't see any patches for this header.
>>I do see it incorrectly listed on:

If you have a support contract, you should contact the Response Center and mention that fixes for these two bugs weren't delivered and you need a patch.

Re: C compiler warning

Nivel — Wed, 30 Apr 2008 14:21:12 GMT

No solution was forthcoming from the replies received, but I managed to find a work-around in my code such that I did not need to use a function with a variable number of args.