https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60100
Eric Gallager changed:
What|Removed |Added
Keywords||diagnostic
Status|WAITING
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60100
Andreas Schwab changed:
What|Removed |Added
CC||gccbugs at dima dot
secretsauce.ne
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60100
--- Comment #10 from lavr at ncbi dot nlm.nih.gov ---
> I guess also a dup of PR57201.
While I can agree these cases (and the one mentioned within PR57201) look
similar, the gravity of the disappearing warning in case of a mismatched type
is more
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60100
--- Comment #9 from Marek Polacek ---
I guess also a dup of PR57201.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60100
--- Comment #8 from lavr at ncbi dot nlm.nih.gov ---
This is the code from the original .c file that fails to post a warning.
sock->w_len -= BUF_PeekAtCB(sock->w_buf,
BUF_Size(sock->w_buf) - sock->w_len,
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60100
--- Comment #7 from Andreas Schwab ---
# 3416 "/home/lavr/cxx/src/connect/ncbi_socket.c" 3 4
The file is marked as system header, perhaps because the expansion on this line
came from a system header? (looks like assert(...)) Note that there are
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60100
--- Comment #6 from lavr at ncbi dot nlm.nih.gov ---
The .c file has a lot of headers included. Do you want all of them, as well?
OTOH, the code in the preprocessed file clearly shows the use of a function
pointer of mismatched type gone un-warned
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60100
Marek Polacek changed:
What|Removed |Added
Status|UNCONFIRMED |WAITING
Last reconfirmed|
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60100
--- Comment #4 from lavr at ncbi dot nlm.nih.gov ---
Created attachment 32072
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=32072&action=edit
Preprocessed C source that fails to produce a warning when compiled
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60100
--- Comment #3 from lavr at ncbi dot nlm.nih.gov ---
Ok, sorry and let me start again. My original mockup case wasn't good enough.
So attached is the real (preprocessed) code that fails to produce a warning
(yet when compiled from the .c form, th
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60100
--- Comment #2 from lavr at ncbi dot nlm.nih.gov ---
> Because your command line did not actual compile anything.
Indeed. with .i I see the warning again. But I can't see
any warning if the precompiled file is processed through distcc...
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60100
--- Comment #1 from Andrew Pinski ---
>Also, I'm not sure why there is a bogus warning about linking here (and not
>when
compiling right from the source file, above).
Because your command line did not actual compile anything. Use the .i suffix
12 matches
Mail list logo
