From: Vladimir Makarov <vmakarov@redhat.com>
To: Maxim Kuvyrkov <maxim@codesourcery.com>
Cc: Andrey Belevantsev <abel@ispras.ru>,
gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Fix ICE in ia64 speculation support
Date: Thu, 20 Sep 2007 20:47:00 -0000 [thread overview]
Message-ID: <46F2D838.4040309@redhat.com> (raw)
In-Reply-To: <46E97245.5010107@codesourcery.com>
Maxim Kuvyrkov wrote:
> Hi,
>
> This patch fixes minor bug in ia64 speculation support.
>
> The issue is that may_trap_p () can return different results given
> normal instruction and its speculative version. E.g., this occurs for
> (set (reg:DF) (mem:DF)) and (set (reg:DF) (unspec:DF [(mem:DF)]
> DATA_SPEC)). The latter is a speculative variant of the former and
> may_trap_p () always returns 'true' for the speculative version
> because unspec:DF is considered a random floating point operation that
> might trap.
>
> This causes an assert, that checks that a speculative insn can stay
> speculative, fail. The fix is to use original pattern when calling
> may_trap_p ().
>
> The bug was reported by Andrey and implicates itself only with '-O2
> -funroll-loops' (the options tested by default do not include this
> combination). The testcase is a copy of
> gcc.c-torture/execute/20040709-1.c but with forced -funroll-loops.
>
> OK for trunk?
>
>
Sorry, I can reproduce the bug. I've tried today repository. No luck.
I think that right solution would be make may_trap_p to understand that
the insn is speculative. But without reproducing the bug, I can not be
sure about my proposal.
Vlad
next prev parent reply other threads:[~2007-09-20 20:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-13 17:42 Maxim Kuvyrkov
2007-09-20 20:47 ` Vladimir Makarov [this message]
2007-09-20 21:51 ` Vladimir Makarov
2007-09-21 9:18 ` Maxim Kuvyrkov
2007-09-21 9:38 ` Paolo Bonzini
2007-09-21 9:53 ` Maxim Kuvyrkov
2007-09-21 10:43 ` Paolo Bonzini
2007-10-14 18:04 ` Maxim Kuvyrkov
2007-10-15 8:06 ` Paolo Bonzini
2007-10-15 8:17 ` Eric Botcazou
2007-10-15 10:52 ` Maxim Kuvyrkov
2007-10-15 21:57 ` Jim Wilson
2007-10-16 9:51 ` Maxim Kuvyrkov
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=46F2D838.4040309@redhat.com \
--to=vmakarov@redhat.com \
--cc=abel@ispras.ru \
--cc=gcc-patches@gcc.gnu.org \
--cc=maxim@codesourcery.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).