similar to: Unresolved symbols in compiler-rt

Hello, I was hoping that someone would be able to help me or at least point me in the right direction regarding a problem I am having. I am a new R user, and I've been trying to read tutorials but they haven't been much help to me so far. The problem is relatively simple as I've already created working solutions in Java and Perl, but I need a solution in R as well. I have two text

Hi Jonathan, I'm sorry to bring this up again, and I don't want to beat a dead horse, but I was very surprised by your benchmarks so I took a little closer look. I think what's happening is that it's a little unfair to compare the ARM64 inline assembly to the C code, because looking at the C macros in "fixed_generic.h" for MULT16_32_Q16 and MULT16_32_Q15 you find

Thanks, I look forward to seeing what you find out. BTW, I was wondering if you tried replacing the SIG2WORD16 macro using the vqmovns_s32 intrinsic? I'm sure it would be faster than the C code, but in the grand scheme of things it might not make much difference. On 11/13/2015 12:15 PM, Jonathan Lennox wrote: >> On Nov 13, 2015, at 1:51 PM, John Ridges <jridges at masque.com>

> Err, no it wouldn't. In fact this example you gave only confuses > the matter. ? What do you mean? typedef struct { FLAC__uint32 length; FLAC__byte *entry; } FLAC__StreamMetadata_VorbisComment_Entry; Can you confirm that the entry member is a pointer and not a byte array? In that case: What happens if the compiler expands the size of the structure twice (8=>16 bytes)? I

Hi Gao, Thanks for the extra information... On Wed, Jan 16, 2013 at 1:14 PM, Yunzhong Gao <Yunzhong.Gao at am.sony.com>wrote: > Hi Daniel, > > Nice to meet you. > > My understanding of the Microsoft #pragma comment(lib, ...) semantics is > that > each specified library will be converted into a directive that starts with > "/DEFAULTLIB" in the COFF

Hi Daniel, >> My understanding of the Microsoft #pragma comment(lib, ...) semantics is that >> each specified library will be converted into a directive that starts with >> "/DEFAULTLIB" in the COFF .drectve section. To demonstrate, the following patch >> produces directives that work with Visual Studio 2010 using the now-deprecated >> dependent library

Hello, I have a statistical problem that I am using R for, but I am not making sense of the results. I am trying to use multiple regression to explore which variables (weather conditions) have the greater effect on a local atmospheric variable. The data is taken from a database that has 20391 data points (Z1). A simplified version of the data I'm looking at is given below, but I have a

Hello, All: The "writeFindFn2xls" function in the "sos" package tries to write an Excel file with 3 sheets ('PackageSum2', 'findFn', 'call'). Unfortunately, it is often unable to do this because of configuration problems that are not easy to fix. I've found 3 contributed packages that provide facilities to write Excel files with

Hi Daniel, Nice to meet you. My understanding of the Microsoft #pragma comment(lib, ...) semantics is that each specified library will be converted into a directive that starts with "/DEFAULTLIB" in the COFF .drectve section. To demonstrate, the following patch produces directives that work with Visual Studio 2010 using the now-deprecated dependent library feature (commits r168779 and

Hi All I am having 2 very long character strings (550chars) and I want to put them as expressions together with c(). The problem is that I also get these double-quotes, as seen below in 'fct'. How can I remove these double-quotes? I tried as.name() but it did not work (because of size?). These are creating trouble with subsequent programs, which I tested with strings that for some

On Fri, Mar 15, 2019 at 6:23 AM bd1976 llvm <bd1976llvm at gmail.com> wrote: > > > On Thu, Mar 14, 2019 at 6:43 PM bd1976 llvm <bd1976llvm at gmail.com> wrote: > >> >> >> On Thu, Mar 14, 2019 at 5:58 PM Rui Ueyama <ruiu at google.com> wrote: >> >>> On Thu, Mar 14, 2019 at 9:45 AM bd1976 llvm via llvm-dev < >>> llvm-dev at

Hi all, As I understand there could be issues to edit/create FLAC files in 64-bit due to different structure sizes (data alignment and data structure padding added by 64-bit compilers). I don't know if this have been dealt with before in this list. I suggest the following addition to the headers (understood by most compilers) #pragma pack(push,4) FLAC_structures ... #pragma pack(pop) That

On Thu, Mar 14, 2019 at 5:58 PM Rui Ueyama <ruiu at google.com> wrote: > On Thu, Mar 14, 2019 at 9:45 AM bd1976 llvm via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > >> On Thu, Mar 14, 2019 at 3:32 PM Peter Smith <peter.smith at linaro.org> >> wrote: >> >>> Hello, >>> >>> I've put some comments on the proposal

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

Hello, Iam being to compile speexenc but I have the following error: LINK : warning LNK4098: defaultlib "LIBCMTD" conflicts with use of other libs; use /NODEFAULTLIB:library libspeex.lib(lsp.obj) : error LNK2001: unresolved external symbol _spx_cos Debug/speexenc.exe : fatal error LNK1120: 1 unresolved externals Error executing link.exe. Please, help me Guillaume --- >8 ---- List

Hi all, We plan to add some auto-linking support for Mach-O, and need a scheme for encoding this information in the LLVM IR. We would like the same scheme to be able to support Microsoft's #pragma comment(lib,...) and #pragma comment(library, ...) features eventually. The current proposal is as follows: -- #1. Extend module-level metadata flags (llvm.module.flags) to support two new

On 3/30/2017 9:03 PM, Reid Kleckner via llvm-dev wrote: > On Thu, Mar 30, 2017 at 5:57 PM, Edward Diener via llvm-dev > <llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>> wrote: > > Actually just doing: > > clang++ -c t.cpp -o t.o --target=x86_64-windows-msvc -fmsc-version=1900 > clang++ t.o -o t.exe --target=x86_64-windows-msvc

hi, i hope this is not too "newbie-ish" but i've never programmed with static libs before. i've downloaded the win32sdk and try to build a simple wav->ogg/vorbis encoder, but the linker complained about several redefinitions. environment is visual studio .net 2003 on winxp and a standard mfc-app set up by this project-wizzard that comes with vs.net2003 using the default

--- configure.ac | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/configure.ac b/configure.ac index f52d2c2..e1a6e9b 100644 --- a/configure.ac +++ b/configure.ac @@ -190,7 +190,7 @@ AC_ARG_ENABLE([rtcd], [enable_rtcd=yes]) AC_ARG_ENABLE([intrinsics], - [AS_HELP_STRING([--disable-intrinsics], [Disable intrinsics optimizations for ARM(float) X86(fixed)])],, +

I am following along in http://llvm.org/docs/GettingStartedVS.html with a Hello World bitcode file. I can run the file using the command `lli HelloWorld.bc`, but now I want to link it into an executable file (on windows). The next thing the document says to run is `llc -filetype=obj HelloWorld.bc` which runs fine and now I have a `HelloWorld.obj` file. It's the last step that is giving me some