public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: ms@siroyan.com To: gcc-gnats@gcc.gnu.org Subject: c/4608: --save-temps breaks location information in dwarf1 output Date: Thu, 18 Oct 2001 09:16:00 -0000 [thread overview] Message-ID: <200110181606.RAA20084@stl01.stl.siroyan.com> (raw) >Number: 4608 >Category: c >Synopsis: --save-temps breaks location information in dwarf1 output >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Thu Oct 18 09:16:01 PDT 2001 >Closed-Date: >Last-Modified: >Originator: >Release: 3.0.1 >Organization: >Environment: System: SunOS stl01 5.7 Generic_106541-04 sun4u sparc SUNW,Ultra-5_10 Architecture: sun4 host: sparc-sun-solaris2.7 build: sparc-sun-solaris2.7 target: sparc-sun-solaris2.7 configured with: ../gcc/configure --prefix=/home/ms/native : (reconfigured) ../gcc/configure --prefix=/home/ms/native >Description: --save-temps causes the .c file to be processed by an external cpp and the resulting .i file to be passed into cc1. There are a number of comments in toplevel.c and elsewhere which indicate that the correct orignal filename id (.c) should be extracted from the initial #line directive and placed into "main_filename". This variable is passed into the dwarf emitter in order to emit the name of the original file. In practice "main_filename" remains set at the default .i filename causeing the dwarf emitter to emit the .i name instead of the .c. >How-To-Repeat: Compile any source .c with the options: gcc --save-temps -gdwarf -g1 t.c Inspecting the dwarf in the resulting t.s file will indicate the .i source instead of the .c >Fix: >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2001-10-18 9:16 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-10-18 9:16 ms [this message] 2001-11-04 15:37 neil 2001-11-04 22:41 neil
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=200110181606.RAA20084@stl01.stl.siroyan.com \ --to=ms@siroyan.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).