From: Alexandre Oliva <aoliva@redhat.com>
To: Bernd Schmidt <bernds@codesourcery.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: don't force debug insns after their PREV_INSNs
Date: Wed, 13 Jun 2012 08:08:00 -0000 [thread overview]
Message-ID: <oripev63gd.fsf@livre.localdomain> (raw)
In-Reply-To: <orbon1e6v2.fsf@livre.localdomain> (Alexandre Oliva's message of "Mon, 09 Apr 2012 03:50:41 -0300")
On Apr 9, 2012, Alexandre Oliva <aoliva@redhat.com> wrote:
> The problem here is that a nondebug insn may be moved ahead of a useful
> debug insn and clobber one of its inputs, rendering it useless, when
> there's no good reason for the debug insn to be kept in place, other
> than an accidental dependency on the previous insn when it happens to be
> unrelated with the debug insn.
> Removing the extraneous dependency, that was thought to be a way to
> reduce movement of debug insns, improves on this problem. It's not
> clear that this artificial dependency really does any good, since odds
> are that that previous insn may be pulled ahead anyway, in which case so
> will debug insn (unless that would fail other of its deps, of course)
> Retested. Ok?
> for gcc/ChangeLog
> from Alexandre Oliva <aoliva@redhat.com>
> * sched-deps.c (sched_analyze_insn): Don't force debug insns
> to follow their original predecessors.
Ping? http://gcc.gnu.org/ml/gcc-patches/2012-04/msg00418.html
--
Alexandre Oliva, freedom fighter http://FSFLA.org/~lxoliva/
You must be the change you wish to see in the world. -- Gandhi
Be Free! -- http://FSFLA.org/ FSF Latin America board member
Free Software Evangelist Red Hat Brazil Compiler Engineer
prev parent reply other threads:[~2012-06-13 8:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-03 14:51 Alexandre Oliva
2011-06-03 18:29 ` Bernd Schmidt
2012-04-09 6:51 ` Alexandre Oliva
2012-06-13 8:08 ` Alexandre Oliva [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=oripev63gd.fsf@livre.localdomain \
--to=aoliva@redhat.com \
--cc=bernds@codesourcery.com \
--cc=gcc-patches@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).