public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pluto at agmk dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/32218] [4.2/4.3 Regression] segfault with -O1 -ftree-vectorize
Date: Thu, 26 Jul 2007 16:38:00 -0000	[thread overview]
Message-ID: <20070726163754.28290.qmail@sourceware.org> (raw)
In-Reply-To: <bug-32218-12387@http.gcc.gnu.org/bugzilla/>



------- Comment #10 from pluto at agmk dot net  2007-07-26 16:37 -------
(In reply to comment #9)
> The fix for this was approved and checked into mainline.

resolved/fixed? what about 4.2 branch? it's a regression.


-- 

pluto at agmk dot net changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |pluto at agmk dot net


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32218


  parent reply	other threads:[~2007-07-26 16:38 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-05  8:31 [Bug tree-optimization/32218] New: " tbm at cyrius dot com
2007-06-06 23:44 ` [Bug target/32218] " sje at cup dot hp dot com
2007-06-30  9:15 ` pinskia at gcc dot gnu dot org
2007-07-01 11:23 ` dorit at gcc dot gnu dot org
2007-07-01 11:32 ` tbm at cyrius dot com
2007-07-01 11:33 ` tbm at cyrius dot com
2007-07-03 20:19 ` sje at cup dot hp dot com
2007-07-04  3:24 ` mmitchel at gcc dot gnu dot org
2007-07-20  3:52 ` mmitchel at gcc dot gnu dot org
2007-07-24  8:53 ` dorit at gcc dot gnu dot org
2007-07-24 18:37 ` tbm at cyrius dot com
2007-07-25 16:20 ` sje at cup dot hp dot com
2007-07-25 20:24 ` sje at gcc dot gnu dot org
2007-07-26 16:30 ` sje at cup dot hp dot com
2007-07-26 16:38 ` pluto at agmk dot net [this message]
2007-07-26 16:44 ` sje at cup dot hp dot com
2007-07-30 15:16 ` sje 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=20070726163754.28290.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).