public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Tokarev <mjt@tls.msk.ru>
To: Linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: VIA C7 / VIA PC-1 (PC2500) anyone?
Date: Tue, 12 Jun 2007 16:19:36 +0400	[thread overview]
Message-ID: <466E8F58.9010502@msgid.tls.msk.ru> (raw)
In-Reply-To: <466E69BE.405@vger.kernel.org>

Linux-kernel wrote:
[]
> To me it looks like a wrong choice of gcc switches to user-mode programs. What
> distribution are you using? try compiling failing programs from source with
> conservative command line switches to gcc. See if things change.

Wrong choice of gcc switches tends to produce binaries wich are either works
or does not.  Here, it sometimes works and sometimes does not.  Also, if
it was wrong options, programs usually tends to fail with something like
SIGILL (Illegal Instruction), not SIGSEGV.

The system is running Debian Etch (4.0), with everything compiled for plain
i386 (default gcc -O2 without any fancy optimizations).

I tried installing libc6-i686 package (cmov-enabled glibc) - unlike with
VIA C3 (which indeed does not have this instruction), it worked on C7, but
installing libc6-i686 didn't change SIGSEGVs at all.

I just tried to recompile man(1) command (the one that gave SIGSEGVs most
often).  The resulting binary fails MUCH less often, but still sometimes
fails.

Note that this is real i686 CPU.  At least according to kernel - when one
chooses C7 CPU in kernel config, kernel uses -march=i686 switch - the only
CPU-specific switch it is.  The difference between i686 and C7 in kernel
config is cache shift value.

Thanks.

/mjt

  reply	other threads:[~2007-06-12 12:19 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-12  9:21 VIA C7 / VIA PC-1 (PC2500) anyone? Michael Tokarev
2007-06-12  9:39 ` Linux-kernel
2007-06-12 12:19   ` Michael Tokarev [this message]
2007-06-12 10:43 ` Alan Cox
2007-06-12 12:04   ` Michael Tokarev
2007-06-12 10:44 ` Wander Winkelhorst
2007-06-12 11:58   ` Michael Tokarev
2007-06-12 12:54     ` Claas Langbehn
2007-06-12 13:01       ` Michael Tokarev
2007-06-12 21:59         ` Jan Engelhardt
2007-06-12 22:08           ` Dave Jones
2007-07-05 20:20 ` Michael Tokarev

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=466E8F58.9010502@msgid.tls.msk.ru \
    --to=mjt@tls.msk.ru \
    --cc=linux-kernel@vger.kernel.org \
    /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