From: Josef Zlomek <zlomj9am@artax.karlin.mff.cuni.cz>
To: Kazu Hirata <kazu@cs.umass.edu>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: Variable tracking (location lists support) - part 2
Date: Sat, 21 Feb 2004 13:45:00 -0000 [thread overview]
Message-ID: <20040211153613.GA3210@artax.karlin.mff.cuni.cz> (raw)
Message-ID: <20040221134500.Yat2N2gV5RNeqFklWsPWe9NFaP3xosZ4dUVXyIkbqYM@z> (raw)
In-Reply-To: <20040211.092114.23008033.kazu@cs.umass.edu>
> > this patch adds location list support to dwarf2out.c.
> > This generates the location list debug info from the NOTE_INSN_VAR_LOCATION
> > notes produces by the first patch of variable tracking.
> >
> > Bootstrapped/regtested x86-64 (standalone and together with the first part).
> >
> > Josef
> >
> > 2004-02-02 Daniel Berlin <dberlin@dberlin.org>
> > Josef Zlomek <zlomekj@suse.cz>
> >
> > * dwarf2out.c (struct gcc_debug_hooks): Call dwarf2out_begin_function
> > :
> > :
>
> This patch unfortunately breaks the build of h8300-elf. Specifically,
> I get assembler errors while compiling muldi3 of libgcc2.c. Here is a
> minimized testcase and the errors I get.
>
> int
> foo (int a)
> {
> return a;
> }
>
> /tmp/cchHQ5CR.s: Assembler messages:
> /tmp/cchHQ5CR.s:75: Error: can't resolve `.LVL0' {.text section} - `_.text' {*UND* section}
> /tmp/cchHQ5CR.s:76: Error: can't resolve `.LVL1' {.text section} - `_.text' {*UND* section}
> /tmp/cchHQ5CR.s:75: Error: Difference of symbols in different sections is not supported
> /tmp/cchHQ5CR.s:76: Error: Difference of symbols in different sections is not supported
There is a patch (http://gcc.gnu.org/ml/gcc-patches/2004-02/msg00826.html)
from Daniel Berlin submited several days before which should fix this.
Josef
next prev parent reply other threads:[~2004-02-11 15:36 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-02 20:37 Josef Zlomek
2004-02-06 3:34 ` Roger Sayle
2004-02-06 12:31 ` Josef Zlomek
2004-02-06 12:32 ` Josef Zlomek
2004-02-09 14:55 ` debug info breaks build (Was: Re: Variable tracking (location lists support) - part 2) Joern Rennecke
2004-02-09 15:45 ` Daniel Berlin
2004-02-09 16:34 ` Joern Rennecke
2004-02-09 17:26 ` Daniel Berlin
2004-02-09 21:48 ` Richard Henderson
2004-02-10 18:05 ` Josef Zlomek
2004-02-10 18:12 ` Daniel Berlin
2004-02-21 13:45 ` Daniel Berlin
2004-02-21 13:45 ` Josef Zlomek
2004-02-21 13:45 ` Richard Henderson
2004-02-21 13:45 ` Daniel Berlin
2004-02-21 13:45 ` Joern Rennecke
2004-02-21 13:45 ` Daniel Berlin
2004-02-21 13:45 ` Joern Rennecke
2004-02-21 13:45 ` Variable tracking (location lists support) - part 2 Josef Zlomek
2004-02-06 13:41 ` Roger Sayle
2004-02-08 22:24 ` Roger Sayle
2004-02-08 23:01 ` Josef Zlomek
2004-02-21 13:45 ` Josef Zlomek
2004-02-21 13:45 ` Roger Sayle
2004-02-21 13:45 ` Roger Sayle
2004-02-21 13:45 ` Josef Zlomek
2004-02-21 13:45 ` Roger Sayle
2004-02-11 14:55 ` Kazu Hirata
2004-02-11 16:06 ` Josef Zlomek [this message]
2004-02-21 13:45 ` Josef Zlomek
2004-02-11 16:11 ` Rainer Orth
2004-02-11 17:15 ` Daniel Berlin
2004-02-11 17:32 ` Rainer Orth
2004-02-21 13:45 ` Rainer Orth
2004-02-21 13:45 ` Daniel Berlin
2004-02-21 13:45 ` Rainer Orth
2004-02-11 16:47 ` Daniel Berlin
2004-02-11 17:50 ` Kazu Hirata
2004-02-11 18:12 ` Zack Weinberg
2004-02-21 13:45 ` Zack Weinberg
2004-02-21 13:45 ` Kazu Hirata
2004-02-21 13:45 ` Daniel Berlin
2004-02-21 13:45 ` Kazu Hirata
2004-02-21 13:45 ` Josef Zlomek
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=20040211153613.GA3210@artax.karlin.mff.cuni.cz \
--to=zlomj9am@artax.karlin.mff.cuni.cz \
--cc=gcc-patches@gcc.gnu.org \
--cc=kazu@cs.umass.edu \
/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).