public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "inaoka dot kazuhiro at renesas dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/13786] New: can't disable ".debugsym" when both of -g and -m32r2 is specified
Date: Wed, 21 Jan 2004 05:35:00 -0000	[thread overview]
Message-ID: <20040121053456.13786.inaoka.kazuhiro@renesas.com> (raw)

command line:
m32r-elf-gcc -S -g -m32r2 func.c

Output like a following line debug information.
A .debugsym must be output when -m32r or -Os is specified.

func:
.stabn 68,0,2,.LM1-func
        .debugsym .LM1
        ; PROLOGUE, vars= 0, regs= 1, args= 0, extra= 0
        push fp
        mv fp,sp
.stabn 68,0,3,.LM2-func
        .debugsym .LM2
        ldi r4,#0       ; 0x0
.stabn 68,0,4,.LM3-func
        .debugsym .LM3
        mv r0,r4
        ; EPILOGUE
        pop fp
        jmp lr

-- 
           Summary: can't disable ".debugsym" when both of -g and -m32r2 is
                    specified
           Product: gcc
           Version: 3.4.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: debug
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: inaoka dot kazuhiro at renesas dot com
                CC: gcc-bugs at gcc dot gnu dot org
GCC target triplet: m32r-elf, m32r-linux


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13786


             reply	other threads:[~2004-01-21  5:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-21  5:35 inaoka dot kazuhiro at renesas dot com [this message]
2004-01-21  5:39 ` [Bug debug/13786] " inaoka dot kazuhiro at renesas dot com
2004-01-21  5:48 ` [Bug target/13786] " pinskia at gcc dot gnu dot org
2004-01-21  6:26 ` dhazeghi at yahoo dot com
2004-01-21 12:24 ` nickc at redhat dot com
2004-01-21 14:25 ` pinskia at gcc dot gnu 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=20040121053456.13786.inaoka.kazuhiro@renesas.com \
    --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).