public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Eric Botcazou <ebotcazou@adacore.com>
To: Richard Sandiford <rdsandiford@googlemail.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: PR 48826: NOTE_INSN_CALL_ARG_LOCATION vs. define_split
Date: Sun, 29 May 2011 14:31:00 -0000	[thread overview]
Message-ID: <201105291044.14784.ebotcazou@adacore.com> (raw)
In-Reply-To: <87fwnyhh4o.fsf@firetop.home>

> If this usage isn't legitimate, and the CALL_ARG_LOCATION is supposed
> to come directly after the call, then it would be great if someone more
> familiar with the var-tracking code could have a look at it.

"Be liberal in what you accept" says the common wisdom.

> gcc/
> 	* emit-rtl.c (try_split): Use a loop to search for
> 	NOTE_INSN_CALL_ARG_LOCATIONs.
>
> gcc/testsuite/
> 	From Ryan Mansfield
> 	* gcc.dg/pr48826.c: New test.

OK, thanks.

-- 
Eric Botcazou

      reply	other threads:[~2011-05-29  8:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-23  2:07 Richard Sandiford
2011-05-23  9:30 ` Eric Botcazou
2011-05-23 20:16   ` Richard Sandiford
2011-05-23 22:46     ` Eric Botcazou
2011-05-29  1:07     ` Richard Sandiford
2011-05-29 14:31       ` Eric Botcazou [this message]

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=201105291044.14784.ebotcazou@adacore.com \
    --to=ebotcazou@adacore.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=rdsandiford@googlemail.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).