search for: const_

...ough. Is this what you're in > contact with Gabor? > > -Chris > I agree with Chris, that auto-dereferencing is a bad thing (esp. because of the gothcas I detailed). I checked in a bunch of fixes to remove auto-dereferencing. Maybe we should get rid of the type simplifier for (const_) use_iterator? Sabre what do you think? There is one thing that is still irritating me: dyn_cast_or_null and cast_or_null have different interfaces. Should these be made consistent? Cheers, Gabor -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://list...

...in contact with Gabor? >> >> -Chris >> > > I agree with Chris, that auto-dereferencing is a bad thing (esp. because of the gothcas I detailed). > I checked in a bunch of fixes to remove auto-dereferencing. > > Maybe we should get rid of the type simplifier for (const_)use_iterator? Sabre what do you think? Sounds great to me! > There is one thing that is still irritating me: > dyn_cast_or_null and cast_or_null have different interfaces. Should these be made consistent? What do you mean? -Chris -------------- next part -------------- An HTML attachmen...

...alue), but got further problems and had to >> add a specialization >> >> +template<typename From> struct simplify_type<From*const> { >> + typedef From* SimpleType; >> + static SimpleType &getSimplifiedValue(From*const &Val) { >> + return const_cast<From*&>(Val); >> + } >> +}; >> >> Is there a simpler way to accomplish this? >> >> Cheers, >> >> Gabor >> _______________________________________________ >> LLVM Developers mailing list >> LLVMdev at cs.uiuc....

...erval has been backed off to 600 seconds I have tried running dispatch.fcgi from the command line, as I''ve seen it suggested, in order to attempt to debug the problem. I get the following error: c:/ruby/lib/ruby/gems/1.8/gems/activesupport-1.2.5/lib/active_support/dependencies.rb:200:in `const_ missing'': uninitialized constant RailsFCGIHandler (NameError) from ./dispatch.fcgi:24 The shebang line for dispatch.fcgi is #!c:/ruby/bin/ruby which is the correct location of the interpreter. I hope the problem is that I overlooked something trivial - and if that''s th...

...t;>> -Chris >>> >> >> I agree with Chris, that auto-dereferencing is a bad thing (esp. >> because of the gothcas I detailed). >> I checked in a bunch of fixes to remove auto-dereferencing. >> >> Maybe we should get rid of the type simplifier for (const_) >> use_iterator? Sabre what do you think? > > Sounds great to me! Okay, soon :-) > > >> There is one thing that is still irritating me: >> dyn_cast_or_null and cast_or_null have different interfaces. >> Should these be made consistent? > > What do you...

...xen-4.2.1/debian/build/build-hypervisor_amd64_amd64/xen/include/xen/hypercall.h:9, from memory.c:3: memory.c: In function 'compat_memory_op': /tmp/xen-4.2.1/debian/build/build-hypervisor_amd64_amd64/xen/include/public/arch-x86/xen.h:35:33: error: typedef '__guest_handle_const_compat_memory_exchange_t' locally defined but not used [-Werror=unused-local-typedefs] typedef struct { type *p; } __guest_handle_ ## name ^ /tmp/xen-4.2.1/debian/build/build-hypervisor_amd64_amd64/xen/include/public/arch-x86/xen.h:43:5: note: in expansion o...

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

On Oct 15, 2008, at 6:29 PM, Mike Stump wrote: > On Oct 15, 2008, at 1:09 PM, David Vandevoorde wrote: >> On Oct 15, 2008, at 3:53 PM, Mike Stump wrote: >> [...] >>> Objects are defined like so: >>> >>> Two pointers of >>> the same type compare equal if and only if they are both null, >>> both >>> point to the same object or

On Oct 15, 2008, at 1:09 PM, David Vandevoorde wrote: > On Oct 15, 2008, at 3:53 PM, Mike Stump wrote: > [...] >> Objects are defined like so: >> >> Two pointers of >> the same type compare equal if and only if they are both null, >> both >> point to the same object or function, or both point one past the >> end >> of the same array.

hi, my friends: Currently, i am studying the way of hypercall's implementation. i have already known the flow of hypercall's execuation, and i decided to add a new hypercall into the Xen. first, i want to know the detail of one hypercall function, for example, "do_xen_version", but i can not find the location of definition of "do_xen_version". who can help me? i have

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

Hello everyone, this is the fourth version of the patch series that introduces ARMv7 with virtualization extensions support in Xen. The series allows Xen and Dom0 to boot on a Cortex-A15 based Versatile Express simulator. See the following announce email for more informations about what we are trying to achieve, as well as the original git history: See

Hello everyone, this is the very first version of the patch series that introduces ARMv7 with virtualization extensions support in Xen. The series allows Xen and Dom0 to boot on a Cortex-A15 based Versatile Express simulator. See the following announce email for more informations about what we are trying to achieve, as well as the original git history: See