confusing messages from clang
Steve Kargl
sgk at troutmask.apl.washington.edu
Sat Feb 20 01:15:40 UTC 2016
If anyone is interesting fixing FreeBSD's C compiler, it
would be appreciated.
% cat foo.c
#include <stdio.h>
#include <unistd.h>
void
foo(int i)
{
if (i < 0)
goto whoops;
if (i == 0)
printf("foo\n");
if (i > 0)
goto corrupt;
return;
whoops:
printf("whoops\n");
return
corrupt:
printf("corrupt\n");
}
% cc -c foo.c
foo.c:21:1: error: use of undeclared identifier 'corrupt'; did you mean 'crypt'?
corrupt:
^~~~~~~
crypt
/usr/include/unistd.h:450:7: note: 'crypt' declared here
char *crypt(const char *, const char *);
^
foo.c:21:8: error: expected ';' after return statement
corrupt:
^
;
foo.c:14:12: error: use of undeclared label 'corrupt'
goto corrupt;
^
3 errors generated.
No, I did not mean crypt. 'corrupt' is a defined label.
The missing semicolon occurs in line 19, but the line is
not properly identified in error output.
--
Steve
More information about the freebsd-toolchain
mailing list