similar to: [LLVMdev] comments on Bug 1521 (Revamp LLVM by-value structure passing)

> > 2) add a "byref" mark in the pointer argument. > > I think you mean "bycopy" or "byval" here. Yes, good catch. > > 3) Have llvm-gcc create a copy before calling the function. > > Don't forget that the function may be called by code that > was not compiled by LLVM. That's why we have to pay attention > to the ABI! Solution

Hi Rafael, > 2) add a "byref" mark in the pointer argument. I think you mean "bycopy" or "byval" here. > 3) Have llvm-gcc create a copy before calling the function. Don't forget that the function may be called by code that was not compiled by LLVM. That's why we have to pay attention to the ABI! Solution (3) supposes we have control over both

On Fri, 3 Aug 2007, Rafael Espindola wrote: > Sorry for the delay. I am back from a vacation and have been busy > catching up.... Welcome back :) > That is why I need the types (just for the size). This is necessary to > implement both the current behavior and the correct ABI. Right. > consider the llvm code > --------------------------------------- > %struct.s = type {

On 27/07/07, Evan Cheng <evan.cheng at apple.com> wrote: > Code generator shouldn't introspect the LLVM type at all, except to > get the size of the type. Anything needed should be encoded by the > front-end. In the short term, please focus on getting parity with > what we already have. This means x86-64 will be wrong, but it > already is. As a second step we can then

At the LLVM Developers' Meeting in November, I promised to work on isolating a subset of the current test suite that is useful for benchmarking. Having looked at this in more detail, most of the applications and benchmarks in the test suite are useful for benchmarking, and so I think that a better way of phrasing it is that we should construct a list of programs in the test suite that are not

Hi everybody! I recently started using llvm in a project on inferring additional information about pointers based on their types, casts, etc. The following simple example is giving me a headache :): typedef struct { int a; short b, c; int d, e, f; } foo; void bar(foo f) { short s; s = f.b; } int main(void) { foo p; bar(p); } Because llvm doesn't allow structures and arrays

https://bugs.freedesktop.org/show_bug.cgi?id=95251 Bug ID: 95251 Summary: vdpau decoder capabilities: not supported Product: Mesa Version: 11.2 Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/nouveau Assignee: nouveau at

Hi all, I have been looking at how to convert by-reference captures into by-copy captures for captured statements and possibly C++ lambdas, and am looking for some feedback on my approach. The motivation for trying to use copy captures is to avoid unnecessary loads that are otherwise required inside the outlined function. This can be important when the outlined function represents the body of a

Hi Folks, We've now reconnected the newgroup comp.emulators.ms-windows.wine to the wine-users mailing list, so they are, in theory, one 'virtual' community. We also revamped the web site a bit to try to make these things pop out a bit more. Please see this page in particular: http://www.winehq.org/site/getting_help Hopefully this will help people find a way to search for help and

On Mon, Jul 25, 2016 at 05:47:05PM +0200, Pino Toscano wrote: > + if (path == NULL) > + path = "/usr/share/osinfo"; I wonder if we should use $prefix here. I guess there are arguments both ways. Should we just run the external osinfo-query program? Anyway it's fine as it stands, so ACK. Rich. -- Richard Jones, Virtualization Group, Red Hat

Newer versions do not have the 24px distributor.png icon; OTOH they have the 48px version, so look for that one before the 24px one. Also, bump the size limit to 10K, as newer versions of the icon are bigger than 3K. --- lib/inspect-icon.c | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/lib/inspect-icon.c b/lib/inspect-icon.c index 0cc8e92ad..623591aa6 100644 ---

It turns out that a) the standalone pep8 executable is deprecated in favour of pycodestyle b) $python-pep8 does not exist in modern distros and thus the style checks for Python scripts have been skipped for a long time. Instead, switch to pycodestyle directly, updating the list of ignored issues to the two categories left. --- config.sh.in | 1 + m4/guestfs-progs.m4 |

The existing implementation admitted that it was not very robust in the face of garbage input (including, but not limited to, the the fact that the scanf() family has undefined behavior on integer overflow). Tighten things up by reimplementing the function. The old comment mentioned the 'human*' interface from gnulib; we can't use that for licensing reasons; so my rewrite is done

In order to the code generators to lower functions arguments that have the "byval" attribute, they would have to access the original argument Type. For example, on linux x86_64 {i64, i64} should be passed on registers and {i64, i64, i64} goes on the stack. The problem is that when looking at (for example) FORMAL_ARGUMENTS, the only thing that is present is the type of the pointer itself

More recent versions of libosinfo switched the internal directory with the XML files of OSes to a different layout (still with the same XML format), causing libguestfs to not read them anymore. Furthermore, the internal directory is going to disappear soon, replaced by a public osinfo database [1]. Revamp the way libguestfs reads the data: first try the upcoming osinfo layout, falling back to

Hi there, I have searched what seems like everywhere and was unable to find a .NET wrapper so that I can use speex in VB. I did find a speex.NET.dll but this didn't seem to work on what I needed. I therefore decided I could just use DllImport within VB .NET and create my own unmanaged links to libspeex.dll. With the help of this partial c# code

The existing implementation admitted that it was not very robust in the face of garbage input; tighten things up by reimplementing the function, and add testsuite coverage to ensure further tweaks do not break things. The testsuite additions were interesting - we didn't have any easy way to link against a subset of the src/ files (all previous uses of the util functions have been through

There appears to be a difference between passing by value:     call void @foo(%some_struct %v) And using the `byval` attribute on a pointer:     call void @foo(%some_struct* byval %v) They are not compatible with each other yet logically do the same thing.  The second form is the one that appears to work with the ABI on linux, and the first one not. What is the reason for the difference? --

Hi All, I was debugging a clang binary when i found this problem. The following code is complied with clang. typedef struct s { short s; } SVAL; void recurse (SVAL a, int depth) { a.s = --depth; if (depth == 0) return; else recurse(a,depth); } int main () { SVAL s; s.s = 5; recurse (s, 5); return 0; } When i try to access value of a.s in function recurse through gdb(i.e

Hi David, I think it might not be exactly PR13303 which might be causing the corruption of struct when accessed through GDB. This seems to be an ABI problem in clang. The problem seems to be that when we have pass by value of struct (having indirect arguments) stack is not aligned properly. I tried realigning the stack for indirect arguments in(TargetInfo.cpp) - ABIArgInfo