search for: stackbased

Displaying 11 results from an estimated 11 matches for "stackbased".

Did you mean: stackbase
2013 Jul 25
4
[LLVMdev] Proposing a new 'alloca' parameter attribute to implement the Microsoft C++ ABI
Hi LLVM folks, To properly implement pass-by-value in the Microsoft C++ ABI, we need to be able to take the address of an outgoing call argument slot. This is http://llvm.org/PR5064 . Problem ------- On Windows, C structs are pushed right onto the stack in line with the other arguments. In LLVM, we use byval to model this, and it works for C structs. However, C++ records are also passed this
2013 Oct 22
1
[LLVMdev] Starting implementation of 'inalloca' parameter attribute for MS C++ ABI pass-by-value
I wanted to mention that I'm planning to start writing and sending out patches for this. Naming the attribute 'alloca' was really confusing, so I'd like to change it to 'inalloca', which follows the preposition pattern of inreg and byval. After discussion, we decided it was silly to add stackbase uses to alloca instructions. They should stay simple. Instead, we'll
2013 Jul 30
0
[LLVMdev] Proposing a new 'alloca' parameter attribute to implement the Microsoft C++ ABI
How do you handle this during codegen? One problem is avoid stack changes (like spills). Another is coordinating things that are using allocas and those that are not but end up in the stack. Consider void foo(int arg1, int arg2, int arg3, ....CXXTypeWithCopyConstructor argn, int argp1...) You will need an alloca for argn, but the ABI also requires it to be next to the plain integers that
2008 Nov 21
1
[LLVMdev] Simple stack machine
...for this (possibly very much tuned to LLVM). Of course, that would also mean building an LLVM backend. I guess having a very simple backend would also server LLVM well, as an example backend and one to base new architectures on. Now, on to my real question. Is there any LLVM backend for a (simple) stackbased machine? Anyone working on something like this? Anything we can use (either directly, or as an example and/or to get an idea how much work would be involved)? Gr. Matthijs -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signa...
2013 Jul 30
1
[LLVMdev] Proposing a new 'alloca' parameter attribute to implement the Microsoft C++ ABI
On Tue, Jul 30, 2013 at 11:07 AM, Rafael EspĂ­ndola < rafael.espindola at gmail.com> wrote: > How do you handle this during codegen? One problem is avoid stack > changes (like spills) I'm not sure I understand your question, but my plan is to basically use a frame pointer when there is a call with an argument using the 'alloca' attribute. It'll be slow but
2013 Jul 29
0
[LLVMdev] Proposing a new 'alloca' parameter attribute to implement the Microsoft C++ ABI
Hi Reid, On 25/07/13 23:38, Reid Kleckner wrote: > Hi LLVM folks, > > To properly implement pass-by-value in the Microsoft C++ ABI, we need to be able > to take the address of an outgoing call argument slot. This is > http://llvm.org/PR5064 . > > Problem > ------- > > On Windows, C structs are pushed right onto the stack in line with the other > arguments. In
2020 Mar 28
0
[klibc:update-dash] dash: memalloc: Avoid looping in growstackto
Commit-ID: 21ceb151c758eb2384962b9ee8abc33b5bd674e9 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=21ceb151c758eb2384962b9ee8abc33b5bd674e9 Author: Herbert Xu <herbert at gondor.apana.org.au> AuthorDate: Thu, 31 May 2018 01:51:48 +0800 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Sat, 28 Mar 2020 21:42:55 +0000 [klibc] dash: memalloc: Avoid
2011 Nov 30
1
[PATCH] [MEMALLOC] remove unused variable
Since commit 6ee30a14afac681adb1d62361ebcb0c9b6ba3153 ([klibc] [MEMALLOC] Add pushstackmark), the 'oldstackp' local variable has been unused. This change deletes the unused variable. Signed-off-by: Greg Thelen <gthelen at google.com> --- usr/dash/memalloc.c | 2 -- 1 files changed, 0 insertions(+), 2 deletions(-) diff --git a/usr/dash/memalloc.c b/usr/dash/memalloc.c index
2012 Jul 02
0
[klibc:master] [MEMALLOC] Avoid gcc warning: variable ' oldstackp' set but not used
Commit-ID: cf9ea962f1fb310a92efd184f14df2c04b30f75a Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=cf9ea962f1fb310a92efd184f14df2c04b30f75a Author: Jim Meyering <meyering at redhat.com> AuthorDate: Fri, 8 Jul 2011 16:12:20 +0800 Committer: maximilian attems <max at stro.at> CommitDate: Mon, 2 Jul 2012 10:44:23 +0200 [klibc] [MEMALLOC] Avoid gcc warning:
2018 May 11
0
Wine release 3.8
The Wine development release 3.8 is now available. What's new in this release (see below for details): - Infrastructure for writing kernel driver tests. - Support for showing file properties in the Shell browser. - MP3 decoder as a DirectX Media Object. - More support for the Task Scheduler. - Support for COM aggregation in UrlMon. - Various bug fixes. The source is available
2013 Oct 26
2
[PATCH] 1. changes for vdiskadm on illumos based platform
2. update ZFS in libfsimage from illumos for pygrub diff -r 7c12aaa128e3 -r c2e11847cac0 tools/libfsimage/Rules.mk --- a/tools/libfsimage/Rules.mk Thu Oct 24 22:46:20 2013 +0100 +++ b/tools/libfsimage/Rules.mk Sat Oct 26 20:03:06 2013 +0400 @@ -2,11 +2,19 @@ include $(XEN_ROOT)/tools/Rules.mk CFLAGS += -Wno-unknown-pragmas -I$(XEN_ROOT)/tools/libfsimage/common/