similar to: Global Variables Scope

`memset(&mc_ext, 0, ...)'' leads to a buffer overflow and a subsequent null pointer dereference. Replace `&mc_ext'' with `mc_ext''. Signed-off-by: Xi Wang <xi@mit.edu> --- xen/arch/x86/cpu/mcheck/mce_intel.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/xen/arch/x86/cpu/mcheck/mce_intel.c b/xen/arch/x86/cpu/mcheck/mce_intel.c index

file://docs/LangRef.html#globalvars The section describing the definition of global vars discusses that you can specify an alignment and can also specify a section. Could someone provide an example that works in gccas in release 1.9 for both defining which section the var is assigned to and defining the variables alignment? Also, is there another document that describes how you define sections

On Thu, 11 Jan 2007, Schimmel, Mark wrote: > file://docs/LangRef.html#globalvars > > The section describing the definition of global vars discusses that you > can specify an alignment and can also specify a section. Could someone > provide an example that works in gccas in release 1.9 for both defining > which section the var is assigned to and defining the variables >

Hi Keno, Could you give a short high-level overview of the way Julia works now with MCJIT instead the JIT: What I gather so far... * Compiled IR functions are emitted to a shadow module. * Any used function is cloned into its own new module and the module is added to MCJIT. * Called functions or globalvars are only declared in that module. * Modules are never removed meaning "old"

Does anyone have any good ideas to verify that the layout of a struct from the front end (field offsets and alignment) exactly match LLVM's interpretation of that struct? I want to support packing of structs and pragmas/attributes for alignment and validate that the front end and back end match. [ This is a different front end (ie. Not GNU based). ] For example: __packed struct S1 { char

On Mon, 21 Jun 2004, Vladimir Merzliakov wrote: > Is it ok sending this results for FreeBSD5.1 at daily/weekly based to this > mail list? A better list for it would be the llvmbugs list for now. I beginning to think that we need a new test results mailing list. We have 3 instances of the nightly tester going now (x86/linux, sparc, ppc) and may have more in the future. The nightly tester

Is it ok sending this results for FreeBSD5.1 at daily/weekly based to this mail list? Now results. Big improvement in llvm tests results from last test result sended. New regressions: Regression.Assembler.ConstantExprFold : FAIL , expected PASS Regression.CodeGen.Generic.2004-04-09-SameValueCoalescing: FAIL , expected PASS Regression.Transforms.PRE.basictest : FAIL

> thanks for your reply. Sorry for the delay, I've been buried in email lately. >>> When translating a complex c application to llvm bytecodes, some >>> semantics are lost: >>> >> LLVM 1.6 and the "new front-end" already handle this right. Here's the >> bugzilla bug corresponding to it: >>

Hi I am wondering why the following variable has a PointerTy. @foo.data = internal addrspace(3) global float 5.000000e+000, align 4 When I do a V->getType()->dump() on the variable its printed as float addrspace(3)* thanks shrey

Is it possible to use address of function in case block of switch instruction? I understand that it should be constants only, but in llvm reference i founded that: "The addresses of global variables and functions are always implicitly valid (link-time) constants. " Yours sincerely, Kadysev Mikhail -------------- next part -------------- An HTML attachment was scrubbed... URL:

In the maps library, NA's are inserted between polygons so lines() can be used to draw all polygons at once. The code to do it is like this: *x++ = NA_REAL; *y++ = NA_REAL; where x and y are declared as double *x, *y, *range; and are the arguments passed in through a .C call. However, the values show up in R as -6.62314033633867e-229 instead of NA, so the

Hello, I'm developing a C compiler for a machine with different local memories, for which I need to be able to specify in which specific memory a global variable should be allocated, and I also need to generate different instructions for accessing different local memories. I've seen in the LLVM 2.2 release notes that there is now support for multiple address spaces, that seem to

Hi Everyone, If you're JITing with LLVM and haven't made the switch to MCJIT already, now is the time. As per discussions on the mailing list and at the last dev meeting, LLVM 3.5 will be the last release to support the old JIT infrastructure. Now that LLVM 3.5 has branched, we plan to start removing the old JIT from the mainline. If you're looking for help in making the switch, Andy

Thanks Vladimir. That's great! Glad you got it working. BTW, the failures you're seeing have been experienced by Chris and I as well. Chris is diligently working on making the LLVM processing more consistent so he track down the problem. A week ago or so, these tests passed at 100%. Reid. On Sun, 2004-06-20 at 15:50, Vladimir Merzliakov wrote: > In attached file. > > Vladimir

In attached file. Vladimir -------------- next part -------------- A non-text attachment was scrubbed... Name: test2004_06_20.log Type: application/octet-stream Size: 88488 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20040620/98042f01/attachment.obj>

hi Chris! thanks for your reply. First of all I did not know about the history with the Annotation stuff. Annotable for me was a way how one could realize this things. So as I see it right now - it is more that Annotable will completly vanish soon. This is interesting to me. Chris Lattner schrieb: > On Fri, 24 Feb 2006, Jakob Praher wrote: > >> When translating a complex c