public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
* missing gcc C comp
@ 1999-11-11 12:12 Aaron Sosnick
  1999-11-21 13:24 ` Martin v. Loewis
  1999-11-30 23:28 ` Aaron Sosnick
  0 siblings, 2 replies; 4+ messages in thread
From: Aaron Sosnick @ 1999-11-11 12:12 UTC (permalink / raw)
  To: gcc-help, gcc

Once upon a time gcc had some combination of command line options that
caused it to make noise when C code ignored the return value of a function:


extern int foo();

int main() {
    foo();  /* gcc could be made to moan about the ignored return value */
    exit(1);
}


It could, of course, be annoying when moaning about ignoring the
return of value of fprintf and other such functions whose
return values you had no use for.

Nonetheless, I liked having the option around.

Does anybody know what happened to this warning?

In the latest versions (2.95.x, 2.8.x) no amount of twiddling with the
various -W flags seems to be able to make it complain.

Did it go away or am I just missing something.

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: missing gcc C comp
  1999-11-11 12:12 missing gcc C comp Aaron Sosnick
@ 1999-11-21 13:24 ` Martin v. Loewis
  1999-11-30 23:28   ` Martin v. Loewis
  1999-11-30 23:28 ` Aaron Sosnick
  1 sibling, 1 reply; 4+ messages in thread
From: Martin v. Loewis @ 1999-11-21 13:24 UTC (permalink / raw)
  To: aaron; +Cc: gcc-help, gcc

> Did it go away or am I just missing something.

I can't find anything like that in the current sources, so it went
away (if it was ever there, which I'm not certain about).

Regards,
Martin

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: missing gcc C comp
  1999-11-21 13:24 ` Martin v. Loewis
@ 1999-11-30 23:28   ` Martin v. Loewis
  0 siblings, 0 replies; 4+ messages in thread
From: Martin v. Loewis @ 1999-11-30 23:28 UTC (permalink / raw)
  To: aaron; +Cc: gcc-help, gcc

> Did it go away or am I just missing something.

I can't find anything like that in the current sources, so it went
away (if it was ever there, which I'm not certain about).

Regards,
Martin

^ permalink raw reply	[flat|nested] 4+ messages in thread

* missing gcc C comp
  1999-11-11 12:12 missing gcc C comp Aaron Sosnick
  1999-11-21 13:24 ` Martin v. Loewis
@ 1999-11-30 23:28 ` Aaron Sosnick
  1 sibling, 0 replies; 4+ messages in thread
From: Aaron Sosnick @ 1999-11-30 23:28 UTC (permalink / raw)
  To: gcc-help, gcc

Once upon a time gcc had some combination of command line options that
caused it to make noise when C code ignored the return value of a function:


extern int foo();

int main() {
    foo();  /* gcc could be made to moan about the ignored return value */
    exit(1);
}


It could, of course, be annoying when moaning about ignoring the
return of value of fprintf and other such functions whose
return values you had no use for.

Nonetheless, I liked having the option around.

Does anybody know what happened to this warning?

In the latest versions (2.95.x, 2.8.x) no amount of twiddling with the
various -W flags seems to be able to make it complain.

Did it go away or am I just missing something.

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~1999-11-30 23:28 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
1999-11-11 12:12 missing gcc C comp Aaron Sosnick
1999-11-21 13:24 ` Martin v. Loewis
1999-11-30 23:28   ` Martin v. Loewis
1999-11-30 23:28 ` Aaron Sosnick

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).