public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: inaoka.kazuhiro@renesas.com To: gcc-gnats@gcc.gnu.org Subject: target/10775: m32r-elf-gcc -O3 (regrename) used lr in leaf-functions without saving Date: Wed, 14 May 2003 06:16:00 -0000 [thread overview] Message-ID: <20030514060813.20528.qmail@sources.redhat.com> (raw) >Number: 10775 >Category: target >Synopsis: m32r-elf-gcc -O3 (regrename) used lr in leaf-functions without saving >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: wrong-code >Submitter-Id: net >Arrival-Date: Wed May 14 06:16:00 UTC 2003 >Closed-Date: >Last-Modified: >Originator: Kazuhiro Inaoka >Release: gcc 3.2.3 >Organization: >Environment: Linux 2.4.18-24.7.x i686, target m32r-elf >Description: In gcc/testsuite: FAIL: gcc.c-torture/execute/20000726-1.c execution, -O3 -fomit-frame-pointer FAIL: gcc.c-torture/execute/20000726-1.c execution, -O3 -g When regrename optimizing (-O3) in leaf-functions, lr(R14) was used without saving. >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted: ----gnatsweb-attachment---- Content-Type: application/octet-stream; name="20000726-1.c" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="20000726-1.c" dm9pZCBhZGp1c3RfeHkgKHNob3J0ICosIHNob3J0ICopOwoKc3RydWN0IGFkanVzdF90ZW1wbGF0 ZQp7CiAgc2hvcnQga3hfeDsKICBzaG9ydCBreF95OwogIHNob3J0IGt4OwogIHNob3J0IGt6Owp9 OwoKc3RhdGljIHN0cnVjdCBhZGp1c3RfdGVtcGxhdGUgYWRqdXN0ID0gezAsIDAsIDEsIDF9OwoK bWFpbiAoKQp7CiAgc2hvcnQgeCA9IDEsIHkgPSAxOwoKICBhZGp1c3RfeHkgKCZ4LCAmeSk7Cgog IGlmICh4ICE9IDEpCiAgICBhYm9ydCAoKTsKCiAgZXhpdCAoMCk7Cn0KCnZvaWQKYWRqdXN0X3h5 ICh4LCB5KQogICAgIHNob3J0ICAqeDsKICAgICBzaG9ydCAgKnk7CnsKICAqeCA9IGFkanVzdC5r eF94ICogKnggKyBhZGp1c3Qua3hfeSAqICp5ICsgYWRqdXN0Lmt4Owp9Cg==
next reply other threads:[~2003-05-14 6:16 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-05-14 6:16 inaoka.kazuhiro [this message] 2003-05-14 18:16 Dara Hazeghi 2003-05-15 10:56 Kazuhiro Inaoka
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=20030514060813.20528.qmail@sources.redhat.com \ --to=inaoka.kazuhiro@renesas.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: 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).