From: Alexandre Oliva <aoliva@redhat.com>
To: gcc-patches@gcc.gnu.org
Subject: Re: debug insns in SMS
Date: Wed, 13 Jun 2012 08:07:00 -0000 [thread overview]
Message-ID: <ormx4763ij.fsf@livre.localdomain> (raw)
In-Reply-To: <or7gxpe6qt.fsf@livre.localdomain> (Alexandre Oliva's message of "Mon, 09 Apr 2012 03:53:14 -0300")
On Apr 9, 2012, Alexandre Oliva <aoliva@redhat.com> wrote:
>>> I think this will restore proper functioning to SMS in the presence of
>>> debug insns. A while ago, we'd never generate deps of non-debug insns
>>> on debug insns. I introduced them to enable sched to adjust (reset)
>>> debug insns when non-debug insns were moved before them. I believe it
>>> is safe to leave them out of the SCCs. Even though this will end up
>>> causing some loss of debug info, that's probably unavoidable, and the
>>> end result after this change is pobably the best we can hope for. Your
>>> thoughts?
> for gcc/ChangeLog
> from Alexandre Oliva <aoliva@redhat.com>
> * ddg.c (build_intra_loop_deps): Discard deps of nondebug on debug.
> Ping?
http://gcc.gnu.org/ml/gcc-patches/2012-04/msg00419.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
next prev parent reply other threads:[~2012-06-13 8:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <OFFA1E9979.E0BBC3C3-ONC2257884.004228E1-C2257884.0048FF4A@il.ibm.com>
[not found] ` <ormxj5m9yy.fsf@livre.localdomain>
[not found] ` <OF77DA4497.F3AFFC59-ONC2257885.002FEAEA-C2257885.003268D3@il.ibm.com>
2011-05-04 7:27 ` debug insns in SMS (was: Re: Debug_insn) Alexandre Oliva
2011-05-04 9:02 ` debug insns in SMS Alexandre Oliva
2011-05-04 9:33 ` debug insns in SMS (was: Re: Debug_insn) Revital1 Eres
2012-04-09 6:53 ` debug insns in SMS Alexandre Oliva
2012-06-13 8:07 ` Alexandre Oliva [this message]
2012-06-13 22:08 ` Alexandre Oliva
2012-06-14 17:03 ` Ayal Zaks
2012-06-22 1:40 ` Alexandre Oliva
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=ormx4763ij.fsf@livre.localdomain \
--to=aoliva@redhat.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).