[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Tinycc-devel] Possible to don't stop on first error?

From: Milan Nikolic
Subject: [Tinycc-devel] Possible to don't stop on first error?
Date: Wed, 11 Apr 2018 16:11:50 +0200


Is it possible for tcc to don't exit on first error? For example, with tcc:

# tcc /temp/test.c 
not-type:1: error: '__cgo_undefined__2' undeclared

And with gcc:

not-type: In function '__cgo_f_1_2':
not-type:1:33: error: '__cgo_undefined__2' undeclared (first use in this function); did you mean '__ino_t_defined'?
not-type:1:33: note: each undeclared identifier is reported only once for each function it appears in
not-int-const: In function '__cgo_f_1_3':
not-int-const:1:61: error: invalid operands to binary * (have 'void (*)()' and 'int')
not-num-const: In function '__cgo_f_1_4':
not-num-const:1:67: error: incompatible types when initializing type 'double' using type 'void (*)()'
not-str-lit: In function '__cgo_f_1_5':
not-str-lit:1:67: error: invalid initializer
completed: At top level:
completed:1:16: error: '__cgo__2' undeclared here (not in a function); did you mean '__cgo__1'?
completed:1:16: warning: initialization makes integer from pointer without a cast [-Wint-conversion]
completed:1:16: error: initializer element is not constant

Something like this is actually used in Golang cgo, to check types, e. g. https://github.com/golang/go/blob/master/src/cmd/cgo/gcc.go#L281 .

I wanted to try and use tcc with Go instead of gcc, --enable-cross option is super cool!


reply via email to

[Prev in Thread] Current Thread [Next in Thread]