From: Dave Korn <dave.korn.cygwin@googlemail.com>
To: Justin Mattock <justinmattock@gmail.com>
Cc: Dave Korn <dave.korn.cygwin@googlemail.com>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
gcc@gcc.gnu.org,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
David Rientjes <rientjes@cs.washington.edu>
Subject: Re: cc1plus invoked oom-killer: gfp_mask=0x280da, order=0, oom_adj=0
Date: Thu, 05 Nov 2009 04:53:00 -0000 [thread overview]
Message-ID: <4AF25DCE.3010101@gmail.com> (raw)
In-Reply-To: <dd18b0c30911041936i7876f2d1o7e31059cc44c644f@mail.gmail.com>
Justin Mattock wrote:
> ==1830== Command: c++ -o jsxml.o -c -DOSTYPE="Linux2.6" -DOSARCH=Linux
Ah, you're running it on the "c++" utility and it's reporting the stats for
that, but how it works is that "c++" (and "gcc", "g++", et al) is just a
driver, that parses the command line arguments and shells out to the actual
compiler ("cc1plus"), assembler and linker to get them to do all the work.
If you add "-v --save-temps" to the c++ invocation, it'll show you the
separate command lines it executes for the subprograms; the first invocation
will be of cc1plus, using the -E flag to generate the preprocessed source into
a .ii file, it's the second invocation you want, the one which uses the
"-fpreprocessed" flag and names the .ii file as input, which is the one that
actually then compiles the pre-processed source into assembly. For fuller
explanation, see the GCC wiki:
http://gcc.gnu.org/wiki/DebuggingGCC
cheers,
DaveK
next prev parent reply other threads:[~2009-11-05 4:53 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-02 21:29 Justin Mattock
2009-11-02 21:49 ` Jiri Slaby
2009-11-02 22:02 ` Justin Mattock
2009-11-02 22:05 ` Jiri Slaby
2009-11-02 22:12 ` Justin P. Mattock
2009-11-03 0:56 ` Justin P. Mattock
2009-11-04 1:18 ` KOSAKI Motohiro
2009-11-04 1:40 ` Justin P. Mattock
2009-11-04 6:24 ` Andrew Morton
2009-11-04 6:44 ` Justin P. Mattock
2009-11-04 9:14 ` Jiri Slaby
2009-11-04 9:32 ` KOSAKI Motohiro
2009-11-04 15:29 ` Andrew Morton
2009-11-04 23:20 ` KOSAKI Motohiro
2009-11-04 12:58 ` Dave Korn
2009-11-04 15:08 ` Justin P. Mattock
2009-11-04 15:30 ` Dave Korn
2009-11-04 16:40 ` Justin Mattock
2009-11-04 19:33 ` Dave Korn
2009-11-04 20:39 ` Justin P. Mattock
2009-11-04 21:22 ` Justin Mattock
2009-11-05 0:21 ` Dave Korn
2009-11-05 3:36 ` Justin Mattock
2009-11-05 4:53 ` Dave Korn [this message]
2009-11-06 21:21 ` Justin P. Mattock
2009-11-10 2:55 ` Justin P. Mattock
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=4AF25DCE.3010101@gmail.com \
--to=dave.korn.cygwin@googlemail.com \
--cc=akpm@linux-foundation.org \
--cc=gcc@gcc.gnu.org \
--cc=justinmattock@gmail.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rientjes@cs.washington.edu \
/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).