public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "janis at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/25682] [4.0/4.1/4.2 Regression] ICE when using old sytle offsetof (with non zero start) as array size
Date: Mon, 16 Jan 2006 19:28:00 -0000	[thread overview]
Message-ID: <20060116192826.4804.qmail@sourceware.org> (raw)
In-Reply-To: <bug-25682-3368@http.gcc.gnu.org/bugzilla/>



------- Comment #5 from janis at gcc dot gnu dot org  2006-01-16 19:28 -------
A regression hunt on powerpc-linux using the submitter's testcase identified
the following patch as introducing the failure:

http://gcc.gnu.org/viewcvs?view=rev&rev=87064

r87064 | rth | 2004-09-03 23:50:11 +0000 (Fri, 03 Sep 2004) | 16 lines

        PR middle-end/9997
        * cfgexpand.c (LOCAL_ALIGNMENT): Provide default.
        (STACK_ALIGNMENT_NEEDED, FRAME_GROWS_DOWNWARD): Likewise.
        (struct stack_var, EOC, stack_vars, stack_vars_alloc, stack_vars_num,
        stack_vars_sorted, stack_vars_conflict, stack_vars_conflict_alloc,
        frame_phase, get_decl_align_unit, add_stack_var, triangular_index,
        resize_stack_vars_conflict, add_stack_var_conflict,
        stack_var_conflict_p, add_alias_set_conflicts, stack_var_size_cmp,
        union_stack_vars, partition_stack_vars, dump_stack_var_partition,
        expand_one_stack_var_at, expand_stack_vars, expand_one_stack_var,
        expand_one_static_var, expand_one_hard_reg_var,
        expand_one_register_var, expand_one_error_var, defer_stack_allocation,
        expand_one_var, expand_used_vars_for_block, clear_tree_used): New.
        (expand_used_vars): Rewrite.
        * Makefile.in (cfgexpand.o): Update dependencies.


-- 

janis at gcc dot gnu dot org changed:

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


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


  parent reply	other threads:[~2006-01-16 19:28 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-05 21:39 [Bug c/25682] New: ICE when using (int)(&((S*)0)->field) " gcc-bugzilla at gcc dot gnu dot org
2006-01-05 22:36 ` [Bug c/25682] [4.0/4.1/4.2 Regression] " steven at gcc dot gnu dot org
2006-01-05 22:42 ` pinskia at gcc dot gnu dot org
2006-01-07 16:01 ` [Bug c/25682] [4.0/4.1/4.2 Regression] ICE when using old sytle offsetof (with non zero start) " pinskia at gcc dot gnu dot org
2006-01-14  6:04 ` pinskia at gcc dot gnu dot org
2006-01-15 22:27 ` mmitchel at gcc dot gnu dot org
2006-01-16 12:46 ` jakub at gcc dot gnu dot org
2006-01-16 19:28 ` janis at gcc dot gnu dot org [this message]
2006-01-17  9:58 ` jakub at gcc dot gnu dot org
2006-01-17 10:00 ` jakub at gcc dot gnu dot org
2006-02-27 20:25 ` [Bug c/25682] [4.0 " mmitchel at gcc dot gnu dot org
2006-02-28 11:38 ` jakub at gcc dot gnu dot org
2006-02-28 12:45 ` pinskia 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=20060116192826.4804.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).