On Tue, Aug 14, 2012 at 04:36:47PM +0200, Emmanuel Kasper wrote:
> Sorry Mame still segfaults with mame -O3 and the latest gcc
> available in debian
I filed the bug upstream:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54569
Berto
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.de
Dear debian user
We will believe the bug you reported is fixed in mame 0.146-2,
availaible in wheezy and sid.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Sorry Mame still segfaults with mame -O3 and the latest gcc available in
debian ( I guess my build env was broken )
The package mame/0.146-2 will fix this bug tough (by recompiling with
-O2 on all arches)
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "
I have recompiled mame with the current wheezy gcc (Debian 4.7.1-6), and
I cannot make mame segfault anymore on i386.
I have seen there has been a slew of bug fixes in the debian gcc
changelog but nothing that I can really pin point to this bug.
As the best way to see if a bug still exist, is
On Wed, Jun 27, 2012 at 03:02:21PM +0200, Emmanuel Kasper wrote:
> @Berto:
> Upstream is however interested in sorting out this bug, so could you
> maybe submit your backtrace as asked in
> http://forums.bannister.org/ubbthreads.php?ubb=showflat&Number=80250
> ?
I registered there buy my account
So i have reproduced the bug, and you're right, using -O2 or compiling
with gcc 4.6 resolves the problem.
As "official" gcc 4.7 support is only coming in mame 0.146 update 2, I
am thinking of using the second option to resolve the bug on the package.
@Berto:
Upstream is however interested in sort
I've been trying to narrow the problem down and I found that
compiling MAME normally with the default options and then recompiling
src/emu/ioport.c with -fno-ipa-cp-clone fixes the issue.
So it's -fipa-cp-clone in ioport.c that is causing the problem.
This looks like a GCC bug to me, and I hope t
On Thu, Jun 21, 2012 at 12:54:28PM +0300, Alberto Garcia wrote:
> > If I have time tomorrow I'll try to compile it with GCC 4.7
>
> I've done it now and I confirm that it crashes. So either GCC 4.7
> is buggy or there's a bug in MAME/MESS that is only reproduced with
> that GCC version.
I'll be
I have here a debian wheezy system in VirtualBox , and I can't reproduce
this bug.
Could try maybe without a mame.ini file ?
Are all your libraries up to date ?
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas..
9 matches
Mail list logo
