public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dnovillo at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/15855] [3.4/4.0/4.1 Regression] g++ crash with -O2 and -O3 on input file
Date: Mon, 17 Oct 2005 17:32:00 -0000	[thread overview]
Message-ID: <20051017173219.28757.qmail@sourceware.org> (raw)
In-Reply-To: <bug-15855-8424@http.gcc.gnu.org/bugzilla/>



------- Comment #52 from dnovillo at gcc dot gnu dot org  2005-10-17 17:32 -------

Mark, there's probably not much else we can do in this PR for 4.1.  What I see
in the aliasing times involves quite a few changes, most of them from the
aliasing branch and some other similarly intrusive changes I've got on the
side.

Other than that, the timings are now relatively reasonable.  How do you want to
handle this?


-- 

dnovillo at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mmitchel at gcc dot gnu dot
                   |                            |org


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


  parent reply	other threads:[~2005-10-17 17:32 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-15855-8424@http.gcc.gnu.org/bugzilla/>
2005-10-07 10:54 ` cvs-commit at gcc dot gnu dot org
2005-10-07 11:17 ` rguenth at gcc dot gnu dot org
2005-10-17 16:34 ` dnovillo at gcc dot gnu dot org
2005-10-17 16:46 ` law at redhat dot com
2005-10-17 17:32 ` dnovillo at gcc dot gnu dot org [this message]
2005-10-17 20:30 ` mark at codesourcery dot com
2005-10-18 15:33 ` dnovillo at gcc dot gnu dot org
2004-06-06 19:10 [Bug c++/15855] New: " abegel at cs dot berkeley dot edu
2005-05-19 17:23 ` [Bug middle-end/15855] [3.4/4.0/4.1 Regression] " mmitchel at gcc dot gnu dot org
2005-07-22 21:16 ` pinskia at gcc dot gnu dot org
2005-07-24  1:00 ` pinskia at gcc dot gnu dot org
2005-08-12  6:21 ` phython at gcc dot gnu dot org
2005-08-12 19:08 ` wilson at specifix dot com
2005-09-12 10:53 ` rguenth at gcc dot gnu dot org
2005-09-15 22:06 ` rguenth at gcc dot gnu dot org
2005-09-16  8:14 ` rguenth at gcc dot gnu dot org
2005-09-26  8:39 ` cvs-commit at gcc dot gnu dot org
2005-09-26  8:43 ` cvs-commit at gcc dot gnu dot org
2005-09-27 15:59 ` mmitchel 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=20051017173219.28757.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).