public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "spark at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/34171] [4.3 Regression] Segfault in df_chain_remove_problem with -O3 on alpha
Date: Wed, 21 Nov 2007 16:22:00 -0000	[thread overview]
Message-ID: <20071121162207.2904.qmail@sourceware.org> (raw)
In-Reply-To: <bug-34171-12387@http.gcc.gnu.org/bugzilla/>



------- Comment #7 from spark at gcc dot gnu dot org  2007-11-21 16:22 -------
(In reply to comment #6)
> Subject: Re:  [4.3 Regression] Segfault in df_chain_remove_problem
>  with -O3 on alpha
> 
> So it means the basic block has been deleted.
> 
> I want to see what happens if I consolidate all the 
> out_of_date_transfer_functions bitmaps into one.  Seongbae, do you 
> remember experimenting with anything like that?
> 
> Paolo

Not really. 
I agree that it's most likely a bb being deleted though.
I guess somebody will have to trace through using a debugger 
I'll try to build a cross to alpha and see if I can reproduce the problem
today.


-- 

spark at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         AssignedTo|unassigned at gcc dot gnu   |spark at gcc dot gnu dot org
                   |dot org                     |


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


  parent reply	other threads:[~2007-11-21 16:22 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-21  9:18 [Bug rtl-optimization/34171] New: " tbm at cyrius dot com
2007-11-21  9:19 ` [Bug rtl-optimization/34171] " tbm at cyrius dot com
2007-11-21  9:20 ` tbm at cyrius dot com
2007-11-21  9:20 ` tbm at cyrius dot com
2007-11-21  9:47 ` bonzini at gnu dot org
2007-11-21 10:56 ` tbm at cyrius dot com
2007-11-21 12:52 ` paolo dot bonzini at lu dot unisi dot ch
2007-11-21 16:22 ` spark at gcc dot gnu dot org [this message]
2007-11-21 17:47 ` steven at gcc dot gnu dot org
2007-11-21 18:11 ` tbm at cyrius dot com
2007-11-21 20:03 ` steven at gcc dot gnu dot org
2007-11-21 20:23 ` tbm at cyrius dot com
2007-11-21 20:41 ` spark at gcc dot gnu dot org
2007-11-21 22:09 ` spark at gcc dot gnu dot org
2007-11-21 22:30 ` steven at gcc dot gnu dot org
2007-11-21 22:43 ` spark at gcc dot gnu dot org
2007-11-22  0:30 ` spark at gcc dot gnu dot org
2007-11-22  7:06 ` steven at gcc dot gnu dot org
2007-11-25  2:47 ` pinskia at gcc dot gnu dot org
2007-11-27 22:25 ` mmitchel at gcc dot gnu dot org
2007-11-30 17:03 ` spark at gcc dot gnu dot org
2007-11-30 17:07 ` jakub 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=20071121162207.2904.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).