public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: RE: segv at strcmp
Date: Mon, 05 Jan 2004 22:06:55 +0000	[thread overview]
Message-ID: <16377.57343.186978.712093@napali.hpl.hp.com> (raw)
In-Reply-To: <20040105190848.66033.qmail@web60006.mail.yahoo.com>

>>>>> On Mon, 5 Jan 2004 11:19:36 -0800, "Luck, Tony" <tony.luck@intel.com> said:

  >> Hi - The gcc version is gcc-3.2-29 and the flags we pass to gcc
  >> are : -O -ansi -fwritable-strings -fsigned-char -D_GNU_SOURCE
  >> -D_REENTRANT

  Tony> I have gcc 3.2.3 ... but it appears to not do anything strange
  Tony> to my test program with those options.

  Tony> main() { char *x = "7chars!";

  Tony>         strcmp(x, "This is 24 chars long!!!"); }

  Tony> with those options.  Do you have any include files that might
  Tony> be redefining strcmp as memcmp?

In earlier versions of libc, there were some mem/str-related routines
which were too aggressive in prefetching.  Perhaps Jes remembers the
details, but I'd definitely recommend to make sure you're running the
latest libc for your distro.

	--david

  parent reply	other threads:[~2004-01-05 22:06 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-05 19:08 segv at strcmp umut aymakoglu
2004-01-05 19:19 ` Luck, Tony
2004-01-05 19:52 ` umut aymakoglu
2004-01-05 20:10 ` Luck, Tony
2004-01-05 22:06 ` David Mosberger [this message]
2004-01-06  0:04 ` umut aymakoglu
2004-01-06  1:14 ` Luck, Tony
2004-01-06  1:38 ` umut aymakoglu
2004-01-06  2:01 ` Chen, Kenneth W
2004-01-06 19:58 ` umut aymakoglu
  -- strict thread matches above, loose matches on Subject: below --
2003-12-24 23:13 umut aymakoglu
2003-12-24 23:44 ` Jeff Woods
2003-12-25  0:25 ` Luck, Tony
2003-12-25  1:11 ` Zhu, Yi

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=16377.57343.186978.712093@napali.hpl.hp.com \
    --to=davidm@napali.hpl.hp.com \
    --cc=linux-ia64@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