public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/60756] var-tracking selects wrong registers
Date: Fri, 04 Apr 2014 17:13:00 -0000 [thread overview]
Message-ID: <bug-60756-4-2umfVrB6cl@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-60756-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60756
--- Comment #3 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
> Yes, this testcase works better with -fno-var-tracking-assignments.
That's expected for the param-[123].c testcases.
> It seems to be a mixed bag, though. Running the testsuite with this
> argument causes 79 previously failing guality tests to pass, but
> causes 200 more new failures.
Yes, both modes have severe limitations.
> I wonder if there's some way to get the best of both worlds?
That's what I have been trying to do recently for these testcases: selectively
shut down -fvar-tracking-assignments to track the location instead of the
value, because it's for aggregate parameters and they are rarely modified.
I'll investigate why this isn't sufficient on aarch64.
prev parent reply other threads:[~2014-04-04 17:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-60756-4@http.gcc.gnu.org/bugzilla/>
2014-04-04 0:52 ` rth at gcc dot gnu.org
2014-04-04 10:00 ` ebotcazou at gcc dot gnu.org
2014-04-04 15:34 ` rth at gcc dot gnu.org
2014-04-04 17:13 ` ebotcazou at gcc dot gnu.org [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=bug-60756-4-2umfVrB6cl@http.gcc.gnu.org/bugzilla/ \
--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).