public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "sray at live dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/110983] -fpatchable-function-entry is missing in Option Summary page Date: Tue, 29 Aug 2023 04:22:03 +0000 [thread overview] Message-ID: <bug-110983-4-9zGt6JS2sL@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110983-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110983 Mao <sray at live dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sray at live dot com --- Comment #3 from Mao <sray at live dot com> --- Created attachment 55810 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55810&action=edit invoke-doc-patch I think this can help fix the issue. I am not sure how to build the HTML web pages. But I also checked the man page. The fpatchable-function-entry is also missing in the manpage in the option summary section. And my fix can solve this issue. I still need more time to fight with the git-send-mail and my email provider before I can send this patch file to the gcc-patches mail list...
next prev parent reply other threads:[~2023-08-29 4:22 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-08-11 4:22 [Bug web/110983] New: " sray at live dot com 2023-08-11 4:43 ` [Bug middle-end/110983] " pinskia at gcc dot gnu.org 2023-08-16 6:11 ` sray at live dot com 2023-08-29 4:22 ` sray at live dot com [this message] 2023-08-29 4:25 ` pinskia at gcc dot gnu.org 2023-08-29 4:54 ` sray at live dot com 2023-09-18 5:33 ` sray at live dot com 2023-11-10 23:25 ` 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-110983-4-9zGt6JS2sL@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).