From: Costas Argyris <costas.argyris@gmail.com>
To: gcc-patches@gcc.gnu.org
Subject: [PATCH] gcc-ar: Handle response files properly [PR77576]
Date: Sat, 1 Jul 2023 22:45:50 +0100 [thread overview]
Message-ID: <CAHyHGCkNf173Xp1FVDpSBJ9whQJwxeFxbKek6qpY1U8tHbaRdw@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 399 bytes --]
Basically implementing what Andrew said in the PR:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77576
If @file has been passed to gcc-ar, do the following:
1) Expand it to get an argv without any @files.
2) Then apply the plugin modifications to argv.
3) Create temporary response file.
4) Put the modified argv in the temporary file.
5) Call ar with @tmp.
6) Delete the temporary response file.
[-- Attachment #2: 0001-gcc-ar-Handle-response-files-properly-PR77576.patch --]
[-- Type: application/octet-stream, Size: 2896 bytes --]
From 1eb857daa1cdc75827efeb609f91c90b1dd539eb Mon Sep 17 00:00:00 2001
From: Costas Argyris <costas.argyris@gmail.com>
Date: Sat, 1 Jul 2023 22:00:44 +0100
Subject: [PATCH] gcc-ar: Handle response files properly [PR77576]
If @file has been passed to gcc-ar, do the following:
1) Expand it to get an argv without any @files.
2) Then apply the plugin modifications to argv.
3) Create temporary response file.
4) Put the modified argv in the temporary file.
5) Call ar with @tmp.
6) Delete the temporary response file.
Signed-off-by: Costas Argyris <costas.argyris@gmail.com>
---
gcc/gcc-ar.cc | 47 +++++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 47 insertions(+)
diff --git a/gcc/gcc-ar.cc b/gcc/gcc-ar.cc
index 4e4c525927d..417c4913793 100644
--- a/gcc/gcc-ar.cc
+++ b/gcc/gcc-ar.cc
@@ -135,6 +135,10 @@ main (int ac, char **av)
int k, status, err;
const char *err_msg;
const char **nargv;
+ char **old_argv;
+ const char *rsp_file = NULL;
+ const char *rsp_arg = NULL;
+ const char *rsp_argv[3];
bool is_ar = !strcmp (PERSONALITY, "ar");
int exit_code = FATAL_EXIT_CODE;
int i;
@@ -209,6 +213,13 @@ main (int ac, char **av)
}
}
+ /* Expand any @files before modifying the command line
+ and use a temporary response file if there were any. */
+ old_argv = av;
+ expandargv (&ac, &av);
+ if (av != old_argv)
+ rsp_file = make_temp_file ("");
+
/* Prepend - if necessary. */
if (is_ar && av[1] && av[1][0] != '-')
av[1] = concat ("-", av[1], NULL);
@@ -225,6 +236,39 @@ main (int ac, char **av)
nargv[j + k] = av[k];
nargv[j + k] = NULL;
+ /* If @file was passed, put nargv into the temporary response
+ file and then change it to a single @FILE argument, where
+ FILE is the temporary filename. */
+ if (rsp_file)
+ {
+ FILE *f;
+ int status;
+ f = fopen (rsp_file, "w");
+ if (f == NULL)
+ {
+ fprintf (stderr, "Cannot open temporary file %s\n", rsp_file);
+ exit (1);
+ }
+ status = writeargv (
+ CONST_CAST2 (char * const *, const char **, nargv) + 1, f);
+ if (status)
+ {
+ fprintf (stderr, "Cannot write to temporary file %s\n", rsp_file);
+ exit (1);
+ }
+ status = fclose (f);
+ if (EOF == status)
+ {
+ fprintf (stderr, "Cannot close temporary file %s\n", rsp_file);
+ exit (1);
+ }
+ rsp_arg = concat ("@", rsp_file, NULL);
+ rsp_argv[0] = nargv[0];
+ rsp_argv[1] = rsp_arg;
+ rsp_argv[2] = NULL;
+ nargv = rsp_argv;
+ }
+
/* Run utility */
/* ??? the const is misplaced in pex_one's argv? */
err_msg = pex_one (PEX_LAST|PEX_SEARCH,
@@ -249,5 +293,8 @@ main (int ac, char **av)
else
exit_code = SUCCESS_EXIT_CODE;
+ if (rsp_file)
+ unlink (rsp_file);
+
return exit_code;
}
--
2.30.2
next reply other threads:[~2023-07-01 21:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-01 21:45 Costas Argyris [this message]
2023-07-03 11:07 ` Costas Argyris
2023-07-07 10:33 ` Costas Argyris
2023-07-07 12:00 ` Costas Argyris
2023-07-14 8:05 ` Costas Argyris
2023-07-28 11:59 ` Costas Argyris
2023-07-28 21:11 ` Joseph Myers
2023-07-31 16:58 ` Jeff Law
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=CAHyHGCkNf173Xp1FVDpSBJ9whQJwxeFxbKek6qpY1U8tHbaRdw@mail.gmail.com \
--to=costas.argyris@gmail.com \
--cc=gcc-patches@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).