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/111527] COLLECT_GCC_OPTIONS option hits single-variable limits too early
Date: Sat, 18 May 2024 21:33:37 +0000	[thread overview]
Message-ID: <bug-111527-4-xYfnBSQYk8@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111527-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111527

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Last reconfirmed|                            |2024-05-18
     Ever confirmed|0                           |1
             Status|UNCONFIRMED                 |NEW

--- Comment #11 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Note using "/tmp/rsp.txt" is not acceptable at all since there might be a few
linking happening on the machine. You should use make_at_file (which will make
either a tmp file which will be deleted at the end compiling or an .args.N file
which can be looked at if used with -save-temps) instead from gcc.cc and then
pass the filename to collect2 as "@filename" and then inside collect2 expand as
needed.

      parent reply	other threads:[~2024-05-18 21:33 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-21 19:06 [Bug driver/111527] New: " slyfox at gcc dot gnu.org
2023-09-22  5:22 ` [Bug driver/111527] " rguenth at gcc dot gnu.org
2023-09-22  8:15 ` slyfox at gcc dot gnu.org
2024-03-16  9:52 ` deepadeepthi98 at gmail dot com
2024-03-16  9:53 ` deepadeepthi98 at gmail dot com
2024-03-16 20:18 ` slyfox at gcc dot gnu.org
2024-05-06 11:39 ` deepadeepthi98 at gmail dot com
2024-05-06 11:42 ` deepadeepthi98 at gmail dot com
2024-05-06 16:02 ` pinskia at gcc dot gnu.org
2024-05-15 10:58 ` deepadeepthi98 at gmail dot com
2024-05-15 11:00 ` deepadeepthi98 at gmail dot com
2024-05-18 21:33 ` pinskia at gcc dot gnu.org [this message]

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-111527-4-xYfnBSQYk8@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).