d for a web page, or EPS files for printing.
The copyright notice is for Corel's PostScript code in the EPS file, not
for the entire graphic.
--
Michael Eager
--
Dwarf-discuss mailing list
Dwarf-discuss@lists.dwarfstd.org
https://lists.dwarfstd.org/mailman/listinfo/dwarf-discuss
n how
unnamed bit fields should be described would be in the body of the
standard. (And the example could be extended.)
Or this is yet another case that people would prefer to leave things as is
DWARF-spec-wise
and we should go file bug reports with GCC and Clang?
Sub
a proposal on the Public Comment page:
https://dwarfstd.org/Comment.php. Describe the issue briefly and, if
possible, please specify the change to the wording of the DWARF
Standard that would think appropriate.
--
Michael Eager
___
Dwarf-Discuss maili
itions for a DWARF
attribute, one in an ABI and a different one in the DWARF Spec. We want
to avoid situations where one producer says "I'm following DWARF" and
another "I'm following the ABI". That makes interoperability difficult.
The information you mention in an
(describing a bit field with a certain
size), submit an issue. Alternately, Todd suggested a new flag to
identify a bit field.
--
Michael Eager
___
Dwarf-Discuss mailing list
Dwarf-Discuss@lists.dwarfstd.org
http://lists.dwarfstd.org/listinfo.cgi/dwarf-discuss-dwarfstd.org
g/docs/AMDGPUUsage.html
[2] https://www.mail-archive.com/gcc@gcc.gnu.org/msg97797.html
___
Dwarf-Discuss mailing list
Dwarf-Discuss@lists.dwarfstd.org
http://lists.dwarfstd.org/listinfo.cgi/dwarf-discuss-dwarfstd.org
--
Michael Eager
_
to encode the source file information so that the producers and
consumers agree.
Thank you,
Eugene
___
Dwarf-Discuss mailing list
Dwarf-Discuss@lists.dwarfstd.org
http://lists.dwarfstd.org/listinfo.cgi/dwarf-discuss-dwarfstd.org
ose. You cannot say the same about vtable pointers which can
have any (or no) name.
--
Michael Eager
___
Dwarf-Discuss mailing list
Dwarf-Discuss@lists.dwarfstd.org
http://lists.dwarfstd.org/listinfo.cgi/dwarf-discuss-dwarfstd.org
< 3><0x026b> DW_TAG_variable
DW_AT_name RESULT
DW_AT_location 0x766806
DW_OP_breg6-24 DW_OP_deref
DW_AT_type
___
registers.
Best Regards,
Archana
On Tue, Mar 9, 2021 at 11:07 PM Michael Eager <mailto:ea...@eagercon.com>> wrote:
It's difficult to offer advice with such a spare description.
You might read the executable and relocate the .debug_info and
other debug sections
tion attribute is the constant
DW_CC_nocall, the subroutine does not obey standard calling conventions,
and it may not be safe for the debugger to call this subroutine."
All that says is that you can't call the function. It doesn't
describe how to call functions with n
is a more general way to
describe optimizations.
--
Michael Eager
___
Dwarf-Discuss mailing list
Dwarf-Discuss@lists.dwarfstd.org
http://lists.dwarfstd.org/listinfo.cgi/dwarf-discuss-dwarfstd.org
--
From: *Michael Eager* mailto:ea...@eagercon.com>>
Date: Sat, Mar 6, 2021 at 10:53 PM
Subject: Re: [Dwarf-Discuss] Retrieving variables, function address
using dwarf
To: Archana Deshmukh mailto:desharchan...@gmail.com>>, mailto:dwarf-discuss@lists.dwarfstd.org>>
ions when a compiler might place a function return
value in a variety of different locations, not constrained by the
ABI, a DWARF attribute might be useful.
--
Michael Eager
___
Dwarf-Discuss mailing list
Dwarf-Discuss@lists.dwarfstd.org
http://lists.dwarf
the DWARF
debug data.
DWARF does not contain information about the process memory
layout, such as the location of the heap or the start of the
stack.
--
Michael Eager
___
Dwarf-Discuss mailing list
Dwarf-Discuss@lists.dwarfstd.org
http://lists.dw
in."
Make sure that you have filled in all fields before submitting comment.
--
Michael Eager
___
Dwarf-Discuss mailing list
Dwarf-Discuss@lists.dwarfstd.org
http://lists.dwarfstd.org/listinfo.cgi/dwarf-discuss-dwarfstd.org
//lists.dwarfstd.org/listinfo.cgi/dwarf-discuss-dwarfstd.org
--
Michael Eager
___
Dwarf-Discuss mailing list
Dwarf-Discuss@lists.dwarfstd.org
http://lists.dwarfstd.org/listinfo.cgi/dwarf-discuss-dwarfstd.org
participating on the DWARF Committee please
contact me privately.
--
Michael Eager, DWARF Committee Chair
___
Dwarf-Discuss mailing list
Dwarf-Discuss@lists.dwarfstd.org
http://lists.dwarfstd.org/listinfo.cgi/dwarf-discuss-dwarfstd.org
t of
a group which works well together and is trying to do the right thing. Thanks
and fare well!
-John
-Original Message-
From: Dwarf-Workgroup On Behalf Of
Jason Merrill via Dwarf-Workgroup
Sent: Monday, September 7, 2020 5:39 PM
To: Michael Eager
Cc: dwarf-workgr...@lists
On 9/1/20 6:59 AM, David Anderson wrote:
Mike Eager: please delete the new issue 200831.1 as it is simply wrong.
Done.
--
Michael Eager
___
Dwarf-Discuss mailing list
Dwarf-Discuss@lists.dwarfstd.org
http://lists.dwarfstd.org/listinfo.cgi/dwarf
ar to be
a name, or if the email address appears to be invalid, the member will
be unsubscribed.
You can update your subscription by following the link at the bottom of
this message. Thanks for your understanding.
--
Michael Eager
___
Dwarf-Di
spaces?
--
Michael Eager
___
Dwarf-Discuss mailing list
Dwarf-Discuss@lists.dwarfstd.org
http://lists.dwarfstd.org/listinfo.cgi/dwarf-discuss-dwarfstd.org
proposal covers
multiple
sections on multiple pages. I did not get any error. I'm attaching the
proposal.
Thanks for resubmitting. This is proposal 200720.1:
http://dwarfstd.org/ShowIssue.php?issue=200720.1
--
Michael Eager
___
Dwarf-Discuss mailin
ou need to know the third piece?
How is this different from a non-vector processor doing an optimized
string operation, loading 4 characters into a register at a time? If
the string is nul-terminated, the string length might be unknown.
--
Michael Eager
___
e that it could also be
used for architectures with multiple address spaces, but I'm not aware
of any that do. If anyone knows of another architecture using this
attribute, I'd like to hear about it.
--
Michael Eager
___
Dwarf-Discuss m
We'd also want an unbounded piece operator to describe partially registerized
unbounded arrays, but I have not worked that out in detail, yet, and we're a bit
farther away from an implementation.
Can you describe this more?
--
Michael Eager
___
D
On 7/16/20 5:37 PM, David Blaikie wrote:
On Thu, Jul 16, 2020 at 4:25 PM Michael Eager
The language used to describe segmented addressing in DW_AT_segment
reads to me like the same language used to describe segmented addresses
in debug_aranges - it reads to me like they refer to the same
On 7/16/20 2:57 PM, David Blaikie wrote:
On Thu, Jul 16, 2020 at 2:05 PM Michael Eager
You appear to be starting with a counterfactual premise and using that
to postulate a problem where none exists.
Sorry - I seem to be misunderstanding what you mean by "there are no
restric
On 7/16/20 1:36 PM, David Blaikie wrote:
On Thu, Jul 16, 2020 at 1:07 PM Michael Eager <mailto:ea...@eagercon.com>> wrote:
> Perhaps it's more like Paul was postulating - that the spec
assumes code
> is in a code segment/doesn't need to be clarified.
Again, FORM_addrx doesn't mean the same as DW_AT_segment.
They are orthogonal concepts. Compression techniques, like FORM_addrx,
should not be used to describe architectural features.
--
Michael Eager
___
Dwarf-Discuss mailing list
Dwarf-Discuss@l
resolves the "but debug_addr has segment
selectors"
nor "what's the point of segment selector size in debug_rnglists,
debug_loclists, and debug_line" - none of those sections seem to contain
segment selectors, so why do their headers describe the size of suc
e
of standardization.
--
Michael Eager
___
Dwarf-Discuss mailing list
Dwarf-Discuss@lists.dwarfstd.org
http://lists.dwarfstd.org/listinfo.cgi/dwarf-discuss-dwarfstd.org
lting memory location description wouldn't have an
address-space qualifier.
I found DW_AT_address_class, which allows attaching an integer, which
could represent the address-space. This sounds pretty close. I'm a bit
thrown
ified addresses, although using a typed stack, this could be an
extension.
I found DW_AT_address_class, which allows attaching an integer, which
could represent the address-space. This sounds pretty close. I’m a bit
thrown off by the example, though.
Which example?
--
Michael
On 7/15/20 9:49 PM, David Blaikie wrote:
On Wed, Jul 15, 2020 at 7:07 PM Michael Eager via Dwarf-Discuss
<mailto:dwarf-discuss@lists.dwarfstd.org>> wrote:
Segmented addresses have been in the DWARF specification since
Version 2
and AFAIK have not been changed since
segment size is given by the segment_selector_size field of the
> header, and the address size is given by the address_size field
of the
> header. If the segment_selector_size field in the header is zero, the
> segment selector is omitted from the range list ent
you submit an issue on the
Public Comment page so that we can track it?
http://dwarfstd.org/Comment.php
--
Michael Eager
___
Dwarf-Discuss mailing list
Dwarf-Discuss@lists.dwarfstd.org
http://lists.dwarfstd.org/listinfo.cgi/dwarf-discuss-dwarfstd.org
On 3/23/20 3:58 PM, Cary Coutant via Dwarf-Discuss wrote:
I think that the description has become a bit less clear with the
addition of the Implicit Location Descriptions in Section 2.6.1.1.4,
which do compute values, rather than locations. Perhaps these should
have been described in Section 2.5
On 3/23/20 6:28 AM, Robinson, Paul via Dwarf-Discuss wrote:
From: Dwarf-Discuss On Behalf
Of Adrian Prantl via Dwarf-Discuss
On Mar 19, 2020, at 5:49 PM, Michael Eager via Dwarf-Discuss
disc...@lists.dwarfstd.org> wrote:
My reading of sections 2.5 & 2.6 is that you cannot have a DW_O
do not modify the stack. (See comment page 40.)
Implicit Location Descriptions may only appear in Location Descriptions.
The wording of the text says that the three operations specify a
value, but do not say that this value is pushed on the stack.
--
Michael Eagerea...@eagercon.c
On 2/26/20 1:05 AM, Pavel Labath via Dwarf-Discuss wrote:
The main question on my mind now is, what is the likely future
direction of the DWARF spec -- if say DWARF v6 adds a new section, how
will it handle mixed v5+v6 debug_cu_indexes? I don't think it will
want to make that unsupported (1). I a
ght reduce the surprise
factor. But this depends on neither of the complication 3 cases being
true, and there may be no way to confirm this. This might give the user
an even stronger false impression that the new value is being used, when
it isn't.
--
Michael Eagerea...@eagercon.com
1
onsumer and producer tools to mention whether they have considered
this area, so as to collect a census.
--
Michael Eagerea...@eagerm.com
1960 Park Blvd., Palo Alto, CA 94306
___
Dwarf-Discuss mailing list
Dwarf-Discuss@lists.dwarfstd.org
http://li
istent. (A clear
definition of quiescent would be needed.)
As Cary notes, a default or bounded location description might be used,
but I don't believe that either implies that a variable is quiescent (or
not) over the specified range.
--
Michael E
| Raincode Labs India
Tel: (+91) 080 41159811
Mob: (+91) 9049336744
www.raincodelabs.com <http://www.raincodelabs.com>
-Original Message-
From: Michael Eager
Sent: 08 November 2019 20:04
To: Chirag Patel ; Robinson, Paul
; Ron Brender
Cc: dwarf-discuss@lists.dwarfstd.org
Subje
e from myside.
Regards,
**
*Chirag Patel*
Software Engineer | Raincode Labs India
*Tel*: (+91) 080 41159811
*Mob*: (+91) 9049336744
_www.raincodelabs.com <http://www.raincodelabs.com/>_
linkedin-button <https://in.linkedin.com/in/chirag-patel->
*From:*Chirag Patel
*Sent:
ineer | Raincode Labs India
*Tel*: (+91) 080 41159811
*Mob*: (+91) 9049336744
www.raincodelabs.com <http://www.raincodelabs.com/>__
linkedin-button <https://in.linkedin.com/in/chirag-patel->
_______
Dwarf-Discuss mailing list
Dwarf-D
d the
parse tree, pushing previous values, and popped when ascend the tree.
Almost all architectures, and specifically the ARM and AMD64
architectures you mention, use linear, not segmented, address spaces.
Kind regards,
Jayvee
Am Do., 26. Sept. 2019 um 23:12 Uhr schrieb Michael Eager
mail
s Ron mentioned, AT_segment is intended to support architectures like
the X86 where an address is composed of a [segment,offset] pair. Most
architectures do not use segments.
--
Michael Eagerea...@eagerm.com
1960 Park Blvd., Palo Alto, CA
can look at the DWARF debug info
(using readelf or dwarfdump) and see what is at offset 0x4c4f5254. If
that is not a DIE, then the DWARF generated by clang is incorrect. If
it is a DIE, then dysmutil is confused.
--
Michael Eagerea...@eagerm.com
1960 Park Blvd., Palo
ng your question to
the LLVM/Clang mailing list.
--
Michael Eagerea...@eagerm.com
1960 Park Blvd., Palo Alto, CA 94306
___
Dwarf-Discuss mailing list
Dwarf-Discuss@lists.dwarfstd.org
http://lists.dwarfstd.org/listinfo.cgi/dwarf-discuss-dwarfstd.org
ed this, but not the time during the call.
-cary
--
Michael Eagerea...@eagerm.com
1960 Park Blvd., Palo Alto, CA 94306
___
Dwarf-Discuss mailing list
Dwarf-Discuss@lists.dwarfstd.org
http://lists.dwarfstd.org/listinfo.cgi/dwarf-discuss-dwarfstd.org
the value as live (in a register)
after the call, at PC = 0xf.
--
Michael Eagerea...@eagerm.com
1960 Park Blvd., Palo Alto, CA 94306
___
Dwarf-Discuss mailing list
Dwarf-Discuss@lists.dwarfstd.org
http://lists.dwarfstd.org/listinfo.cgi/dwarf-discuss-dwarfstd.org
On 12/07/2018 08:12 AM, Jakub Jelinek wrote:
On Fri, Dec 07, 2018 at 07:57:23AM -0800, Michael Eager wrote:
On 12/07/2018 04:54 AM, Jakub Jelinek wrote:
On Fri, Dec 07, 2018 at 12:36:39PM +, David Stenberg via Dwarf-Discuss
wrote:
For calls, we need to distinguish the locations that are
rn address is in the called routine, and I know what the PC is
after the return. None of these addresses is in the middle of the call.
Why not generate the label as the next address following the call?
--
Michael Eagerea...@eagerm.com
1960 Park Blvd.,
lq f
f: b8 7b 00 00 00 mov$0x7b,%eax
When debugging the Clang-built binary in GDB, when unwinding from set()
to main(), `local' will be evaluated using the value RAX has in set(),
rather then being printed as "".
Best regards,
David
--
Michael Eagerea...@ea
t works on all architectures.
In any case, this is the way that GDB has handled return addresses
for n >= 2 decades. Whatever the OP's issue is, this is not related.
--
Michael Eagerea...@eagerm.com
1960 Park Blvd., Palo Alto, CA 94306
___
Dwa
e ABI requirements in
the CFI, since this would be duplicated in every CFI entry.
DWARF philosophy is not to duplicate information which is defined
by the ABI or other architecture definitions.
--
Michael Eagerea...@eagercon.com
1960 Park Blvd., Palo Alto, CA 94306
<9e> DW_AT_decl_line : 7
<9f> DW_AT_frame_base : 1 byte block: 6e (DW_OP_reg30
(r30))
This looks odd to me as well.
Looking at the DWARF, I would interpret it to say that foo takes two
arguments, a and b, and bar takes zero arguments. Shouldn't the
DW_TAG_
ddress on the
target machine.
The most common way in which the machine address is provided as the
operand is by generating a relocatable value pointing to the target
address. This is not really a DWARF specification; it is how
relocations work in assemblers and linkers.
--
Michae
On 05/22/2018 04:34 PM, David Anderson wrote:
On 05/22/2018 04:18 PM, Michael Eager wrote:
On 05/22/2018 02:33 PM, David Anderson via Dwarf-Discuss wrote:
I have been given a tiny object file created by armcc
using DWARF and things make no sense to me so far.
dwarfdump (and libdwarf) use
post the output of readelf?
--
Michael Eagerea...@eagercon.com
1960 Park Blvd., Palo Alto, CA 94306
___
Dwarf-Discuss mailing list
Dwarf-Discuss@lists.dwarfstd.org
http://lists.dwarfstd.org/listinfo.cgi/dwarf-discuss-dwarfstd.org
://dwarfstd.org/Issues.php which
describes the situation and your proposed changes to the standard.
--
Michael Eagerea...@eagerm.com
1960 Park Blvd., Palo Alto, CA 94306
___
Dwarf-Discuss mailing list
Dwarf-Discuss@lists.dwarfstd.org
http://lis
=Best_Practices
--
Michael Eagerea...@eagercon.com
1960 Park Blvd., Palo Alto, CA 94306
___
Dwarf-Discuss mailing list
Dwarf-Discuss@lists.dwarfstd.org
http://lists.dwarfstd.org/listinfo.cgi/dwarf-discuss-dwarfstd.org
g that the compiler generates a valid source type. In some
cases, particularly with template classes, this may not be the case.
i.e. If I copy string from DW_AT_name to source code, and compile it
with the same compiler that produced DWARF, will it produce the same type?
T var1;
DW_
this might be used?
On 2018-02-01 17:20, Michael Eager wrote:
On 02/01/2018 12:01 PM, sc...@scottlinder.com wrote:
Hi Paul,
My intention was to support an empty source string; I want to be
explicit about the presence of embedded source for each file.
I'm not fond of the belt and suspe
.org
___
Dwarf-Discuss mailing list
Dwarf-Discuss@lists.dwarfstd.org
http://lists.dwarfstd.org/listinfo.cgi/dwarf-discuss-dwarfstd.org
--
Michael Eagerea...@eagercon.com
1960 Park Blvd., Palo Alto, CA 94306
__
ailing list
Dwarf-Discuss@lists.dwarfstd.org
http://lists.dwarfstd.org/listinfo.cgi/dwarf-discuss-dwarfstd.org
--
Michael Eagerea...@eagercon.com
1960 Park Blvd., Palo Alto, CA 94306
___
Dwarf-Discuss mailing list
Dwarf-Discuss@lists.dwarfstd.org
http://lists.dwarfstd.org/listinfo.cgi/dwarf-discuss-dwarfstd.org
s.dwarfstd.org
http://lists.dwarfstd.org/listinfo.cgi/dwarf-discuss-dwarfstd.org
--
Michael Eagerea...@eagerm.com
1960 Park Blvd., Palo Alto, CA 94306
___
Dwarf-Discuss mailing list
Dwarf-Discuss@lists.dwarfstd.org
http://lists.dwarfstd.org/listinfo.cgi/dwarf-discuss-dwarfstd.org
this attribute
(DW_TAG_hash_value), the attibute value is generated as a hash function
taken over all the compile unit DWARF debug information. Hash function
might be selected as SHA1.
Thanks!
Aleksandr
--
Michael Eagerea...@eagerm.com
1960 Park Blvd., Palo Alto, CA 94306
To: Michael Eager
CC: David Anderson ,
dwarf-discuss@lists.dwarfstd.org
On Wed, Nov 22, 2017 at 03:58:47PM -0800, Michael Eager wrote:
On 11/22/2017 02:17 PM, David Anderson wrote:
>"In general, the structure and content of any
>given concrete inlined instance tree
>will be clo
that do not
exist in the abstract tree.
--
Michael Eagerea...@eagerm.com
1960 Park Blvd., Palo Alto, CA 94306
___
Dwarf-Discuss mailing list
Dwarf-Discuss@lists.dwarfstd.org
http://lists.dwarfstd.org/listinfo.cgi/dwarf-discuss-dwarfstd.org
rement in the DWARF Spec that the concrete and abstract instance
descriptions need to match each other. If not, I think that there
should be.
I'd like to see an example (as Jason mentioned) where abstract and
concrete instances do not match and where this appears to be correct.
I
Hi Folks --
There have been several recent posts to the mailing list which are over 100K
bytes.
Please submit posts in plain text rather than HTML and be judicious about the
amount of backquoting.
--
Michael Eagerea...@eagercon.com
1960 Park Blvd., Palo Alto, CA 94306 650-325-8077
s DWARF v5.
--
Michael Eagerea...@eagercon.com
1960 Park Blvd., Palo Alto, CA 94306 650-325-8077
___
Dwarf-Discuss mailing list
Dwarf-Discuss@lists.dwarfstd.org
http://lists.dwarfstd.org/listinfo.cgi/dwarf-discuss-dwarfstd.org
Alexandre --
I don't know in what way the CAPTCHA "takes control of your computer",
but I'll add your proposals manually.
On 04/27/2017 05:43 PM, Alexandre Oliva wrote:
On Feb 23, 2017, Michael Eager wrote:
Please submit comments/proposals online at http://dwarfstd.
list.
How's this to get the discussion on this extension started?
This is implemented in GCC, GIT branch aoliva/SFN. binutils+gdb branch
users/aoliva/SFN has gas support for '.loc ... view' so as to generate
more compact line number programs than GCC can on its own.
--
Michael Ea
Format or the DWARF
Committee can be directed to the DWARF Committee Chair, Michael Eager at i...@dwarfstd.org.
--
Michael Eagerea...@eagercon.com
1960 Park Blvd., Palo Alto, CA 94306 650-325-8077
___
Dwarf-Discuss mailing list
Dwarf-Discuss
s. Little-endian and big-endian store the bytes
of a register in different orders. Which is unchanged?
--
Michael Eagerea...@eagercon.com
1960 Park Blvd., Palo Alto, CA 94306 650-325-8077
___
Dwarf-Discuss mailing list
Dwarf-Discuss@lists.dwar
not sure which. What happens
if the register is a FP reg? What does it mean to right-shift a floating
point register?
Seems to be way more complicated to me.
--
Michael Eagerea...@eagercon.com
1960 Park Blvd., Palo Alto, CA 94306 650-325-8077
__
o, not what we want.
I think it's also unfortunate that we allowed the offset field for
DW_OP_bit_piece to apply to register values. That's a very different
use for the value, and just adds to the confusion.
It's the same use when a register contains multiple fields of a stru
On 01/27/2017 11:15 AM, Andreas Arnez wrote:
On Fri, Jan 27 2017, Michael Eager wrote:
On 01/27/2017 06:49 AM, Andreas Arnez wrote:
But if some "even less significant" bits were added (such as with
z/Architecture, where a newer release extended 64-bit FP-registers to
128-bit vect
On 01/27/2017 07:19 AM, Andreas Arnez wrote:
On Thu, Jan 26 2017, Michael Eager wrote:
I don't understand the assertion that "most significant" can not be
applied to registers. In the case where a register contains a single
value, this appears to be unambiguous. When a re
On 01/27/2017 06:49 AM, Andreas Arnez wrote:
On Thu, Jan 26 2017, Michael Eager wrote:
On 01/26/2017 11:17 AM, Andreas Arnez wrote:
Exactly: the current DWARF text*differs* from the usual "defined by the
ABI"-principle when it states for DW_OP_bit_piece: "If the location is
both
big- and litle-endian architectures.
--
Michael Eagerea...@eagercon.com
1960 Park Blvd., Palo Alto, CA 94306 650-325-8077
___
Dwarf-Discuss mailing list
Dwarf-Discuss@lists.dwarfstd.org
http://lists.dwarfstd.org/listinfo.cgi/dwarf-discuss-dwarfstd.org
s this growing a register?) then you would describe the value in the register
with a length of 16 and an offset of 16. Same applies for 32-bit values in
64-bit registers.
--
Michael Eagerea...@eagercon.com
1960 Park Blvd., Palo Alto, CA 94306 650-325-8077
_
isters is similar. When
discussing compound values (such as floating point) it is common to say that
the sign bit is in the most-significant bit of the register, without ambiguity.
So, to answer your question "how do I interpret left and right", in a DWARF
context, I don't, since t
to the draft easier.
Sources for the document will be available on the DWARF website
when the document is finalized.
Generally, when an issue is resolved (either adopted, adopted with
modificaitons, or rejected) comments are added to the issue which
describe the resolution.
--
Michael Eager
;) registers.
This usage is not covered by the current description of DW_OP_piece.
Should it be?
--
Andreas
___
Dwarf-Discuss mailing list
Dwarf-Discuss@lists.dwarfstd.org
http://lists.dwarfstd.org/listinfo.cgi/dwarf-discuss-dwarfstd.org
--
Micha
version will be published. Additional information about
DWARF, including how to subscribe to the DWARF mailing list, can also be found on the website.
Questions about the DWARF Debugging Information Format or the DWARF Committee can be directed to the
DWARF Committee Chair, Michael Eager at i
tc_arc_frame_initial_instructions (void)
{
/* Stack pointer is register 28. */
- cfi_add_CFA_def_cfa_register (28);
+ cfi_add_CFA_def_cfa(28, 0);
}
int
--
Michael Eagerea...@eagercon.com
1960 Park Blvd., Palo Alto, CA 94306 650-325-8077
___
Dwarf-Discuss
er
may be found at a different location, or the end of the CFI.
As an example, if C were to raise an exception and we’d use stack unwinding,
how could the unwinder find the old/callee-saved EDI value?
Look up the value's location as described in the CFI for the PC value.
--
Michael Eager
On 03/09/2016 05:24 PM, Michael Eager wrote:
There are no DWARF expressions involved here. What does the
description of DW_OP_piece have to do with a DWARF description
which doesn't use a DWARF expression?
Oops. There is a DWARF expression in the DW_AT_location.
--
Michael Eager
But we make no
such similar claim for simple register location descriptions. That led
Adrian to wonder if he should be using DW_OP_piece. I think it's an
oversight, easily clarified.
There are no DWARF expressions involved here. What does the
description of DW_OP_piece have to do with a DWARF
On 03/09/2016 11:35 AM, Adrian Prantl wrote:
On Mar 9, 2016, at 8:36 AM, Michael Eager wrote:
On 03/04/2016 01:12 PM, Adrian Prantl wrote:
I have a best-practice kind of question:
The x86_64 System V ABI passes floating point values in the xmm0, xmm1, ...
128-bit SSE vector registers. I’m
On 03/09/2016 11:26 AM, Frank Ch. Eigler wrote:
Hi -
On Wed, Mar 09, 2016 at 11:20:38AM -0800, Michael Eager wrote:
[...]
Variable definitions describe where the variable is defined.
If the size of the variable is different from the size of
the container, it should be described as such.
This
base type explicitly describes the size of the type and the
size of its container.
Type representations such as "integer" or "float" are attributes of the
base type, and are orthogonal to descriptions of where the variable
is allocated.
--
Michael Eagerea...@eagercon.com
1
On 03/09/2016 10:00 AM, David Blaikie wrote:
On Wed, Mar 9, 2016 at 9:57 AM, Michael Eager mailto:ea...@eagercon.com>> wrote:
On 03/09/2016 09:33 AM, Jakub Jelinek wrote:
On Wed, Mar 09, 2016 at 08:36:44AM -0800, Michael Eager wrote:
How is the "float"
On 03/09/2016 09:33 AM, Jakub Jelinek wrote:
On Wed, Mar 09, 2016 at 08:36:44AM -0800, Michael Eager wrote:
How is the "float" type described?
A value which is contained in a register larger than the size of
the value should be described by a DW_TAG_base_type. (DWARF 4,
Sect. 5.1,
DW_AT_byte_size 16
DW_AT_bit_size 32
DW_AT_data_bit_offset 0
Note that there is no requirement that the names on base types
be unique. There may be more than one with the name "float".
--
Michael Eagerea...@eagercon.com
1960 Park Blvd., Palo Alto, CA 94306 650-325-8077
___
1 - 100 of 158 matches
Mail list logo
