public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mister.freeman at laposte dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/55808] excessive memory usage from gcc 4.7.2 when compiling mame source code
Date: Tue, 01 Jan 2013 04:41:00 -0000	[thread overview]
Message-ID: <bug-55808-4-f1UQe2I3GI@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55808-4@http.gcc.gnu.org/bugzilla/>


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55808

--- Comment #5 from Patrick <mister.freeman at laposte dot net> 2013-01-01 04:41:07 UTC ---
here are the options :

gcc -DCRLF=2 -DINLINE=static inline -DLSB_FIRST -DNDEBUG -DFLAC__NO_DLL
-DSDLMAME_SDL2=0 -D_LFS64_LARGEFILE=0 -DDISTRO=generic -DSDLMAME_ARCH=
-DSYNC_IMPLEMENTATION=tc -DSDLMAME_UNIX -DUSE_OPENGL=1
-DUSE_DISPATCH_GL=1 -DSDLMAME_X11 -DUSE_XINPUT=0 -DNATIVE_DRC=drcbe_x86
-save-temps -pipe -O3 -Werror -fno-strict-aliasing -Wall -Wcast-align
-Wundef -Wformat-security -Wwrite-strings -Wno-sign-compare
-Wno-conversion -Wno-narrowing -Wno-attributes -D_GNU_SOURCE=1
-D_REENTRANT -pthread -pthread

I will post later the  preprocessed files (*.i*) that trigger the bug

Le 01/01/2013 05:04, pinskia at gcc dot gnu.org a écrit :

> 
> I mean which are used to invoke gcc.  I am not going out of my way to create a
> vm and try to compile mame, you already have it compiling already.
> 
> Please read http://gcc.gnu.org/bugs.html and provide all the needed information
> listed on that page.
>


  parent reply	other threads:[~2013-01-01  4:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-26  1:36 [Bug c/55808] New: " mister.freeman at laposte dot net
2012-12-31 10:28 ` [Bug c/55808] " pinskia at gcc dot gnu.org
2012-12-31 10:31 ` [Bug middle-end/55808] " pinskia at gcc dot gnu.org
2012-12-31 15:06 ` mister.freeman at laposte dot net
2012-12-31 21:11 ` pinskia at gcc dot gnu.org
2013-01-01  4:41 ` mister.freeman at laposte dot net [this message]
2013-01-01 16:24 ` mister.freeman at laposte dot net

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=bug-55808-4-f1UQe2I3GI@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /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).