public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "costas.argyris at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug driver/71850] @file should be used to cc1/cc1plus when @file is used
Date: Fri, 03 Mar 2023 11:30:36 +0000	[thread overview]
Message-ID: <bug-71850-4-nA2cDNo50P@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-71850-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #7 from Costas Argyris <costas.argyris at gmail dot com> ---
Created attachment 54575
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54575&action=edit
Treat include path args the same way between cpp_unique_options and asm_options

The proposed patch extends the logic already used for passing include paths
down to the compiler (when a @file was given to gcc), also to the assembler.   
This unifies the logic and also avoids overflowing the Windows command line
when many include paths have been passed to gcc through a @file.

  parent reply	other threads:[~2023-03-03 11:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-71850-4@http.gcc.gnu.org/bugzilla/>
2022-10-24 11:29 ` costas.argyris at gmail dot com
2023-03-03 11:30 ` costas.argyris at gmail dot com [this message]
2023-04-19  8:56 ` costas.argyris at gmail dot com
2023-06-14 17:04 ` costas.argyris at gmail dot com
2023-06-14 18:31 ` segher 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-71850-4-nA2cDNo50P@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).