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 driver/114330] New: needs_preprocessing field of struct compiler is unused Date: Wed, 13 Mar 2024 22:15:23 +0000 [thread overview] Message-ID: <bug-114330-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114330 Bug ID: 114330 Summary: needs_preprocessing field of struct compiler is unused Product: gcc Version: 14.0 Status: UNCONFIRMED Keywords: internal-improvement Severity: enhancement Priority: P3 Component: driver Assignee: unassigned at gcc dot gnu.org Reporter: pinskia at gcc dot gnu.org Target Milestone: --- I suspect needs_preprocessing field became unused when the C preprocessor became itergrated into the cc1. while it does not hurt anything to have the field still around and only the ".c" sets it to true, it seems like a decent idea to remove the field. Also note it might be useful to boolize combinable in struct compiler in gcc.cc too.
next reply other threads:[~2024-03-13 22:15 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-03-13 22:15 pinskia at gcc dot gnu.org [this message] 2024-03-13 22:16 ` [Bug driver/114330] " pinskia at gcc dot gnu.org 2024-03-14 1:18 ` sjames at gcc dot gnu.org 2024-03-14 1:19 ` sjames at gcc dot gnu.org 2024-03-14 1:52 ` pinskia at gcc dot gnu.org 2024-04-16 19:49 ` pinskia 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-114330-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).