public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "changpeng.fang at amd dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug regression/47037] 465.tonto Segmentation Fault in memset with -fcaller-saves (default at -O2 or higher)
Date: Mon, 03 Jan 2011 22:00:00 -0000	[thread overview]
Message-ID: <bug-47037-4-m4aEUKSwyC@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-47037-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47037

--- Comment #6 from Changpeng Fang <changpeng.fang at amd dot com> 2011-01-03 21:59:44 UTC ---
(In reply to comment #5)
> Does your glibc have CPU specific optimizations?

I don't think so. 

The OS is SLES 11, SP1. The machine (bobcat) indeed does not
support some instructions that K8 supports.

gcc (4.3, coming up with the systems) works fine.


  parent reply	other threads:[~2011-01-03 22:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-22  0:44 [Bug regression/47037] New: 465.tonto Segmentation Fault in memset changpeng.fang at amd dot com
2010-12-22  0:55 ` [Bug regression/47037] " changpeng.fang at amd dot com
2010-12-23  9:14 ` tkoenig at gcc dot gnu.org
2010-12-23 18:05 ` [Bug regression/47037] 465.tonto Segmentation Fault in memset with -fcaller-saves (default at -O2 or higher) changpeng.fang at amd dot com
2010-12-23 18:09 ` changpeng.fang at amd dot com
2010-12-28 16:07 ` rguenth at gcc dot gnu.org
2011-01-03 22:00 ` changpeng.fang at amd dot com [this message]
2011-01-03 22:04 ` hjl.tools at gmail dot com
2011-01-03 22:30 ` changpeng.fang at amd dot com
2012-02-02  8:13 ` pinskia at gcc dot gnu.org

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=bug-47037-4-m4aEUKSwyC@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).