Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 26 Dec 2014 12:15:04 +0200
From:      Konstantin Belousov <kostikbel@gmail.com>
To:        Thomas Zander <riggs@freebsd.org>
Cc:        "freebsd-ports@freebsd.org" <ports@freebsd.org>, multimedia@freebsd.org
Subject:   Re: [CFT] New upstream version of mplayer + mencoder
Message-ID:  <20141226101504.GG1754@kib.kiev.ua>
In-Reply-To: <CAFU734wkwxGPmxigiyA9JhiWQ7adX5_fVzFSCFxVOSaCM1iKOw@mail.gmail.com>
References:  <20141225134226.GA78595@marvin2011.fritz.box> <20141225150940.GF1754@kib.kiev.ua> <CAFU734wkwxGPmxigiyA9JhiWQ7adX5_fVzFSCFxVOSaCM1iKOw@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Dec 25, 2014 at 05:26:24PM +0100, Thomas Zander wrote:
> On 25 December 2014 at 16:09, Konstantin Belousov <kostikbel@gmail.com> wrote:
> > On Thu, Dec 25, 2014 at 02:42:26PM +0100, Thomas Zander wrote:
> >> - Remove -fomit-frame-pointer from CFLAGS (we have apparently a fair
> >>   number of CPUs out there which can't run code compiled with this
> >>   option reliably)
> >
> > Could you, please, explain this ?
> 
> Unfortunately, I don't know yet why this happens. But I can point you
> to the PR where we narrowed the issue down. So far, it seems to affect
> various CPUs in 32 bit mode. If you have additional insights, I'd
> appreciate it. See here:
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=185560

The track in the PR does not contain clean summary, and I have troubles
making the conclusion from the vague info there.

I very much doubt that the problem is a CPU bug, it would be very
high-profile event and would be discovered much earlier then now,
esp. for Pentium IV class machines.

It seems that everything makes circles around stack alignment and SSE.
At least, this is strongly suggested by references to OCFLAGS and the
fact that -fomit-frame-pointer implicitely changes stack alignment.
SIGBUS is somewhat consistent with this observation.

This might be a compiler bug (what compiler ?  I cannot find a conclusive
answer in the PR), or more likely, it is a bug in inline assembler code,
which probably makes unwarranted assumptions about stack alignment.

Reporters must show the disassembly of the failed instruction and register
dump to confirm or deny my theory.  You might want to play with the
-mstackrealign compiler option.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20141226101504.GG1754>