public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/29558] ICE in set_variable_part, at var-tracking.c:2140
Date: Mon, 23 Oct 2006 11:29:00 -0000	[thread overview]
Message-ID: <20061023112920.3392.qmail@sourceware.org> (raw)
In-Reply-To: <bug-29558-10053@http.gcc.gnu.org/bugzilla/>



------- Comment #2 from rguenth at gcc dot gnu dot org  2006-10-23 11:29 -------
Fails on the 4.2.0 branch.  On the 4.1 branch it might be due to packports of

2006-05-23  Alexandre Oliva  <aoliva@redhat.com>

        * simplify-rtx.c (simplify_subreg): Adjust REG_OFFSET for
        big-endian paradoxical subregs.
        * var-tracking.c (struct micro_operation_def): Document that,
        for modify micro operations, insn is the subsequent instruction.
        (var_reg_delete_and_set, var_mem_delete_and_set): Split into...
        (var_reg_set, var_mem_set): ... new functions.
        (add_stores): Record subsequent insn.
        (compute_bb_dataflow): Use new functions for MO_USE.
        (emit_notes_in_bb): Use new functions for MO_USE.  Emit use
        notes after the insn, and modify notes before the insn known
        to be the subsequent one.
        (vt_initialize): Invert sorting of MO_CLOBBERs and MO_SETs.

from  Alexandre Oliva  <aoliva@redhat.com>

        * var-tracking.c (enum micro_operation_type): Add MO_COPY.
        (var_debug_decl): New function.
        (var_reg_set): Follow debug decl link.  Add location even if
        reg is already known to hold some other variable.
        (var_mem_set): Follow debug decl link.
        (var_reg_delete_and_set, var_mem_delete_and_set): Follow debug
        decl link.  Delete other known locations of the variable part
        if requested.
        (var_reg_delete, var_mem_delete): Delete other known locations
        of the variable part if requested.
        (same_variable_part_p): New function.
        (add_stores): Select MO_COPY when appropriate.
        (vt_initialize): Handle it.
        (compute_bb_dataflow, emit_notes_in_bb): Likewise.  Delete
        known locations for MO_SET and MO_CLOBBER.
        (find_variable_location_part): New function.
        (set_variable_part, delete_variable_part): Use it.
        (clobber_variable_part): New function.
        * dwarf2out.c (dwarf2out_var_location): Do not follow debug
        decl link.

2006-09-11  Alexandre Oliva  <aoliva@redhat.com>

        PR target/28672
        * var-tracking.c (dump_dataflow_set): Start dumping at
        register zero.
        (clobber_variable_part): Kill only the variable part in
        registers holding it, leaving other variables alone.


-- 

rguenth at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |aoliva at gcc dot gnu dot
                   |                            |org
      Known to fail|                            |4.2.0


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


  parent reply	other threads:[~2006-10-23 11:29 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-23  9:07 [Bug target/29558] New: " rguenth at gcc dot gnu dot org
2006-10-23 10:14 ` [Bug target/29558] " rguenth at gcc dot gnu dot org
2006-10-23 11:29 ` rguenth at gcc dot gnu dot org [this message]
2006-10-23 15:48 ` [Bug middle-end/29558] [4.2 Regression] " pinskia at gcc dot gnu dot org
2006-10-23 16:06 ` [Bug debug/29558] " pinskia at gcc dot gnu dot org
2006-11-07 19:18 ` [Bug debug/29558] [4.2/4.3 " janis at gcc dot gnu dot org
2007-01-19 22:30 ` bergner at gcc dot gnu dot org
2007-01-19 22:32 ` bergner at gcc dot gnu dot org
2007-02-15 17:51 ` rth at gcc dot gnu dot org
2007-02-19 16:11 ` rth at gcc dot gnu dot org
2007-02-19 16:22 ` rth at gcc dot gnu dot org
2007-02-19 20:35 ` mmitchel at gcc dot gnu dot org
2007-02-19 23:45 ` rth 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=20061023112920.3392.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).