public inbox for ecos-bugs@sourceware.org help / color / mirror / Atom feed
From: bugzilla-daemon@bugs.ecos.sourceware.org To: unassigned@bugs.ecos.sourceware.org Subject: [Bug 1001999] New: adder.S: Error: operand out of range Date: Fri, 04 Jul 2014 09:46:00 -0000 [thread overview] Message-ID: <bug-1001999-777@http.bugs.ecos.sourceware.org/> (raw) Please do not reply to this email, use the link below. http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001999 Bug ID: 1001999 Summary: adder.S: Error: operand out of range Product: eCos Version: unknown Target: All Architecture/Host Other OS: Status: UNCONFIRMED Severity: enhancement Priority: low Component: HAL Assignee: unassigned@bugs.ecos.sourceware.org Reporter: mrandreas@hotmail.com CC: ecos-bugs@ecos.sourceware.org I have issues finding the root of this problem: packages/hal/powerpc/adder/current/src/adder.S:401: Error: operand out of range (0x0000ffffffffe000 is not between 0x0000000000000000 and 0x000000000000ffff) The compiler powerpc-860-linux-gnu-gcc is complaining about the last of these line in adder.S mflr r3 lwi r4, 0x00FFFFF and r3,r3,r4 oris r3,r3,CYGMEM_REGION_rom>>16 I had no problem 32 bit version of ubuntu 12.04 LTS, while the 64 bit version I've stumbled on this one while building redboot. Obvious it's trying to put a 32 bit value into an 16 bit and fail to acept this. Any clue what to look for? Is there a 16 bit / 32 bit prosessor definition causing this? thanks Andreas -- You are receiving this mail because: You are the assignee for the bug.
next reply other threads:[~2014-07-04 9:46 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-07-04 9:46 bugzilla-daemon [this message] 2014-07-04 9:59 ` [Bug 1001999] " bugzilla-daemon 2014-07-04 9:46 [Bug 1001999] New: " bugzilla-daemon
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-1001999-777@http.bugs.ecos.sourceware.org/ \ --to=bugzilla-daemon@bugs.ecos.sourceware.org \ --cc=unassigned@bugs.ecos.sourceware.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).