public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug web/104254] New: -freport-bug should be mentioned on https://gcc.gnu.org/bugs/
Date: Wed, 26 Jan 2022 22:42:36 +0000 [thread overview]
Message-ID: <bug-104254-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104254
Bug ID: 104254
Summary: -freport-bug should be mentioned on
https://gcc.gnu.org/bugs/
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Keywords: documentation
Severity: normal
Priority: P3
Component: web
Assignee: unassigned at gcc dot gnu.org
Reporter: pinskia at gcc dot gnu.org
Target Milestone: ---
Wile having -freport-bug is good, it is not mentioned on
https://gcc.gnu.org/bugs/ . Having it listed as another way of getting the
preprocessed source for an internal compiler error would be a good idea and
maybe even save some time for some users trying to find the preprocessed source
since it lists the file that needs to be attached in the error message.
next reply other threads:[~2022-01-26 22:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-26 22:42 pinskia at gcc dot gnu.org [this message]
2022-01-27 8:53 ` [Bug web/104254] " marxin at gcc dot gnu.org
2022-01-27 8:55 ` marxin at gcc dot gnu.org
2022-01-27 9:08 ` marxin at gcc dot gnu.org
2022-01-27 9:14 ` jakub at gcc dot gnu.org
2022-01-27 10:45 ` marxin at gcc dot gnu.org
2022-01-27 10:50 ` marxin at gcc dot gnu.org
2022-01-27 10:51 ` pinskia at gcc dot gnu.org
2022-01-27 12:34 ` cvs-commit 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-104254-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: link
Be 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).