public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/64003] valgrind complains about get_attr_length_nobnd in insn-attrtab.c from i386.md
Date: Thu, 20 Nov 2014 19:27:00 -0000 [thread overview]
Message-ID: <bug-64003-4-7qgMqMma4V@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64003-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64003
--- Comment #4 from dmalcolm at gcc dot gnu.org ---
(In reply to dmalcolm from comment #3)
> fwiw, "insn" seems to be:
>
> (jump_insn:TI 10 4 56 2 (set (pc)
> (if_then_else (eq (reg:CCGC 17 flags)
> (const_int 0 [0]))
> (label_ref 29)
> (pc)))
> /home/david/coding-3/gcc-git-jit-valgrind/get-attr-length-i386.c:3 610
> {*jcc_1}
> (int_list:REG_BR_PROB 2000 (nil))
> -> 29)
...so presumably it's the attr highlighted below:
10920 (define_insn "*jcc_1"
10921 [(set (pc)
10922 (if_then_else (match_operator 1 "ix86_comparison_operator"
10923 [(reg FLAGS_REG) (const_int 0)])
10924 (label_ref (match_operand 0))
10925 (pc)))]
10926 ""
10927 "%!%+j%C1\t%l0"
10928 [(set_attr "type" "ibr")
10929 (set_attr "modrm" "0")
>10930 (set (attr "length_nobnd")
>10931 (if_then_else (and (ge (minus (match_dup 0) (pc))
>10932 (const_int -126))
>10933 (lt (minus (match_dup 0) (pc))
>10934 (const_int 128)))
>10935 (const_int 2)
>10936 (const_int 6)))])
10937
next prev parent reply other threads:[~2014-11-20 19:27 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-20 18:39 [Bug rtl-optimization/64003] New: " dmalcolm at gcc dot gnu.org
2014-11-20 18:41 ` [Bug rtl-optimization/64003] " dmalcolm at gcc dot gnu.org
2014-11-20 18:54 ` dmalcolm at gcc dot gnu.org
2014-11-20 19:23 ` dmalcolm at gcc dot gnu.org
2014-11-20 19:27 ` dmalcolm at gcc dot gnu.org [this message]
2014-11-20 19:41 ` dmalcolm at gcc dot gnu.org
2014-11-21 19:04 ` [Bug target/64003] " dmalcolm at gcc dot gnu.org
2014-12-02 2:20 ` dmalcolm at gcc dot gnu.org
2014-12-02 15:40 ` dmalcolm at gcc dot gnu.org
2014-12-02 15:48 ` dmalcolm at gcc dot gnu.org
2014-12-02 15:54 ` dmalcolm at gcc dot gnu.org
2014-12-02 16:08 ` dmalcolm at gcc dot gnu.org
2014-12-02 16:13 ` dmalcolm at gcc dot gnu.org
2014-12-04 9:24 ` amylaar at gcc dot gnu.org
2014-12-04 18:43 ` law at redhat dot com
2014-12-04 18:44 ` law at redhat dot com
2014-12-04 19:19 ` amylaar at gcc dot gnu.org
2014-12-04 19:38 ` enkovich.gnu at gmail dot com
2014-12-04 19:45 ` amylaar at gcc dot gnu.org
2014-12-04 19:51 ` law at redhat dot com
2014-12-04 19:54 ` law at redhat dot com
2014-12-05 10:07 ` enkovich.gnu at gmail dot com
2014-12-05 10:08 ` enkovich.gnu at gmail dot com
2014-12-05 10:38 ` ubizjak at gmail dot com
2014-12-05 10:50 ` ubizjak at gmail dot com
2014-12-05 14:19 ` rsandifo at gcc dot gnu.org
2014-12-05 15:01 ` enkovich.gnu at gmail dot com
2014-12-05 16:01 ` ienkovich at gcc dot gnu.org
2015-04-16 14:08 ` ienkovich at gcc dot gnu.org
2015-07-24 8:32 ` ubizjak at gmail dot com
2015-07-24 8:36 ` ubizjak at gmail dot com
2015-07-24 16:26 ` uros at gcc dot gnu.org
2015-07-24 16:31 ` ubizjak at gmail dot com
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-64003-4-7qgMqMma4V@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).