public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rsandifo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/61268] [4.10 regression] ICE in vt_expand_var_loc_chain, at var-tracking.c:8262
Date: Thu, 24 Jul 2014 15:18:00 -0000	[thread overview]
Message-ID: <bug-61268-4-wV3zpd61id@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-61268-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61268

--- Comment #10 from rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> ---
Author: rsandifo
Date: Thu Jul 24 15:17:35 2014
New Revision: 213002

URL: https://gcc.gnu.org/viewcvs?rev=213002&root=gcc&view=rev
Log:
gcc/
    PR middle-end/61268
    * function.c (assign_parm_setup_reg): Prevent invalid sharing of
    DECL_INCOMING_RTL and entry_parm.
    (get_arg_pointer_save_area): Likewise arg_pointer_save_area.
    * calls.c (load_register_parameters): Likewise argument values.
    (emit_library_call_value_1, store_one_arg): Likewise argument
    save areas.
    * config/i386/i386.c (assign_386_stack_local): Likewise the local
    stack slot.
    * explow.c (validize_mem): Modify the argument in-place.

Modified:
    trunk/gcc/ChangeLog
    trunk/gcc/calls.c
    trunk/gcc/config/i386/i386.c
    trunk/gcc/explow.c
    trunk/gcc/function.c


  parent reply	other threads:[~2014-07-24 15:18 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-21 12:17 [Bug middle-end/61268] New: " ro at gcc dot gnu.org
2014-05-21 12:18 ` [Bug middle-end/61268] " ro at gcc dot gnu.org
2014-06-17 13:08 ` ro at gcc dot gnu.org
2014-06-17 13:08 ` ro at gcc dot gnu.org
2014-06-17 14:02 ` ro at gcc dot gnu.org
2014-06-17 14:03 ` ro at gcc dot gnu.org
2014-06-18  8:19 ` rsandifo at gcc dot gnu.org
2014-06-18  8:55 ` ro at CeBiTec dot Uni-Bielefeld.DE
2014-07-17 11:47 ` ro at gcc dot gnu.org
2014-07-17 23:53 ` pthaugen at gcc dot gnu.org
2014-07-24 15:18 ` rsandifo at gcc dot gnu.org [this message]
2014-07-24 15:36 ` rsandifo at gcc dot gnu.org
2014-07-28  8:46 ` rsandifo at gcc dot gnu.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=bug-61268-4-wV3zpd61id@http.gcc.gnu.org/bugzilla/ \
    --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).