search for: _compiler

Displaying 10 results from an estimated 10 matches for "_compiler".

Did you mean: compiler
2015 Nov 19
2
[PATCH] [CMAKE] Allow a toolchain file for the host when cross-compiling
The current behavior is to not specify any toolchain and invoke CMake without additional arguments for configuring the NATIVE portion of the build. However, CMake will actually set the CC, CXX, and FC environment variables to full paths of the compilers in the CMAKE_{C,CXX,Fortran}_COMPILER CMake variables inside the CMake process. This results in those variables being propagated to any execute_process calls so without explicitly providing a separate toolchain file, the configure step for the NATIVE host will pick up the compilers used by the cross-compile toolchain intended for the t...
2017 May 03
3
Runtime-configurable LLVM_DEFAULT_TARGET_TRIPLE by env var
...cache whenever the tree is built before lit. - Almost all compilation units will hit ccache except for Host.cpp when the tree is built with different LLVM_DEFAULT_TARGET_TRIPLE. FYI, I am doing a trick to let ccache recognize compilation units identical for build.ninja; $ sed -i -r 's=(-I|_COMPILER\S* )/home/bb/\w[^/]*/llvm-project=\1../llvm-project=g' build.ninja In other words, testing builders have almost same build except for Host.cpp. I have to build the tree for each testing target. I propose an option to override LLVM_DEFAULT_TARGET_TRIPLE in run-time. The change will be small bu...
2013 Jan 10
2
[LLVMdev] Using C++'11 language features in LLVM itself
...entire project. This > is especially crucial in HPC applications, where you may want to use LLVM > to compile a domain-specific language and the compiler is part of a larger > project that you want to compile using a vendor compiler for performance > reasons. > In LLVM+platform_C++_compiler scenario the safest way would be to use no C++11 features in LLVM at all and just keep the status quo. > >> >> Clang is good enough to bootstrap itself on practically >> any platform I can think of or it can be cross-bootstrapped >> if needed. >> > > Being...
2013 Jan 10
0
[LLVMdev] Using C++'11 language features in LLVM itself
...ecially crucial in HPC applications, where you may want to use LLVM > > to compile a domain-specific language and the compiler is part of a > larger > > project that you want to compile using a vendor compiler for performance > > reasons. > > > > In LLVM+platform_C++_compiler scenario the safest way would be to use > no C++11 features in LLVM at all and just keep the status quo. > That's exactly the point of this discussion. What C++11 features could be feasibly allow without alienating too many users with diverse requirements. > > > > >>...
2015 Apr 21
3
Availability of the 1.1.1 stable version
...h.pcm > > libopus 1.1.1-beta > > Decoding with 8000 Hz output (1 channels) > > average bitrate: 31.864 kb/s > > maximum bitrate: 49.200 kb/s > > bitrate standard deviation: 3.412 kb/s > > [root at MEDIA opus-1.1]# > > > > *_compiler flags in 1.1:_* > > > > AWK = gawk > > CC = gcc -std=gnu99 > > CCAS = gcc -std=gnu99 > > CCASDEPMODE = depmode=gcc3 > > CCASFLAGS = -g -O2 > > CCDEPMODE = depmode=gcc3 > > CFLAGS = -g -O2 -fvisibility=hidden -W -Wall -Wextra -Wcast-align > > -Wn...
2013 Jan 10
0
[LLVMdev] Using C++'11 language features in LLVM itself
On Thu, Jan 10, 2013 at 1:11 AM, Pawel Wodnicki <root at 32bitmicro.com> wrote: > Hello, > > I have been following this discussion for a while and I think the > question we should be asking is: > > Why do we want to even bother with all these other broken C++ > compilers in a first place? > Because not everyone that uses LLVM also uses Clang for every C++ compile.
2015 Apr 21
0
Availability of the 1.1.1 stable version
...coded_crash.opus > opus_encoded_crash.pcm > libopus 1.1.1-beta > Decoding with 8000 Hz output (1 channels) > average bitrate: 31.864 kb/s > maximum bitrate: 49.200 kb/s > bitrate standard deviation: 3.412 kb/s > [root at MEDIA opus-1.1]# > > *_compiler flags in 1.1:_* > > AWK = gawk > CC = gcc -std=gnu99 > CCAS = gcc -std=gnu99 > CCASDEPMODE = depmode=gcc3 > CCASFLAGS = -g -O2 > CCDEPMODE = depmode=gcc3 > CFLAGS = -g -O2 -fvisibility=hidden -W -Wall -Wextra -Wcast-align > -Wnested-externs -Wshadow -Wstrict-prototypes &...
2015 Apr 22
0
Availability of the 1.1.1 stable version
...1-beta >> > Decoding with 8000 Hz output (1 channels) >> > average bitrate: 31.864 kb/s >> > maximum bitrate: 49.200 kb/s >> > bitrate standard deviation: 3.412 kb/s >> > [root at MEDIA opus-1.1]# >> > >> > *_compiler flags in 1.1:_* >> > >> > AWK = gawk >> > CC = gcc -std=gnu99 >> > CCAS = gcc -std=gnu99 >> > CCASDEPMODE = depmode=gcc3 >> > CCASFLAGS = -g -O2 >> > CCDEPMODE = depmode=gcc3 >> > CFLAGS = -g -O2 -fvisibility=hidden -W -Wall -W...
2015 Apr 21
2
Availability of the 1.1.1 stable version
Hi, There is no change in the compiler flags. I'm using as it is from the original code. No change in the Makefile and I believe it is using the floating point only by default. We are using 8k samples and mono so the commands is as follows. [root at MEDIA opus-1.1]# ./opus_demo -d 8000 1 opus_encoded_crash.opus opus_encoded_crash.pcm *And segmentation is as below..*. ............ Calling
2013 Jan 10
5
[LLVMdev] Using C++'11 language features in LLVM itself
Hello, I have been following this discussion for a while and I think the question we should be asking is: Why do we want to even bother with all these other broken C++ compilers in a first place? Clang is good enough to bootstrap itself on practically any platform I can think of or it can be cross-bootstrapped if needed. I think usage of any language features should be decided based on