public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hjl at lucon dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/30474] New: Bad 16bit constant code generation on 64bit host Date: Mon, 15 Jan 2007 18:59:00 -0000 [thread overview] Message-ID: <bug-30474-682@http.gcc.gnu.org/bugzilla/> (raw) score_print_operand has 'U' print hi part of a CONST_INT rtx else if (c == 'U') { gcc_assert (code == CONST_INT); fprintf (file, HOST_WIDE_INT_PRINT_HEX, (unsigned HOST_WIDE_INT) INTVAL (op) >> 16); } On 64bit host, for (const_int -2147483648 [0xffffffff80000000]), it will generate 0xffffffff8000. -- Summary: Bad 16bit constant code generation on 64bit host Product: gcc Version: 4.3.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: hjl at lucon dot org GCC target triplet: score-unknown-elf http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30474
next reply other threads:[~2007-01-15 18:59 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-01-15 18:59 hjl at lucon dot org [this message] 2007-05-10 7:21 ` [Bug target/30474] " liqin at gcc dot gnu dot org 2007-05-23 5:50 ` liqin at gcc dot gnu dot org 2007-05-23 6:10 ` liqin at gcc dot gnu dot org 2007-05-23 6:35 ` liqin 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=bug-30474-682@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).