public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Michael Ritzert <ritzert@t-online.de> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: optimization/9096: SEGV in find_and_verify_loops Date: Tue, 18 Feb 2003 10:46:00 -0000 [thread overview] Message-ID: <20030218104601.6388.qmail@sources.redhat.com> (raw) The following reply was made to PR optimization/9096; it has been noted by GNATS. From: Michael Ritzert <ritzert@t-online.de> To: ebotcazou@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org Cc: Subject: Re: optimization/9096: SEGV in find_and_verify_loops Date: Tue, 18 Feb 2003 11:41:24 +0100 Am Dienstag, 18. Februar 2003 11:21 schrieb ebotcazou@gcc.gnu.org: > Synopsis: SEGV in find_and_verify_loops [...] > I can't reproduce the SIGSEGV with gcc version 3.4 20030215 > (experimental). Could you try with a more recent snapshot too? I can confirm it does not longer SEGV on both FreeBSD and Linux. Michael
next reply other threads:[~2003-02-18 10:46 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-02-18 10:46 Michael Ritzert [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-02-18 10:52 ebotcazou 2003-02-18 10:21 ebotcazou 2002-12-29 11:46 ritzert
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=20030218104601.6388.qmail@sources.redhat.com \ --to=ritzert@t-online.de \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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: linkBe 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).