This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Shebang

From: Ian Lance Taylor <ian at wasabisystems dot com>
To: Zack Weinberg <zack at codesourcery dot com>
Cc: Leah <eequor at earthlink dot net>, gcc at gcc dot gnu dot org
Date: 08 Mar 2004 15:51:49 -0500
Subject: Re: Shebang
References: <20040308142442.3d3ea98c.eequor@earthlink.net><87brn7132z.fsf@egil.codesourcery.com>

Zack Weinberg <zack@codesourcery.com> writes:

> > Also, are there reasons gcc won't compile directly from stdin to
> > stdout? 
> 
> GCC will, actually; it's the assembler and linker that won't.  Try: 
> gcc -S -xc - -o - < file.c > file.s.
> 
> You could take this up with the binutils maintainers
> (binutils@sources.redhat.com) but I believe there are good reasons why
> this is infeasible at least for the linker.

It's feasible, for some definition of feasible.  It's merely
inefficient.  You have to either hold the entire output file in
memory, or you have to process each input file several times.

Ian

References:
- Shebang
  - From: Leah
- Re: Shebang
  - From: Zack Weinberg

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]