public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "aoliva at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/42648] [4.5/4.6 Regression] gcc.dg/guality/pr41353-1.c FAILs at -On, n > 0
Date: Thu, 10 Jun 2010 18:50:00 -0000	[thread overview]
Message-ID: <20100610185025.7413.qmail@sourceware.org> (raw)
In-Reply-To: <bug-42648-10053@http.gcc.gnu.org/bugzilla/>



------- Comment #7 from aoliva at gcc dot gnu dot org  2010-06-10 18:50 -------
Steve, I only see problems on ia64 at -O3, and that's because VTA is disabled
when selective scheduling is enabled.

Uros, I can't duplicate the problem with a cross compiler for alpha: the debug
info in the assembly output and in the vartrack dump looks just right to me. 
I'm not sure how to proceed, maybe post evidence that GCC is actually producing
incorrect debug info, rather than that say the assembler is mangling it or GDB
is misinterpreting it?

Richard, if you can still duplicate the problem on your end, can you help? 
debug bind stmts for incoming args are not expected at the entry point, they're
only inserted when the function is inlined or early in the var-tracking pass.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42648


  parent reply	other threads:[~2010-06-10 18:50 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-07 16:36 [Bug debug/42648] New: [4.5 " rguenth at gcc dot gnu dot org
2010-01-11  8:35 ` [Bug debug/42648] " jakub at gcc dot gnu dot org
2010-02-16 10:37 ` rguenth at gcc dot gnu dot org
2010-02-17 16:53 ` mmitchel at gcc dot gnu dot org
2010-03-20 13:03 ` steven at gcc dot gnu dot org
2010-04-05  5:06 ` aoliva at gcc dot gnu dot org
2010-04-05  7:48 ` aoliva at gcc dot gnu dot org
2010-04-05 18:02 ` ubizjak at gmail dot com
2010-04-06 11:26 ` rguenth at gcc dot gnu dot org
2010-04-21 16:27 ` [Bug debug/42648] [4.5/4.6 " sje at cup dot hp dot com
2010-06-10 18:50 ` aoliva at gcc dot gnu dot org [this message]
2010-06-10 19:27 ` sje at cup dot hp dot com
2010-06-11 10:50 ` aoliva at gcc dot gnu dot org
2010-06-24  3:34 ` aoliva at gcc dot gnu dot 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=20100610185025.7413.qmail@sourceware.org \
    --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).