This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: gcc link_command_spec question (possible bug?)
- To: Mumit Khan <khan@xraylith.wisc.EDU>
- Subject: Re: gcc link_command_spec question (possible bug?)
- From: Andreas Schwab <schwab@suse.de>
- Date: 17 Aug 1999 10:27:12 +0200
- Cc: gcc@gcc.gnu.org
- References: <199908170607.BAA10705@mercury.xraylith.wisc.edu>
Mumit Khan <khan@xraylith.wisc.EDU> writes:
|> The link_command_spec entry contains the following:
|>
|> static const char *link_command_spec = "\
|> %{!fsyntax-only: \
|> %{!c:%{!M:%{!MM:%{!E:%{!S:%(linker) %l %X %{o*} %{A} %{d} %{e*} %{m} %{N} %{n} \
|> %{r} %{s} %{t} %{u*} %{x} %{z} %{Z}\
|> %{!A:%{!nostdlib:%{!nostartfiles:%S}}}\
|> %{static:} %{L*} %D %o\
|> %{!nostdlib:%{!nodefaultlibs:%G %L %G}}\
|> %{!A:%{!nostdlib:%{!nostartfiles:%E}}}\
|> %{T*}\
|> \n }}}}}}";
|> ^^^
|>
|> Does the \n belong there?
Yes, it is significant. It tells the specs parser to actually start the
command. See gcc.c:do_spec_1, around line 3433 in the current cvs.
--
Andreas Schwab "And now for something
schwab@suse.de completely different."
SuSE GmbH, Schanzäckerstr. 10, D-90443 Nürnberg