public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Joern Wolfgang Rennecke <gnu@amylaar.uk>
To: Claudiu Zissulescu <Claudiu.Zissulescu@synopsys.com>,
	 gcc-patches@gcc.gnu.org
Cc: Francois.Bedard@synopsys.com, jeremy.bennett@embecosm.com
Subject: Re: [PATCH][ARC] Refurbish emitting DWARF2 for epilogue.
Date: Thu, 03 Dec 2015 21:59:00 -0000	[thread overview]
Message-ID: <5660BB51.6000304@amylaar.uk> (raw)
In-Reply-To: <1448632380-7353-1-git-send-email-claziss@synopsys.com>


On 27/11/15 13:53, Claudiu Zissulescu wrote:
>    
> @@ -2502,11 +2540,18 @@ arc_expand_epilogue (int sibcall_p)
>     /* Restore any saved registers.  */
>     if (frame_pointer_needed)
>       {
> -	  rtx addr = gen_rtx_POST_INC (Pmode, stack_pointer_rtx);
> +      insn = emit_insn (gen_blockage ());

Is this actually part of the patch to fix cfi generation?
It looks to me like it is working around an alias.c issue - namely, that 
alias.c does
not consider stack and frame pointer based addresses to alias.
https://gcc.gnu.org/ml/gcc/2011-07/msg00461.html
https://github.com/adapteva/epiphany-gcc/commit/6d1194a563e05dfa826ab4635514477af1f7a2b0

  reply	other threads:[~2015-12-03 21:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-27 14:02 Claudiu Zissulescu
2015-12-03 21:59 ` Joern Wolfgang Rennecke [this message]
2015-12-07  9:19   ` Claudiu Zissulescu
2015-12-09  4:44     ` Joern Wolfgang Rennecke
2015-12-09  4:52       ` Joern Wolfgang Rennecke
2015-12-09 15:34       ` Claudiu Zissulescu
2015-12-09 18:48         ` Joern Wolfgang Rennecke
2015-12-10 14:47           ` Claudiu Zissulescu
2015-12-11 10:29           ` Claudiu Zissulescu
2015-12-12 14:49             ` Joern Wolfgang Rennecke
2015-12-14 10:07               ` Claudiu Zissulescu

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=5660BB51.6000304@amylaar.uk \
    --to=gnu@amylaar.uk \
    --cc=Claudiu.Zissulescu@synopsys.com \
    --cc=Francois.Bedard@synopsys.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jeremy.bennett@embecosm.com \
    /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).