public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ro at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/46114] [4.6 regression] g++ SEGV when built with gld on Solaris 10+/x86
Date: Thu, 21 Oct 2010 20:36:00 -0000 [thread overview]
Message-ID: <20101021203600.FYKbEMvaveBg3B0DYOBZ9uagROabhql780F15gh2Ah8@z> (raw)
In-Reply-To: <bug-46114-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46114
Rainer Orth <ro at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2010.10.21 20:36:21
Ever Confirmed|0 |1
--- Comment #3 from Rainer Orth <ro at gcc dot gnu.org> 2010-10-21 20:36:21 UTC ---
I could reproduce the bug with the attached testcase (go.c with main,
pr46114.c reduced from g++spec.c).
Compile with
% gcc -O2 -o go go.c pr46114.c
After the culprit patch, the program prints
opt_index = 902 arg = 8049253 value = 1 lang_mask = 65536 decoded = 1
opt_index = 902 arg = 8049264 value = 1 lang_mask = 65536 decoded = 804a90c
opt_index = 1019 arg = 0 value = 1 lang_mask = 65536 decoded = 804a938
i.e. decoded (a pointer) is invalid. Before, one gets
opt_index = 902 arg = 8049273 value = 1 lang_mask = 65536 decoded = 804a900
opt_index = 902 arg = 8049284 value = 1 lang_mask = 65536 decoded = 804a92c
opt_index = 1019 arg = 0 value = 1 lang_mask = 65536 decoded = 804a958
The bug is extremely sensitive to the details of the input, so I didn't try
to reduce it further.
Please fix, this is really ugly and makes gcc with gld completely useless.
next prev parent reply other threads:[~2010-10-21 20:36 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-21 12:03 [Bug rtl-optimization/46114] New: " ro at gcc dot gnu.org
2010-10-21 20:32 ` [Bug rtl-optimization/46114] " ro at gcc dot gnu.org
2010-10-21 20:33 ` ro at gcc dot gnu.org
2010-10-21 20:36 ` ro at gcc dot gnu.org [this message]
2010-10-21 20:41 ` hjl.tools at gmail dot com
2010-10-21 20:58 ` ro at CeBiTec dot Uni-Bielefeld.DE
2010-10-21 23:34 ` bernds at gcc dot gnu.org
2010-10-22 10:09 ` ro at gcc dot gnu.org
2010-10-22 10:10 ` ro at gcc dot gnu.org
2010-10-22 10:15 ` ro at CeBiTec dot Uni-Bielefeld.DE
2010-10-22 13:25 ` bernds at gcc dot gnu.org
2010-10-22 13:35 ` ro at CeBiTec dot Uni-Bielefeld.DE
2010-11-03 15:38 ` rguenth at gcc dot gnu.org
2010-11-03 17:10 ` hjl.tools at gmail dot com
2010-11-04 18:48 ` ro at CeBiTec dot Uni-Bielefeld.DE
2010-11-08 7:31 ` steven at gcc dot gnu.org
2010-11-25 16:08 ` bernds at gcc dot gnu.org
2010-11-25 16:51 ` ro at CeBiTec dot Uni-Bielefeld.DE
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=20101021203600.FYKbEMvaveBg3B0DYOBZ9uagROabhql780F15gh2Ah8@z \
--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).