similar to: [LLVMdev] Is LLVM our answer??

Thanks for writing, Nate! Yikes, I totally missed those MSVS docs--it shows just how large and comprehensive LLVM has become! Thanks for helping clarify MSVS support! On Apr 1, 2011, at 2:03 PM, nate fries wrote: > Hi Andy. > This should be no problem, as long as you don't use MSVC's headers inside your scripted code (you should be able to use MinGW's to accomplish the

I just BFU''ed up to B61 and started to play with IP Instances. I''m having trouble making my zone happy: root at aeon zones$ zoneadm -z testing1 boot zoneadm: zone ''testing1'': WARNING: unable to hold network interface ''skge0''.: Invalid argument root at aeon zones$ dladm show-dev nge0 link: up speed: 100Mb duplex: full

On Thu, Mar 26, 2009 at 8:20 AM, Paul Melis <llvm at assumetheposition.nl> wrote: > Hi, > > Slightly off-topic (as it's not directly about using or developing LLVM): > > http://code.google.com/p/unladen-swallow/wiki/ProjectPlan > > "Our long-term proposal is to replace CPython's custom virtual machine > with a JIT built on top of LLVM, while leaving the

On Tue, 4 Dec 2018 15:53:29 +0100 "L.P.H. van Belle via samba" <samba at lists.samba.org> wrote: > Hai, >   > Just a questions, this might be a bug, might not, but for this one i > need some help. > Setup, debian 9. >   > Member server samba 4.9.3 > AD DC servers samba 4.8.7 >   > Im setting up the member with a very tight firewall, so nothing

With current settings, MSVS links debug version of flac.exe (and other .exe and .dll files) with the release version of libogg_static.lib. MSVS issues a "warning LNK4098: defaultlib 'libcmt.lib' conflicts with use of other libs; use /NODEFAULTLIB:library" What's the reason in this setting? What is better: * to change the settings so that MSVS will link debug .exe files with

Hi, Slightly off-topic (as it's not directly about using or developing LLVM): http://code.google.com/p/unladen-swallow/wiki/ProjectPlan "Our long-term proposal is to replace CPython's custom virtual machine with a JIT built on top of LLVM, while leaving the rest of the Python runtime relatively intact." Just curious, has anyone here heard more about this project? Regards,

MSVS profiler shows that the encoder spends too much time inside format_input() when the input is 24-bit. The attached patch increases encoding speed: FLAC -5: from 27.1 to 24.2 seconds FLAC -8: from 76.2 to 73.1 seconds (MSVS 2010, 32-bit flac.exe, 24-bit stereo input file) For GCC compiles the encoding speed remains the same. I suspect that GCC is smart enough to use strict aliasing rule to

LUG 2013 is being held in San Diego this year, April 15-19. Intel and Aeon Computing are co-sponsoring a Pre-LUG party that first Monday night, Apr 15th. Beer and Lustre, a great combination! We''ll be in the Omni Hotel, the same location as LUG itself, up on the 10th floor, catching up with old Lustre friends and hopefully make some new ones. Please join us! For more information, email

LUG 2013 is being held in San Diego this year, April 15-19. Intel and Aeon Computing are co-sponsoring a Pre-LUG party that first Monday night, Apr 15th. Beer and Lustre, a great combination! We''ll be in the Omni Hotel, the same location as LUG itself, up on the 10th floor, catching up with old Lustre friends and hopefully make some new ones. Please join us! For more information, email

lvqcl wrote: > Why? We can use vsnprintf_s for MSVS, and vsnprintf for MinGW. > > MSVS version of vsnprintf_s is located inside (statically linked) msvcp???.lib > or (dynamically linked) msvcp???.dll. They are part of MSVS runtime, and compatible > with WinXP. So it is safe to use it in FLAC. Oh, ok. I missed this bit. I know so very little about Windows. However, if you compile

Erik de Castro Lopo wrote: >> because MSVS2005 doesn't provide stdint.h. According to MSDN, >> uintptr_t is defined in "STDDEF.H and other include files". > > Does the rest of FLAC actually support those compilers? Yes. I removed this #include and all projects were successfully built with MSVS 2005 Express. > Is it worth > continuing to support them? * At

Ralph Giles wrote: >> With current settings, MSVS links debug version of flac.exe (and other >> .exe and .dll files) with the release version of libogg_static.lib. >> MSVS issues a "warning LNK4098: defaultlib 'libcmt.lib' conflicts with use >> of other libs; use /NODEFAULTLIB:library" > > Sounds like a bug. Debug targets should link to debug builds

When compiling lpc.c for x86-64 architecture MSVS issues warnings: warning C4028: formal parameter _N_ different from declaration because of flac_restrict modifier. This patch suppresses these warnings. -------------- next part -------------- A non-text attachment was scrubbed... Name: lpc-msvs-warnings.patch Type: application/octet-stream Size: 1025 bytes Desc: not available Url :

By default, FLAC requires ogg library. Support of old versions of Visual Studio was removed from libogg code about 2 years ago: https://git.xiph.org/?p=ogg.git;a=commit;h=18c401c6bc8814d06f3ae53ebf5d4399f90871cc libogg 1.3.3 (released 2017-11-07) cannot be built with MSVS 2005/2008 anymore. Are there any developers that want to use libFLAC in their programs and still use Visual Studio 2005 or

SimplifyLibCalls.cpp is no longer part of Transforms\IPO and Transforms\Scalar\SimplifyCFG.cpp is renamed to SimplifyCFG.cpp or something to that effect ( I didn't look up the actual checkins ). Having fixed that, I still can't get through the build: Creating library C:\work\s\llvm\win32\\bin\Win32\Debug/opt.lib and object C:\work\s\llvm\win32\\bin\Win32\Debug/opt.exp 1>opt.obj : error

lvqcl wrote: > Ralph Giles wrote: > > >> With current settings, MSVS links debug version of flac.exe (and other > >> .exe and .dll files) with the release version of libogg_static.lib. > >> MSVS issues a "warning LNK4098: defaultlib 'libcmt.lib' conflicts with use > >> of other libs; use /NODEFAULTLIB:library" > > > > Sounds

I don't like the decision to remove the old VS project files, in my opinion it's better to keep them, marked "not updated anymore". I personnally use VS2013, and the reason I don't want to upgrade is the fact that VS2017 requires online registration to work. I'm pretty sure some users also have valid reasons to keep their old VS. On 2 May 2018 at 14:37, lvqcl

Hugo Beauzée-Luyssen <hugo at beauzee.fr> wrote: > --- > src/share/win_utf8_io/win_utf8_io.c | 9 +++++++++ > 1 file changed, 9 insertions(+) > > diff --git a/src/share/win_utf8_io/win_utf8_io.c > b/src/share/win_utf8_io/win_utf8_io.c > index c61d27f3..1437b41e 100644 > --- a/src/share/win_utf8_io/win_utf8_io.c > +++ b/src/share/win_utf8_io/win_utf8_io.c >

On Tue, Mar 20, 2018 at 08:28:24PM +0000, Olly Betts wrote: > Related to this, the appveyor build is currently failing on git master. > Unfortunately the change at which is started to fail was the addition > of the new "honey" backend, which doesn't narrow things down to a > useful degree. I've disabled honey in these builds for now. This really needs to be

Erik de Castro Lopo wrote: >> MSVS version of vsnprintf_s is located inside (statically linked) msvcp???.lib >> or (dynamically linked) msvcp???.dll. They are part of MSVS runtime, and compatible >> with WinXP. So it is safe to use it in FLAC. > > Oh, ok. I missed this bit. I know so very little about Windows. > > However, if you compile flac on say Win7 using