From: Xi Ruoyao <xry111@xry111.site>
To: mizo 91 <mizo91@gmail.com>, LIU Hao <lh_mouse@126.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: CreateProcess No such file or directory
Date: Sat, 24 Sep 2022 01:40:08 +0800 [thread overview]
Message-ID: <90f24cd806655b052a2d1ac190e6b2ed53fbbfce.camel@xry111.site> (raw)
In-Reply-To: <CAGt5VgEKzro0uo5qQaqPZLc=Fpcw4_sLYC_-CFyGxYGWSmqAtg@mail.gmail.com>
On Thu, 2022-09-22 at 18:50 +0200, mizo 91 via Gcc-help wrote:
> Additionaly isnt -I flags required for preprocessor only? Why gcc is
> trying to pass -I arguments to assembler program? Wouldnt you consider this
> gcc driver bug than?
From GNU assembler manual:
-I dir
Add directory dir to the search list for ".include" directives.
So -I flags may be for preprocessor, or for assembler.
> Ok, if indeed this is a system limitation that cannot be avoided then why
> is the clang compiler not having this problem?
Because clang emits an object file without invoking an assembler. This
is a difference in the fundamental design of the two compilers, and you
can't change it just for some looooooong command line.
--
Xi Ruoyao <xry111@xry111.site>
School of Aerospace Science and Technology, Xidian University
next prev parent reply other threads:[~2022-09-23 17:40 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-20 16:02 mizo 91
2022-09-20 16:18 ` Richard Earnshaw
2022-09-20 17:17 ` mizo 91
2022-09-20 22:27 ` Tamar Christina
2022-09-21 2:42 ` fedor_qd
2022-09-21 15:27 ` mizo 91
2022-09-21 15:41 ` Tom Kacvinsky
2022-09-26 6:58 ` Re[2]: " fedor_qd
2022-09-22 6:44 ` LIU Hao
2022-09-22 7:35 ` mizo 91
2022-09-22 9:46 ` LIU Hao
2022-09-22 14:55 ` mizo 91
2022-09-22 16:04 ` LIU Hao
2022-09-22 16:50 ` mizo 91
2022-09-23 17:40 ` Xi Ruoyao [this message]
2022-09-23 21:11 ` mizo 91
2022-09-24 5:13 ` Xi Ruoyao
2022-09-24 9:28 ` mizo 91
2022-09-24 9:51 ` Xi Ruoyao
2022-09-24 10:20 ` Jonathan Wakely
2022-09-23 17:14 ` David Brown
2022-09-23 20:55 ` mizo 91
2022-09-22 8:19 ` Jonathan Wakely
2022-09-22 8:42 ` Jonathan Wakely
2022-09-22 9:48 ` LIU Hao
2022-09-22 9:50 ` mizo 91
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=90f24cd806655b052a2d1ac190e6b2ed53fbbfce.camel@xry111.site \
--to=xry111@xry111.site \
--cc=gcc-help@gcc.gnu.org \
--cc=lh_mouse@126.com \
--cc=mizo91@gmail.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).