similar to: [LLVMdev] seeking advice

As an aside, is there any reason for why C++-style comments were used in C files at all, or should they simply be replaced with the usual /* ... */ in accordance with pre-C99 standards? In the latter case, would there be any objection to it if I were to make a patch for this? While the change itself would be trivial, I don't yet have any experience with making patches, and so for that purpose

While doing a make on the recently checkout version: I got the following errors: [ 68%] Built target dd [ 68%] Built target compiler-rt-headers [ 68%] Building C object projects/compiler-rt/lib/builtins/CMakeFiles/clang_rt.builtins-x86_64.dir/x86_64/floatdidf.c.o In file included from /home/tthtlc/llvm/llvm/projects/compiler-rt/lib/builtins/x86_64/floatdidf.c:9:0:

Hello, I'm generating C code (and the resulting obj files) using llvm 3.4 for both unix and windows. And I use the dreaded weak references, that, for windows, are not too widely supported. When I link my application on linux, I have no issue. But when I'm doing the same on windows using mingw I got a duplicate symbol error :

Thanks for your clear answer. Do you know what modifier should I use to declare such weak symbols in my llvm intermediate code? So that it can be compiled to the .o file with the weak attribute ? Le 10 févr. 2014 19:44, "Reid Kleckner" <rnk at google.com> a écrit : > COFF doesn't support the same kind of concept of 'weak' that ELF does. > This is the issue that

So instead of using linkagetypes.weak I should use externalweaklinkage ? Le 11 févr. 2014 18:29, "Reid Kleckner" <rnk at google.com> a écrit : > You'd have to use extern_weak linkage. Clang compiles the foo declaration > to: > $ clang -cc1 -emit-llvm -o - t.c | grep declare.*@foo > declare extern_weak i32 @foo(...) #1 > > > > On Tue, Feb 11, 2014 at

I think we have located the revision which fixes this regression: r206094 (or commit 6bb00df in llvm-mirror on GitHub). I have attached a patch which can be applied to the current release_34 branch (tested against the release_34 branch in llvm-mirror). With this patch the attached reg-alloc-test.ll file doesn't fail with the "LLVM ERROR: ran out of registers during register

Yep, quite right, Evan. Any regalloc differences due to that patch are purely coincidence; -Jim > On Jun 16, 2014, at 10:13 AM, Evan Cheng <evan.cheng at apple.com> wrote: > > Hi Niklas, > > The attached patch has nothing to do with register allocation. r206094 changes how cpu auto-detection is done. I believe it's now the responsibility of the tools (e.g. llc) to

summary: I can display a lon-lat map on a lattice::layerplot, and I can display a Lambert conformal conic (LCC) map on a spam::image, but I can't display an LCC map on a lattice::layerplot. Example follows. What am I doing wrong? details: I've been using `lattice` (via `rasterVis`) successfully to display global atmospheric data, which works well enough (though I am definitely intrigued

Hi everyone, llvm is great! But there is one exception ;) llvm components are generally fast, but instruction selection is slooow. Let me explain. I am developing a toolkit for building virtual machines which can automatically generate a JIT compiler using the interpreter specification. llvm does the hard work of machine code generation. (Thanks to you all) I discovered that JIT compilation is

Hi, The RoboVM project recently upgraded from LLVM 3.3 to 3.4 and with the new version we are sometimes seeing "ran out of registers during register allocation" errors when targeting x86 32-bit that we haven't seen before. Nothing has changed in our bitcode generator. I have attached an IR file which can be used to reproduce this problem. The problem occurs with -O2 and

Hello, I'm new to OGG and I must say than it's impressive. I plan to use it in my project (BASIC programming langage) but I use LccWin32 as main C compiler (free and very powerful) and OGG has some difficulties to compile. I would like to know if it was already reported. If not, here it is: - Inline ASM functions for vorbis_itoa() isn't ok for LCC (not the same syntax than VC). I

Hello, I'd like to upstream our work over the time which the community would benefit from. This is a part of effort toward minimizing code size presented in here <https://llvm.org/devmtg/2020-02-23/slides/Kyungwoo-GlobalMachineOutlinerForThinLTO.pdf>. In particular, this RFC is about optimizing prolog and epilog for size. *Homogeneous Prolog and Epilog for Size Optimization, D76570

Hi All, I have a netcdf gridded file with LCC projection. I can easily use image.plot to visualize it. However, as the axises are in X,Y, not Lat and Lon, I could not add state or country maps onto it (or lat lon information). I do have a grid2d file that describes the lat and lon for each (X,Y) grid, but the lat and lon are not regularly spaced, so I could not use image.plot. Does anyone know

SUMMARY: Specific problem: I'm regridding biomass-burning emissions from a global/unprojected inventory to a regional projection (LCC over North America). I need to have boundaries for Canada, Mexico, and US (including US states), but also Caribbean and Atlantic nations (notably the Bahamas). I would also like to add Canadian provinces and Mexican states. How to put these together? General

Hi Vedant, Thanks for your interest and comment. Size-optimization improves page-faults and a start-up time for a large application, which this enabling also followed. Even though I didn't see a large regression/complaint on a CPU-bound case, which is not a typical case for mobile workload, I wanted to be precautious of enabling it by default. However, as with default outlining case, I

Hi List, maybe i missed a hint on google, but i didn?t find a answer to following question: is it possible to cascade the logon scripts...? for example: there is a standard script for all client-pc?s called: netlogon.bat and in addition there is for some client-pc?s a additional script called by the %m switch in smb.conf kind regards Arno

*[qali at qali llvm-2.8-rev]$ find . -exec grep -n "LLVMCC_EMITIR_FLAG" ./ {} \;* ./projects/test-suite/Makefile.tests:47: -$(LCC) $(CPPFLAGS) $(CFLAGS) $(LOPTFLAGS) $(X_TARGET_FLAGS) -S $< -o $@ $(LLVMCC_EMITIR_FLAG) ./projects/test-suite/Makefile.tests:51: -$(LCXX) $(CPPFLAGS) $(CXXFLAGS) $(LOPTFLAGS) $(X_TARGET_FLAGS) -S $< -o $@ $(LLVMCC_EMITIR_FLAG)

Documentation and other bugs with postscript(): 1. This code crashes R (it asks for a font that isn't there): postscript() plot(0:1,0:1) text(0.5,0.5,'crash',font=6) The bug appears to be in the FixupFont routine in plot.c; on line 236, it checks that the font number is in the range 1..32. Later this crashes PostScriptStringWidth in devPS.c, because only fonts numbered 1..5

Hi all, I'm using dovecot 1.0 RC24 compiled form source on a OpenBSD 4.0, I use IMAP service with maildir storage and my mail client is Outlook 2003. If the root of the user maildir stay on the BSD filesystem everything is right. If the root of the maildir is mount on an NFS drive on Microsoft Windows 2003 server, I always have the same error when I try to move mail (under Outlook) form my

Hi James, I also think that refactoring the code generation part is a great idea. That code is very complicated and difficult to maintain. I’ve wanted to rewrite that code for a long time, but just have never got to it. There are quite a few edge cases to handle (at least in the current code). I’ll take a deeper look at your patch. The abstractions that you mention, Stage and Block, are good