public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "camm at debian dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/63360] New: Does not retore f31 at -O0 across function calls
Date: Wed, 24 Sep 2014 18:56:00 -0000	[thread overview]
Message-ID: <bug-63360-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63360

            Bug ID: 63360
           Summary: Does not retore f31 at -O0 across function calls
           Product: gcc
           Version: 4.9.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: target
          Assignee: unassigned at gcc dot gnu.org
          Reporter: camm at debian dot org

Created attachment 33551
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=33551&action=edit
invert.c, invert.cpp, and invert.gdb gdb session

Register variable stored in f31 is stored on the stack, but not restored and
thus clobbered, after a function call.

Compiled with 

gcc -c -g  -Wall -fsigned-char -Wno-unused-but-set-variable -pipe -g -mlongcall


             reply	other threads:[~2014-09-24 18:56 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-24 18:56 camm at debian dot org [this message]
2014-09-24 22:18 ` [Bug target/63360] " bergner at gcc dot gnu.org
2014-09-25 14:47 ` camm at debian dot org
2014-09-25 14:59 ` camm at debian dot org
2014-09-25 15:00 ` camm at debian dot org
2014-09-25 15:05 ` schwab@linux-m68k.org
2014-09-25 16:16 ` camm at debian dot org
2014-09-25 16:17 ` camm at debian dot org
2014-09-25 17:10 ` bergner at gcc dot gnu.org
2014-09-25 17:26 ` camm at debian dot org
2014-09-25 19:02 ` bergner at gcc dot gnu.org
2014-09-25 19:24 ` camm at debian dot org
2014-09-25 19:36 ` camm at debian dot org
2014-09-25 19:47 ` camm at debian dot org
2014-09-25 19:52 ` camm at debian dot org
2014-09-25 20:12 ` camm at debian 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-63360-4@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: 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).