public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "yangwang at nj dot iscas.ac.cn" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/107341] New: RISCV User Stack Frame error with -fno-omit-frame-pointer on GCC 10.2.0
Date: Fri, 21 Oct 2022 08:01:38 +0000	[thread overview]
Message-ID: <bug-107341-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 107341
           Summary: RISCV User Stack Frame error with
                    -fno-omit-frame-pointer on GCC 10.2.0
           Product: gcc
           Version: 10.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
          Assignee: unassigned at gcc dot gnu.org
          Reporter: yangwang at nj dot iscas.ac.cn
  Target Milestone: ---

Created attachment 53741
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53741&action=edit
C source code

gcc version 10.2.0 (SiFive GCC-Metal 10.2.0-2020.12.8)

1.compile test.c code
riscv64-unknown-elf-gcc -static -O0 -g -fno-omit-frame-pointer test.c -o test
-lm

2.Using perf record
sudo perf record -e cpu-clock -g ./test

3.Using perf script
sudo perf script > test.perf




at test.perf, you will find that normal_loop call normal_loop

test   769 22186.901402:     250000 cpu-clock: 
                   1018a normal_loop+0x34 (/home/test)
                   1019c normal_loop+0x46 (/home/test)
                   10104 _start+0x40 (/home/test)

             reply	other threads:[~2022-10-21  8:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-21  8:01 yangwang at nj dot iscas.ac.cn [this message]
2022-10-21  8:04 ` [Bug target/107341] " pinskia at gcc dot gnu.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-107341-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).