linux-um archives
 help / color / mirror / Atom feed
From: Michael Roth <mroth@nessie.de>
To: roland <for_spam@gmx.de>
Cc: uml <uml@dot1q.net>,
	user-mode-linux-user@lists.sourceforge.net,
	user-mode-linux-devel@lists.sourceforge.net,
	Jeff Dike <jdike@addtoit.com>
Subject: [uml-devel] Re: [uml-user] mem=64M, mem=128M, mem=ANYTHING ignored??
Date: Sat, 22 May 2004 21:15:44 +0200	[thread overview]
Message-ID: <40AFA6E0.1040902@nessie.de> (raw)
In-Reply-To: <046001c43ffc$e9b52d90$2000000a@schlepptopp>

roland wrote:
> success, too.
> 
> the error definitely seems  to be a compile issue.
> if i compile with -O2, uml just uses the 32M memory default
> if i compile with -O1, uml uses the param "mem=..." the right way

I'm not sure and I'm to lazy to check this out, but IIRC I had the same 
problems using gcc-3.4.0.

> mhhh - don`t know how much "improvement" does "O2" in favour of "O1" - but
> who should we ask now, to help hunting this "bug" ?
> gcc folks ?

Maybe the gcc manual? RTFM? ;-)

http://gcc.gnu.org/onlinedocs/gcc-3.3.3/gcc/Optimize-Options.html

O1 Options:

-fdefer-pop  -fmerge-constants  -fthread-jumps  -floop-optimize 
-fcrossjumping  -fif-conversion  -fif-conversion2  -fdelayed-branch 
-fguess-branch-probability  -fcprop-registers

O2 Options (O1 options plus the following):

-fforce-mem  -foptimize-sibling-calls  -fstrength-reduce 
-fcse-follow-jumps  -fcse-skip-blocks  -frerun-cse-after-loop 
-frerun-loop-opt -fgcse  -fgcse-lm  -fgcse-sm 
-fdelete-null-pointer-checks  -fexpensive-optimizations  -fregmov 
-fschedule-insns  -fschedule-insns2  -fsched-interblock  -fsched-spec 
-fcaller-saves  -fpeephole2  -freorder-blocks  -freorder-functions 
-fstrict-aliasing  -falign-functions  -falign-jumps  -falign-loops 
-falign-labels

Note: First, gcc-3.4.0 is slighlty different. Second, if the problem 
states only with gcc-3.x (x>=1) and not with gcc-3.0.0 or gcc-2.x, then 
maybe the bug in uml is triggered by the opcode scheduler in the newer 
gcc. IIRC correctly, the scheduler changed somewhere in the gcc-3.x 
line. But as always, I'm not sure. ;-)


Michael Roth




-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g. 
Take an Oracle 10g class now, and we'll give you the exam FREE.
http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

      reply	other threads:[~2004-05-22 19:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200405210556.i4L5uIX19375@lifewood.com>
     [not found] ` <004101c43f3b$497c26b0$dd02a8c0@ferraro>
     [not found]   ` <20040521174707.GA7508@ccure.user-mode-linux.org>
     [not found]     ` <005001c43f79$bcfce6e0$dd02a8c0@ferraro>
2004-05-22 13:01       ` [uml-devel] Re: [uml-user] mem=64M, mem=128M, mem=ANYTHING ignored?? roland
2004-05-22 19:15         ` Michael Roth [this message]

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=40AFA6E0.1040902@nessie.de \
    --to=mroth@nessie.de \
    --cc=for_spam@gmx.de \
    --cc=jdike@addtoit.com \
    --cc=uml@dot1q.net \
    --cc=user-mode-linux-devel@lists.sourceforge.net \
    --cc=user-mode-linux-user@lists.sourceforge.net \
    /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