Path: utzoo!attcan!uunet!husc6!bloom-beacon!tut.cis.ohio-state.edu!mailrus!ames!haven!ncifcrf!nlm-mcs!adm!smoke!gwyn
From: gwyn@smoke.ARPA (Doug Gwyn )
Newsgroups: comp.lang.c
Subject: Re: lint on malloc calls
Keywords: malloc lint pointer
Message-ID: <8472@smoke.ARPA>
Date: 9 Sep 88 10:05:50 GMT
References: <39617@linus.UUCP>
Reply-To: gwyn@brl.arpa (Doug Gwyn (VLD/VMB) <gwyn>)
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 11

In article <39617@linus.UUCP> jgb@linus.UUCP (Jonathan G. Bressel) writes:
>	nextentry = (entry *) malloc(sizeof(entry));

That's correct.

>	phone.c(61): warning: illegal pointer combination
>	phone.c(61): warning: possible pointer alignment problem

"lint" doesn't know that malloc() always returns a suitably-aligned pointer.
There really isn't any way to prevent these warnings (other than changing
the code that "lint" sees).