* [VTA merge] Some dwarf problems
@ 2009-09-21 16:04 Hariharan
2009-09-21 16:29 ` Jack Howarth
2009-09-21 19:52 ` Jakub Jelinek
0 siblings, 2 replies; 4+ messages in thread
From: Hariharan @ 2009-09-21 16:04 UTC (permalink / raw)
To: gcc, aoliva
Hi Alexandre,
I was having some trouble with dwarf sections in picochip port. I am not
a dwarf expert, but when i looked at the changes in r151312, file
dwarf2out.c, function dwarf2out_var_location on line 17965, we have
sprintf (loclabel, "%s-1", last_label);
...
What is last_label-1 supposed to point to?
Thanks for your help.
Hari
^ permalink raw reply [flat|nested] 4+ messages in thread* Re: [VTA merge] Some dwarf problems
2009-09-21 16:04 [VTA merge] Some dwarf problems Hariharan
@ 2009-09-21 16:29 ` Jack Howarth
2009-09-21 19:52 ` Jakub Jelinek
1 sibling, 0 replies; 4+ messages in thread
From: Jack Howarth @ 2009-09-21 16:29 UTC (permalink / raw)
To: Hariharan; +Cc: gcc, aoliva
On Mon, Sep 21, 2009 at 05:04:27PM +0100, Hariharan wrote:
> Hi Alexandre,
> I was having some trouble with dwarf sections in picochip port. I am not
> a dwarf expert, but when i looked@the changes in r151312, file
> dwarf2out.c, function dwarf2out_var_location on line 17965, we have
>
> sprintf (loclabel, "%s-1", last_label);
> ...
>
> What is last_label-1 supposed to point to?
>
> Thanks for your help.
>
> Hari
>
>
Hari,
Does the binutils on pico understand dwarf3/dwarf4? We ran into
breakage of the bootstrap on darwin...
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41405
due to r151815 which was based on the assumption that all
of the targets could handle dwarf3/dwarf4 instructions.
If not, a proposed patch for a -gstrict-dwarf option is
being worked on there.
Jack
^ permalink raw reply [flat|nested] 4+ messages in thread* Re: [VTA merge] Some dwarf problems
2009-09-21 16:04 [VTA merge] Some dwarf problems Hariharan
2009-09-21 16:29 ` Jack Howarth
@ 2009-09-21 19:52 ` Jakub Jelinek
2009-09-21 22:43 ` Hariharan
1 sibling, 1 reply; 4+ messages in thread
From: Jakub Jelinek @ 2009-09-21 19:52 UTC (permalink / raw)
To: Hariharan; +Cc: gcc, aoliva
On Mon, Sep 21, 2009 at 05:04:27PM +0100, Hariharan wrote:
> Hi Alexandre,
> I was having some trouble with dwarf sections in picochip port. I am not
> a dwarf expert, but when i looked at the changes in r151312, file
> dwarf2out.c, function dwarf2out_var_location on line 17965, we have
>
> sprintf (loclabel, "%s-1", last_label);
> ...
>
> What is last_label-1 supposed to point to?
See http://gcc.gnu.org/ml/gcc-patches/2009-06/msg01317.html
for details. 1 byte before last_label label (which is usually right after a
call insn). The intent is to have something in the middle of a call insn.
Jakub
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [VTA merge] Some dwarf problems
2009-09-21 19:52 ` Jakub Jelinek
@ 2009-09-21 22:43 ` Hariharan
0 siblings, 0 replies; 4+ messages in thread
From: Hariharan @ 2009-09-21 22:43 UTC (permalink / raw)
To: Jakub Jelinek; +Cc: gcc, aoliva
Thanks for the pointer, Jakub.
Cheers
Hari
Jakub Jelinek wrote:
> On Mon, Sep 21, 2009 at 05:04:27PM +0100, Hariharan wrote:
>
>> Hi Alexandre,
>> I was having some trouble with dwarf sections in picochip port. I am not
>> a dwarf expert, but when i looked at the changes in r151312, file
>> dwarf2out.c, function dwarf2out_var_location on line 17965, we have
>>
>> sprintf (loclabel, "%s-1", last_label);
>> ...
>>
>> What is last_label-1 supposed to point to?
>>
>
> See http://gcc.gnu.org/ml/gcc-patches/2009-06/msg01317.html
> for details. 1 byte before last_label label (which is usually right after a
> call insn). The intent is to have something in the middle of a call insn.
>
> Jakub
>
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2009-09-21 22:43 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2009-09-21 16:04 [VTA merge] Some dwarf problems Hariharan
2009-09-21 16:29 ` Jack Howarth
2009-09-21 19:52 ` Jakub Jelinek
2009-09-21 22:43 ` Hariharan
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).