Date: Sat, 29 Nov 2008 16:02:03 -0800 From: "Garrett Cooper" <yanefbsd@gmail.com> To: "Giorgos Keramidas" <keramida@ceid.upatras.gr> Cc: freebsd-current@freebsd.org, Peter Wemm <peter@wemm.org> Subject: Re: tty problems in recent head? Message-ID: <7d6fde3d0811291602m3d10dcc6m9c9cbb3f2a8bcd47@mail.gmail.com> In-Reply-To: <878wr2pj5p.fsf@kobe.laptop> References: <87wseo731o.fsf@kobe.laptop> <87fxlcba7p.fsf@kobe.laptop> <87myfjma0k.fsf@kobe.laptop> <e7db6d980811282047o5a7ed4cerc466db6d51e616a4@mail.gmail.com> <87wsempm2k.fsf@kobe.laptop> <878wr2pj5p.fsf@kobe.laptop>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Nov 29, 2008 at 8:54 AM, Giorgos Keramidas
<keramida@ceid.upatras.gr> wrote:
> On Sat, 29 Nov 2008 17:51:31 +0200, Giorgos Keramidas <keramida@ceid.upatras.gr> wrote:
>> On Fri, 28 Nov 2008 20:47:00 -0800, "Peter Wemm" <peter@wemm.org> wrote:
>> without -O2 optimizations, I'll keep going backwards to see if I can
>> locate the commit that this started happening.
>
> Heh, interesting... GENERIC from /head@185376 compiled with a
> `make.conf' that disables optimizations works fine so far:
>
> # CFLAGS?= -O2 -fno-strict-aliasing -pipe
> # COPTFLAGS?= -O -pipe
> NO_CPU_CFLAGS= # Don't add -march=<cpu> to CFLAGS automatically
> NO_CPU_COPTFLAGS= # Don't add -march=<cpu> to COPTFLAGS automatically
Might be another compiler issue. There's an issue with
-fstrict-aliasing (at least) on all versions of g++ up to 4.2.3:
<http://lists.copyleft.no/pipermail/pyrex/2007-November/003071.html>.
Are there some compiler warnings when compiling kernel / screen?
Also, have you tried with just COPTFLAGS disabled?
-Garrett
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7d6fde3d0811291602m3d10dcc6m9c9cbb3f2a8bcd47>