Displaying 5 results from an estimated 5 matches for "_param".
Did you mean:
param
2018 Jul 25
2
A question to the DWARF experts on symbol indirection
...Re: [llvm-dev] A question to the DWARF experts on symbol
> indirection
>
> Hi Nat!,
>
> On Wed, 25 Jul 2018 at 01:21, Nat! via llvm-dev <llvm-dev at lists.llvm.org>
> wrote:
> > Is it possible to emit DWARF statements, so that in the debugger the
> > parameter _param is hidden and the visibility is a and b, without a
> _param-> prefix ?
>
> It's certainly possible in LLVM IR. @llvm.dbg.declare and so on can
> associate arbitrary Values in a function with whatever name you want.
DWARF expressions are certainly powerful enough to describe thi...
2018 Jul 25
3
A question to the DWARF experts on symbol indirection
It would be great if some DWARF expert could weigh in on this, since my
understanding on DWARF is rudimentary.
Let's say I have a C function defined as
struct ab
{
int a;
int b;
};
void fooWithAb( struct ab *_param)
{
}
Is it possible to emit DWARF statements, so that in the debugger the
parameter
_param is hidden and the visibility is a and b, without a _param-> prefix ?
Ciao
Nat!
Why I need this:
https://www.mulle-kybernetik.com/weblog/2015/mulle_objc_meta_call_convention.html
2018 May 19
2
tbaa error: Access type node must be a valid scalar type
Hi
I am upgrading my clang fork from 5.0 to 6.0 and I am hit by this error:
Access type node must be a valid scalar type
%4 = load %"struct.Foo::p.test1::"*, %"struct.Foo::p.test1::"**
%_param.addr, align 8, !tbaa !16
!16 = !{!15, !15, i64 0}
!15 = !{!"p.test1::", !13, i64 0, !13, i64 8}
It looks like !16 is referencing !15, which is a struct. !13 is
!13 = !{!"any pointer", !8, i64 0}
But the %4 instruction just deals with pointers, so why is there a
problem ? The...
2012 Aug 10
18
[PATCH v2 0/5] ARM hypercall ABI: 64 bit ready
Hi all,
this patch series makes the necessary changes to make sure that the
current ARM hypercall ABI can be used as-is on 64 bit ARM platforms:
- it defines xen_ulong_t as uint64_t on ARM;
- it introduces a new macro to handle guest pointers, called
XEN_GUEST_HANDLE_PARAM (that has size 4 bytes on aarch and is going to
have size 8 bytes on aarch64);
- it replaces all the occurrences of XEN_GUEST_HANDLE in hypercall
parameters with XEN_GUEST_HANDLE_PARAM.
On x86 and ia64 things should stay exactly the same.
On ARM all the unsigned long and the guest pointers that...
2013 Sep 23
57
[PATCH RFC v13 00/20] Introduce PVH domU support
...el code for PVH guests can be found here:
git://oss.oracle.com/git/mrathor/linux.git pvh.v9-muk-1
(That repo/branch also contains a config file, pvh-config-file)
Changes in v13 can be found inline; major changes since v12 include:
* Include Mukesh''s toolstack patches (v4)
* Allocate hvm_param struct for PVH domains; remove patch disabling
memevents
For those who have been following the series as it develops, here is a
summary of the major changes from Mukesh''s series (v11->v12):
* Introduction of "has_hvm_container_*()" macros, rather than using
"!is_pv_...