public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dave at hiauly1 dot hia dot nrc dot ca" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/39978] [4.5 Regression] SEGV compiling libiberty/regex.c in stage2
Date: Fri, 08 May 2009 20:34:00 -0000 [thread overview]
Message-ID: <20090508203428.22289.qmail@sourceware.org> (raw)
In-Reply-To: <bug-39978-276@http.gcc.gnu.org/bugzilla/>
------- Comment #10 from dave at hiauly1 dot hia dot nrc dot ca 2009-05-08 20:34 -------
Subject: Re: [4.5 Regression] SEGV compiling libiberty/regex.c in stage2
> Interesting you don't hit the bug I described in PR 40031.
I tested the following in the regression search:
146971 bad
146908 bad
146900 bad
146894 bad
146893 ok
146892 ok
146876 ok
146845 ok
The bug in PR 40031 was reported at 147121, so maybe things have
changed.
Dave
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39978
next prev parent reply other threads:[~2009-05-08 20:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-30 17:19 [Bug tree-optimization/39978] New: " danglin at gcc dot gnu dot org
2009-04-30 17:55 ` [Bug middle-end/39978] " pinskia at gcc dot gnu dot org
2009-05-01 14:49 ` ramana at gcc dot gnu dot org
2009-05-01 15:30 ` rearnsha at gcc dot gnu dot org
2009-05-01 20:01 ` rguenth at gcc dot gnu dot org
2009-05-01 20:32 ` danglin at gcc dot gnu dot org
2009-05-04 13:48 ` dave at hiauly1 dot hia dot nrc dot ca
2009-05-05 15:52 ` mmitchel at gcc dot gnu dot org
2009-05-06 15:36 ` bonzini at gnu dot org
2009-05-08 18:21 ` danglin at gcc dot gnu dot org
2009-05-08 19:35 ` pinskia at gcc dot gnu dot org
2009-05-08 20:34 ` dave at hiauly1 dot hia dot nrc dot ca [this message]
2009-05-12 13:06 ` danglin 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=20090508203428.22289.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).