public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "xry111 at mengyan1223 dot wang" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/95472] New: various diagnostics for C/C++ hyperlinks to gfortran doc Date: Tue, 02 Jun 2020 03:42:13 +0000 [thread overview] Message-ID: <bug-95472-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95472 Bug ID: 95472 Summary: various diagnostics for C/C++ hyperlinks to gfortran doc Product: gcc Version: 10.1.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: middle-end Assignee: unassigned at gcc dot gnu.org Reporter: xry111 at mengyan1223 dot wang Target Milestone: --- $ cat t1.c int main() { int x; return x; } $ gcc t1.c -Wall t1.c: In function 'main': t1.c:4:9: warning: 'x' is used uninitialized in this function [-Wuninitialized] 4 | return x; | ^ It looks OK, but in GCC-10 we have diagnostics with hyperlink. If you click "- Wuninitialized" you'll be diverted to gfortran doc: https://gcc.gnu.org/onlinedocs/gfortran/Error-and-Warning-Options.html#index-Wuninitialized This also happens to -Wreturn-type and -Wuninitialized. Strangely these two entries don't even exist in gfortran doc. But it does not happens to -Wformat or -Wimplicit-function-declaration etc.
next reply other threads:[~2020-06-02 3:42 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-06-02 3:42 xry111 at mengyan1223 dot wang [this message] 2020-06-02 3:45 ` [Bug middle-end/95472] " xry111 at mengyan1223 dot wang 2020-06-02 5:57 ` marxin at gcc dot gnu.org 2020-06-02 6:14 ` xry111 at mengyan1223 dot wang 2020-06-02 8:01 ` rguenth at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-95472-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
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).