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 target/108866] Allow to pass Windows resource file (.rc) as input to gcc
Date: Wed, 13 Mar 2024 22:06:14 +0000 [thread overview]
Message-ID: <bug-108866-4-knbAym4eTu@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108866-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108866
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
Last reconfirmed| |2024-03-13
Status|UNCONFIRMED |NEW
--- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Pali Rohár from comment #2)
> Andrew, I do not know what is gcc driver nor what to do for it. But if you
> can show me some pointers, I can try it.
>
> Or if you need more details about files, usage, etc... please let me know.
See gcc.cc (default_compilers).
It contains a mapping from suffix to language and language and how to
"compile/assemble" the files.
See also */lang-specs.h which are included via specs.h (specs.h is a generated
file while building, see the makefile there and depends on which language is
enabled).
Most likely you would add a new target macro which adds to that part of the
gcc.cc and define that macro in the mingw headers.
next prev parent reply other threads:[~2024-03-13 22:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-20 21:17 [Bug c/108866] New: " pali at kernel dot org
2023-02-20 21:24 ` [Bug target/108866] " pinskia at gcc dot gnu.org
2023-02-20 21:24 ` pinskia at gcc dot gnu.org
2024-03-13 21:46 ` pali at kernel dot org
2024-03-13 22:06 ` pinskia at gcc dot gnu.org [this message]
2024-03-14 13:55 ` amonakov at gcc dot gnu.org
2024-03-14 20:19 ` pali at kernel dot org
2024-03-14 20:23 ` pinskia at gcc dot gnu.org
2024-03-15 15:55 ` peter0x44 at disroot dot org
2024-03-15 17:27 ` pali at kernel dot org
2024-03-24 16:07 ` pali at kernel dot 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-108866-4-knbAym4eTu@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).