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] New: 465.tonto Segmentation Fault in memset
Date: Wed, 22 Dec 2010 00:44:00 -0000 [thread overview]
Message-ID: <bug-47037-4@http.gcc.gnu.org/bugzilla/> (raw)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47037
Summary: 465.tonto Segmentation Fault in memset
Product: gcc
Version: 4.6.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: regression
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: changpeng.fang@amd.com
We have a new system and I saw a segmentation fault in memset (with current gcc
trunk).
gfortran -O2 -static (-march=generic64):
(gdb) r < stdin
Starting program:
/local/home/chfang/cpu2006/benchspec/CPU2006/465.tonto/build/build_base_cfangO3.0000/tonto
< stdin
Program received signal SIGSEGV, Segmentation fault.
memset () at ../sysdeps/x86_64/memset.S:496
496 ../sysdeps/x86_64/memset.S: No such file or directory.
in ../sysdeps/x86_64/memset.S
Current language: auto
The current source language is "auto; currently asm".
(gdb) bt
#0 memset () at ../sysdeps/x86_64/memset.S:496
#1 0x2020202020202020 in ?? ()
#2 0x2020202020202020 in ?? ()
#3 0x2020202020202020 in ?? ()
#4 0x2020202020202020 in ?? ()
#5 0x2020202020202020 in ?? ()
#6 0x2020202020202020 in ?? ()
#7 0x2020202020202020 in ?? ()
#8 0x2020202020202020 in ?? ()
#9 0x2020202020202020 in ?? ()
#10 0x2020202020202020 in ?? ()
#11 0x2020202020202020 in ?? ()
#12 0x2020202020202020 in ?? ()
#13 0x2020202020202020 in ?? ()
#14 0x2020202020202020 in ?? ()
#15 0x2020202020202020 in ?? ()
#16 0x2020202020202020 in ?? ()
#17 0x2020202020202020 in ?? ()
#18 0x0000000000b613a0 in ?? ()
#19 0x2020202020202020 in ?? ()
#20 0x0000000120202020 in ?? ()
#21 0x2020202000000001 in ?? ()
#22 0x2020202020202020 in ?? ()
#23 0x0000000000b60eb0 in ?? ()
#24 0x0000000000b60b20 in ?? ()
#25 0x0000000000000080 in ?? ()
#26 0x0000000000000001 in ?? ()
#27 0x0000000000411d6c in read_label (self=...) at atom.fppized.f90:1155
#28 0x0000000000415318 in process_keyword (self=..., keyword=<value optimized
out>, _keyword=-11776) at atom.fppized.f90:1028
#29 0x0000000000415b74 in process_keys (self=...) at atom.fppized.f90:1440
#30 0x000000000042d689 in data_length (self=<value optimized out>) at
atomvec.fppized.f90:1388
#31 0x000000000042ed3a in read_data (self=..., ignore_braces=Cannot access
memory at address 0x0
) at atomvec.fppized.f90:1351
#32 0x00000000004314f8 in read_list_keywords (self=...) at
atomvec.fppized.f90:1306
#33 0x00000000006256e5 in read_atoms (self=...) at mol.fppized.f90:9579
#34 0x0000000000647d3e in process_keyword (self=0xb5b490, keyword="atom",
_keyword=<value optimized out>) at mol_main.fppized.f90:3836
#35 0x0000000000648418 in read_keywords (self=0xb5b490) at
mol_main.fppized.f90:3807
#36 0x0000000000648489 in main (self=0xb5b490) at mol_main.fppized.f90:3744
#37 0x00000000006b9ea2 in run_mol () at run_mol.fppized.f90:125
#38 main () at run_mol.fppized.f90:22
#39 0x0000000000000000 in ?? ()
next reply other threads:[~2010-12-22 0:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-22 0:44 changpeng.fang at amd dot com [this message]
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
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@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).