public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug lto/49123] [4.6 Regression] FAIL: gcc.c-torture/execute/pr48973-[12].c Date: Mon, 23 May 2011 13:45:00 -0000 [thread overview] Message-ID: <bug-49123-4-aUlRrNnW6h@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-49123-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49123 --- Comment #3 from Richard Guenther <rguenth at gcc dot gnu.org> 2011-05-23 13:22:12 UTC --- The 1 is non-canonical: (gdb) call debug_tree ($1) <integer_cst 0x7ffff5b25eb0 type <integer_type 0x7ffff5b29540> constant 1> (gdb) call debug_tree (0x7ffff5b29540) <integer_type 0x7ffff5b29540 public QI size <integer_cst 0x7ffff7e734d8 type <integer_type 0x7ffff7e860a8 bit_size_type> constant 8> unit size <integer_cst 0x7ffff7e73500 type <integer_type 0x7ffff7e86000 long unsigned int> constant 1> align 8 symtab 0 alias set -1 canonical type 0x7ffff5b29540 precision 1 min <integer_cst 0x7ffff5b25690 -1> max <integer_cst 0x7ffff5b256b8 0>> (gdb) p $1->int_cst. common int_cst (gdb) p $1->int_cst.int_cst $2 = {low = 1, high = 0} built via build_int_cst, fixed on trunk by properly making that produce canonical constants.
next prev parent reply other threads:[~2011-05-23 13:44 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-05-23 13:29 [Bug lto/49123] New: " hjl.tools at gmail dot com 2011-05-23 13:34 ` [Bug lto/49123] " rguenth at gcc dot gnu.org 2011-05-23 13:44 ` rguenth at gcc dot gnu.org 2011-05-23 13:45 ` rguenth at gcc dot gnu.org [this message] 2011-05-23 13:46 ` jakub at gcc dot gnu.org 2011-05-23 13:52 ` rguenth at gcc dot gnu.org 2011-05-23 14:17 ` jakub at gcc dot gnu.org 2011-05-23 14:23 ` rguenth at gcc dot gnu.org 2011-05-23 15:20 ` hjl.tools at gmail dot com 2011-05-23 20:55 ` jakub at gcc dot gnu.org 2011-05-23 20:56 ` jakub at gcc dot gnu.org 2011-05-23 21:02 ` jakub at gcc dot gnu.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=bug-49123-4-aUlRrNnW6h@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: linkBe 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).