From: Pierre-Marie de Rodat <derodat@adacore.com>
To: gcc-patches@gcc.gnu.org
Cc: Richard Kenner <kenner@adacore.com>
Subject: [Ada] Create object file for ignored ghost compilation unit
Date: Wed, 1 Dec 2021 10:25:40 +0000 [thread overview]
Message-ID: <20211201102540.GA1635280@adacore.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 467 bytes --]
If the compilation unit we're compiling is an ignored ghost, we need to
ensure that an object file is generated. This happens automatically for
the GCC backend since it always generates the .o file, but for GNAT
LLVM, the backend isn't called. So we need to be sure that we explicitly
generate the file.
Tested on x86_64-pc-linux-gnu, committed on trunk
gcc/ada/
* gnat1drv.adb (Gnat1drv): Force generation of object file if
compilation unit is an ignored ghost.
[-- Attachment #2: patch.diff --]
[-- Type: text/x-diff, Size: 1262 bytes --]
diff --git a/gcc/ada/gnat1drv.adb b/gcc/ada/gnat1drv.adb
--- a/gcc/ada/gnat1drv.adb
+++ b/gcc/ada/gnat1drv.adb
@@ -1415,18 +1415,19 @@ begin
if Back_End_Mode = Skip then
- -- An ignored Ghost unit is rewritten into a null statement because
- -- it must not produce an ALI or object file. Do not emit any errors
- -- related to code generation because the unit does not exist.
+ -- An ignored Ghost unit is rewritten into a null statement. Do
+ -- not emit any errors related to code generation because the
+ -- unit does not exist.
if Is_Ignored_Ghost_Unit (Main_Unit_Node) then
-- Exit the gnat driver with success, otherwise external builders
-- such as gnatmake and gprbuild will treat the compilation of an
- -- ignored Ghost unit as a failure. Note that this will produce
- -- an empty object file for the unit.
+ -- ignored Ghost unit as a failure. Be sure we produce an empty
+ -- object file for the unit.
Ecode := E_Success;
+ Back_End.Gen_Or_Update_Object_File;
-- Otherwise the unit is missing a crucial piece that prevents code
-- generation.
reply other threads:[~2021-12-01 10:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20211201102540.GA1635280@adacore.com \
--to=derodat@adacore.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=kenner@adacore.com \
/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).