public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: speja@telia.com
To: gcc-gnats@gcc.gnu.org
Subject: target/10848: avr-gcc (3.2) generates bad assembler code
Date: Sun, 18 May 2003 21:46:00 -0000	[thread overview]
Message-ID: <20030518214345.11979.qmail@sources.redhat.com> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2143 bytes --]


>Number:         10848
>Category:       target
>Synopsis:       avr-gcc (3.2) generates bad assembler code
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          wrong-code
>Submitter-Id:   net
>Arrival-Date:   Sun May 18 21:46:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator:     Peter Janhäll
>Release:        3.2
>Organization:
>Environment:
Linux bums 2.2.5-22 #1 Wed Jun 2 09:02:27 EDT 1999 i586 unknown
>Description:
bums!speja% avr-gcc -g --save-temps error2.c
error2.s: Assembler messages:
error2.s:128: Error: operand out of range: -65

bums!speja% avr-gcc -v
Reading specs from /home/speja/local/lib/gcc-lib/avr/3.2/specs
Configured with: ../gcc-3.2/configure --prefix=/home/speja/local --enable-languages=c --program-prefix=avr- --target=avr
Thread model: single
gcc version 3.2

bums!speja% avr-as -v
GNU assembler version 2.14.90 (avr) using BFD version 2.14.90 20030517


>How-To-Repeat:
Compile error2.c with 'avr-gcc', it will not pass the assembler.
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: application/octet-stream; name="error2.c"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="error2.c"

CnN0YXRpYyB1bnNpZ25lZCBjaGFyIGV2ZW50c1sxNl0sIHJpeD0wLCB3aXg9MDsKCi8qIEVuYWJs
aW5nIHRoZSBmb2xsb3dpbmcgZnVuY3Rpb24gcHJvZHVjZXMgYSBzZWNvbmQgZXJyb3IgKi8KI2lm
IDAKaW50IGZvbyh1bnNpZ25lZCB4LCB1bnNpZ25lZCBpKSB7CiAgcmV0dXJuICEoeCYoMTw8aSkp
Owp9CiNlbmRpZgoKc3RhdGljIHVuc2lnbmVkIGNoYXIga2l4PTAsIGxhc3RrZXlzWzNdLCBsYXN0
a2V5OwoKdm9pZCBrZXlfcG9sbCh2b2lkKSB7CiAgdW5zaWduZWQgY2hhciB4OwogIHVuc2lnbmVk
IGNoYXIgaTsKICBsYXN0a2V5c1traXhdID0gNTU7CiAgeCA9IChsYXN0a2V5c1swXSZsYXN0a2V5
c1sxXSkKICAgIHwgKGxhc3RrZXlzWzBdJmxhc3RrZXlzWzJdKQogICAgfCAobGFzdGtleXNbMV0m
bGFzdGtleXNbMl0pOwogIGlmICggeCAhPSBsYXN0a2V5KQogICAgZm9yIChpPTA7IGk8ODsgaSsr
KQogICAgICBpZiAoKGxhc3RrZXleeCkmKDE8PGkpKSB7Cgl1bnNpZ25lZCBjaGFyIHogPSAod2l4
KzEpJWxlbmd0aChldmVudHMpOwoJaWYgKHJpeCAhPSB6ICkgewoJICBldmVudHNbd2l4XSA9IChp
KzEpPDwxOwoJICBpZiAoISh4JigxPDxpKSkpCgkgICAgZXZlbnRzW3dpeF0gfD0gMTsKCX0KICAg
ICAgfQp9CgoKCg==


                 reply	other threads:[~2003-05-18 21:46 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20030518214345.11979.qmail@sources.redhat.com \
    --to=speja@telia.com \
    --cc=gcc-gnats@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).