public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at physics dot uc dot edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/26991] Target Help Seg Fault.
Date: Mon, 26 Jun 2006 16:47:00 -0000 [thread overview]
Message-ID: <20060626164655.24777.qmail@sourceware.org> (raw)
In-Reply-To: <bug-26991-12460@http.gcc.gnu.org/bugzilla/>
------- Comment #4 from pinskia at physics dot uc dot edu 2006-06-26 16:46 -------
Subject: Re: Target Help Seg Fault.
On Jun 26, 2006, at 9:41 AM, corsepiu at gcc dot gnu dot org wrote:
>
>
> ------- Comment #3 from corsepiu at gcc dot gnu dot org 2006-06-26
> 16:41 -------
> Traceback:
>
> => the SEGFAULT occurs in memset.
>
> Could it be, "static char* printed" should be initialized = 0?
Looks like reload is storing to cl_options_count :). There was a 4.2
bug
about this, somehow it got exposed for 4.1.x now.
-- Pinski
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26991
next prev parent reply other threads:[~2006-06-26 16:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-02 17:22 [Bug c++/26991] New: " dave dot m at email dot it
2006-04-02 17:33 ` [Bug middle-end/26991] " pinskia at gcc dot gnu dot org
2006-04-03 17:43 ` pinskia at gcc dot gnu dot org
2006-06-26 15:03 ` corsepiu at gcc dot gnu dot org
2006-06-26 16:46 ` corsepiu at gcc dot gnu dot org
2006-06-26 16:47 ` Andrew Pinski
2006-06-26 16:47 ` pinskia at physics dot uc dot edu [this message]
2006-06-26 16:49 ` [Bug middle-end/26991] [4.1 Regression] " pinskia at gcc dot gnu dot org
2006-06-26 17:01 ` pinskia at gcc dot gnu dot org
2006-06-26 17:06 ` corsepiu at gcc dot gnu dot org
2006-06-26 17:22 ` pinskia at gcc dot gnu dot org
2006-06-29 10:06 ` jakub at gcc dot gnu dot org
2006-06-29 10:49 ` jakub at gcc dot gnu dot org
2006-07-04 13:48 ` jakub at gcc dot gnu dot org
2006-07-04 14:38 ` pinskia at gcc dot gnu dot 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=20060626164655.24777.qmail@sourceware.org \
--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).