From: mizo 91 <mizo91@gmail.com>
To: Xi Ruoyao <xry111@xry111.site>
Cc: LIU Hao <lh_mouse@126.com>, gcc-help@gcc.gnu.org
Subject: Re: CreateProcess No such file or directory
Date: Sat, 24 Sep 2022 11:28:22 +0200 [thread overview]
Message-ID: <CAGt5VgFTLteAH1QyVn_7r2wHJab57enY3vrUMWU8UFi-D14msA@mail.gmail.com> (raw)
In-Reply-To: <ae10d3aad1633dfba99a11d157c3ea3682a361bb.camel@xry111.site>
[-- Attachment #1: Type: text/plain, Size: 1407 bytes --]
You are right that changing this behavior would have serious consequences.
But wouldn't you agree that gcc could somehow distinguish whether the input
files is of *.c or *.s source kind, and then decide if it should pass -I to
the assembler or the preprocessor or both? That would be more in line with
what I would expect after reading the documentation. Passing -I to the
assembler when invoking the command 'gcc -c source.c' seems unnecessary. Of
course I admit there could be something I'm missing here.
sob., 24 wrz 2022 o 07:13 Xi Ruoyao <xry111@xry111.site> napisał(a):
> On Fri, 2022-09-23 at 23:11 +0200, mizo 91 wrote:
> > > 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.
> >
> > I'm not calling the assembler. Im calling gcc. Check what gcc manual
> > have to say about it.
>
> The problem is it's common to use "gcc -c foo.s" instead of "as foo.s -o
> foo.o" in the building system of the packages. It can ensure the
> assembler used for both C files and assembly files the same one. If you
> suddenly stop to pass -I options to the assembler, you can break the
> building process of existing packages.
> --
> Xi Ruoyao <xry111@xry111.site>
> School of Aerospace Science and Technology, Xidian University
>
next prev parent reply other threads:[~2022-09-24 9:28 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
2022-09-23 21:11 ` mizo 91
2022-09-24 5:13 ` Xi Ruoyao
2022-09-24 9:28 ` mizo 91 [this message]
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=CAGt5VgFTLteAH1QyVn_7r2wHJab57enY3vrUMWU8UFi-D14msA@mail.gmail.com \
--to=mizo91@gmail.com \
--cc=gcc-help@gcc.gnu.org \
--cc=lh_mouse@126.com \
--cc=xry111@xry111.site \
/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).