Kai Tietz wrote:
2011/10/24 Bob Breuer breu...@mc.net:
Kai Tietz wrote:
Hi,
For trunk-version I have a tentative patch for this issue. On 4.6.x
and older branches this doesn't work, as here we can't differenciate
that easy between ms- and sysv-abi.
But could somebody give this patch a
Kai Tietz wrote:
Hi,
For trunk-version I have a tentative patch for this issue. On 4.6.x
and older branches this doesn't work, as here we can't differenciate
that easy between ms- and sysv-abi.
But could somebody give this patch a try?
Regards,
Kai
ChangeLog
*
2011/10/24 Bob Breuer breu...@mc.net:
Kai Tietz wrote:
Hi,
For trunk-version I have a tentative patch for this issue. On 4.6.x
and older branches this doesn't work, as here we can't differenciate
that easy between ms- and sysv-abi.
But could somebody give this patch a try?
Regards,
Kai
2011/10/22 xunxun xunxun1...@gmail.com:
于 2011/10/22 13:13, xunxun 写道:
Hi, all
It seems that gcc's auto-omit-frame-pointer has other problems.
The example is from mingw bug tracker:
http://sourceforge.net/tracker/?func=detailaid=3426555group_id=2435atid=102435
g++ -O3 main.cpp
On 2011-10-20 23:34, Kai Tietz wrote:
Hi,
For trunk-version I have a tentative patch for this issue. On 4.6.x
and older branches this doesn't work, as here we can't differenciate
that easy between ms- and sysv-abi.
But could somebody give this patch a try?
Regards,
Kai
ChangeLog
Hi, all
It seems that gcc's auto-omit-frame-pointer has other problems.
The example is from mingw bug tracker:
http://sourceforge.net/tracker/?func=detailaid=3426555group_id=2435atid=102435
g++ -O3 main.cpp running will crash.
g++ -O2 main.cpp running no crash.
于 2011/10/22 13:13, xunxun 写道:
Hi, all
It seems that gcc's auto-omit-frame-pointer has other problems.
The example is from mingw bug tracker:
http://sourceforge.net/tracker/?func=detailaid=3426555group_id=2435atid=102435
g++ -O3 main.cpp running will crash.
g++ -O2
On 2011-10-20 AM 6:05, Bob Breuer wrote:
We probably have a difference in build or run environment. I've
double-checked with another machine and can get the same crash in
longjmp when running the test executable on both WinXP and Win2k, but
not on Win7. So it looks like Microsoft may have
2011/10/20 xunxun xunxun1...@gmail.com:
Hi, all
I think this issue causes the gdb crash on XP.
You can see the thread: http://sourceware.org/ml/gdb/2011-10/msg00056.html
My many friends and I can reproduce this crash issue, but no problem on Win7.
On Thu, Oct 20, 2011 at 5:05 AM, Bob
Hi,
For trunk-version I have a tentative patch for this issue. On 4.6.x
and older branches this doesn't work, as here we can't differenciate
that easy between ms- and sysv-abi.
But could somebody give this patch a try?
Regards,
Kai
ChangeLog
* config/i386/i386.c
Kai Tietz wrote:
2011/10/18 Bob Breuer breu...@mc.net:
Kai Tietz wrote:
2011/10/17 Bob Breuer breu...@mc.net:
Richard Henderson wrote:
On 10/17/2011 07:09 AM, Bob Breuer wrote:
Google finds a mention of longjmp failing with -fomit-frame-pointer:
On 10/19/2011 02:05 PM, Bob Breuer wrote:
Is it possible to force a
stackframe by just adding a suitable attribute to either the setjmp
function prototype, or the function which calls setjmp?
The only thing I can think of that'll be portable to a large number
of versions of GCC is
{
int
Hi, all
I think this issue causes the gdb crash on XP.
You can see the thread: http://sourceware.org/ml/gdb/2011-10/msg00056.html
My many friends and I can reproduce this crash issue, but no problem on Win7.
On Thu, Oct 20, 2011 at 5:05 AM, Bob Breuer breu...@mc.net wrote:
Kai Tietz wrote:
On 10/17/2011 07:09 AM, Bob Breuer wrote:
I don't think this is a free/g_free issue. If I use the following
patch, then I at least get the openbios messages:
diff --git a/cpu-exec.c b/cpu-exec.c
index a9fa608..dfbd6ea 100644
--- a/cpu-exec.c
+++ b/cpu-exec.c
@@ -180,6 +180,7 @@ static
On Mon, Oct 17, 2011 at 5:22 PM, Richard Henderson r...@twiddle.net wrote:
On 10/17/2011 07:09 AM, Bob Breuer wrote:
I don't think this is a free/g_free issue. If I use the following
patch, then I at least get the openbios messages:
diff --git a/cpu-exec.c b/cpu-exec.c
index
On 10/17/2011 12:14 PM, Blue Swirl wrote:
IIRC buggy versions of alloca() could also fail without a frame pointer.
(1) GCC always uses a frame pointer for alloca,
(2) Unless you do -fno-builtin-alloca, we always implement it inline.
r~
Richard Henderson wrote:
On 10/17/2011 07:09 AM, Bob Breuer wrote:
I don't think this is a free/g_free issue. If I use the following
patch, then I at least get the openbios messages:
diff --git a/cpu-exec.c b/cpu-exec.c
index a9fa608..dfbd6ea 100644
--- a/cpu-exec.c
+++ b/cpu-exec.c
@@
2011/10/17 Bob Breuer breu...@mc.net:
Richard Henderson wrote:
On 10/17/2011 07:09 AM, Bob Breuer wrote:
I don't think this is a free/g_free issue. If I use the following
patch, then I at least get the openbios messages:
diff --git a/cpu-exec.c b/cpu-exec.c
index a9fa608..dfbd6ea 100644
Kai Tietz wrote:
2011/10/17 Bob Breuer breu...@mc.net:
Richard Henderson wrote:
On 10/17/2011 07:09 AM, Bob Breuer wrote:
I don't think this is a free/g_free issue. If I use the following
patch, then I at least get the openbios messages:
diff --git a/cpu-exec.c b/cpu-exec.c
index
2011/10/18 Bob Breuer breu...@mc.net:
Kai Tietz wrote:
2011/10/17 Bob Breuer breu...@mc.net:
Richard Henderson wrote:
On 10/17/2011 07:09 AM, Bob Breuer wrote:
I don't think this is a free/g_free issue. If I use the following
patch, then I at least get the openbios messages:
diff --git
I'm building QEMU mipsel-linux-user with Ubuntu's GCC 4.4 on an x86
host. Whenever I try to run a trivial MIPS executable, QEMU segfaults
in cpu_loop() shortly after the call to cpu_mips_exec().
The problem seems to be that cpu_exec() doesn't preserve ebp. It tries to:
saved_env_reg =
On 23 February 2010 17:03, Aurelien Jarno aurel...@aurel32.net wrote:
Jay Foad a écrit :
I'm building QEMU mipsel-linux-user with Ubuntu's GCC 4.4 on an x86
host. Whenever I try to run a trivial MIPS executable, QEMU segfaults
in cpu_loop() shortly after the call to cpu_mips_exec().
The
On Tuesday 04 December 2007 06:35:53 pm Carlo Marcelo Arenas Belon wrote:
On Mon, Dec 03, 2007 at 08:20:28PM -0600, Rick Vernam wrote:
any comments on the current status of moving beyond dependency on GCC
3.3.6?
you meant dependency on GCC 4 right?
yeah..thanks.
I use gcc 3.4.6 and there
any comments on the current status of moving beyond dependency on GCC 3.3.6?
no need to go into details of 'why' on my behalf, so spare yourself the time
on that... :-)
thanks
Hello.
I have (GCC) 4.2.1,
when i'm tried to build qemu from cvs, i've got such error:
Code:
make -C i386-softmmu all
make[1]: Entering directory `/mnt/work/install/compil/qemu/qemu/i386-softmmu'
gcc -Wall -O2 -g -fno-strict-aliasing -fno-reorder-blocks -fno-gcse
-fno-tree-ch
Its known bug of gcc4. you should compile on gcc 3.
Please check the following qemu FAQ.
http://calamari.reverse-dns.net:980/cgi-bin/moin.cgi/FrequentlyAskedQuestions#head-1dd86241b11d36963df140c9f6ab46ef402d4244
Thanks
Atsushi SAKAI
Alexander [EMAIL PROTECTED] wrote:
Hello.
I have (GCC)
26 matches
Mail list logo