search for: fcolor

...A, : Error: X11 cannot allocate additional graphics colours. Consider using X11 with colortype="pseudo.cube" or "gray". The problem is I only get it under certain circumstances. I have some quite convoluted test code: n <- 82 mat <- matrix(rnorm(n*10), ncol=n) fcolors <- terrain.colors(n) image(z=mat, axes=FALSE) oneis <- 1 / ncol(mat) sptl <- oneis / 3 max <- 1:n * oneis min <- c(0, max[1:length(max)-1]) for (i in 1:n) { axis(side=2, at=c(min[i]-sptl,max[i]+sptl), labels=NA, line=0.9, lwd=3, lty=1, tick=TRUE, tck=0, col=fcolors[i],lend=2) } No...

...ug/bin/../msp430/include" "-Oz" "-fdebug-compilation-dir" "/Users/joan/Documents-Local/Relay/RelayNou" "-ferror-limit" "19" "-fmessage-length" "224" "-fobjc-runtime=gcc" "-fdiagnostics-show-option" "-fcolor-diagnostics" "-vectorize-slp" "-faddrsig" "-o" "main.ll" "-x" "c" "main.c" > > Or wherever you had: -emit-llvm -S -g main.c (or something like that) > You now have: "-cc1" "-triple" "msp43...

...ug/bin/../msp430/include" "-Oz" "-fdebug-compilation-dir" "/Users/joan/Documents-Local/Relay/RelayNou" "-ferror-limit" "19" "-fmessage-length" "224" "-fobjc-runtime=gcc" "-fdiagnostics-show-option" "-fcolor-diagnostics" "-vectorize-slp" "-faddrsig" "-o" "main.ll" "-x" "c" "main.c" > > Yes it is a list of strings. But the first string "/Users/joan/LLVM-9/llvm-project/build/Debug/bin/clang" is a command. The r...

...ug/bin/../msp430/include" "-Oz" "-fdebug-compilation-dir" "/Users/joan/Documents-Local/Relay/RelayNou" "-ferror-limit" "19" "-fmessage-length" "224" "-fobjc-runtime=gcc" "-fdiagnostics-show-option" "-fcolor-diagnostics" "-vectorize-slp" "-faddrsig" "-o" "main.ll" "-x" "c" "main.c" So what should I set on the debugger? Thanks John > On 4 Nov 2019, at 21:03, David Blaikie <dblaikie at gmail.com> wrote: > &gt...

Hi, I'm using the official 3.6 release binaries for x64 Linux. When compiling with warnings, I don't see any color diagnostics. Explicitly enabling -fcolor-diagnostics works fine. I have TERM set to xterm-256color. Any idea why? For what it's worth, I tried compiling LLVM/clang from trunk and color diagnostics work fine by default. Upon further investigation, I saw that the official binaries were not linked against libtinfo: Official binaries:...

...ug/bin/../msp430/include" "-Oz" "-fdebug-compilation-dir" "/Users/joan/Documents-Local/Relay/RelayNou" "-ferror-limit" "19" "-fmessage-length" "224" "-fobjc-runtime=gcc" "-fdiagnostics-show-option" "-fcolor-diagnostics" "-vectorize-slp" "-faddrsig" "-o" "main.ll" "-x" "c" "main.c" >> >> Yes it is a list of strings. But the first string "/Users/joan/LLVM-9/llvm-project/build/Debug/bin/clang" is a command...

...llowing: I need two sets of colors for B and F which are easy to distinguish (when printed on a color laser printer), represent cardinality (ie have an intuitive mapping to an interval) or at least ordinality. I have experimented with the following: Bcolors <- hsv(.6, seq(0.2, 1, length=5), 1) Fcolors <- hsv(seq(.1,0, length=5), seq(0.2, 1, length=5) this is what you see in the plot. What colors would you use? Do you think that varying both brightness and hue helps to distinguish colors? Should I change saturation, too? Thanks, Tamas PS.: The plot is simply gzipped. If you need a zip...

...; "-fmessage-length" "80 " "-fno-use-cxa-atexit" "-fms-extensions" "-fms-compatibility" "-fms-compatibili ty-version=19.11" "-fdelayed-template-parsing" "-fobjc-runtime=gcc" "-fdiagnosti cs-show-option" "-fcolor-diagnostics" "-faddrsig" "-o" "crash.o" "-x" "c" "crash .c" "C:\\Program Files\\LLVM\\bin\\clang.exe" "-cc1" "-triple" "x86_64-pc-windows-m svc19.11.0" "-emit-obj" "-mrelax-all&q...

...-DNDEBUG -D_GNU_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -stdlib=libc++ -fPIC -fvisibility-inlines-hidden -Wall -W -Wno-unused-parameter -Wwrite-strings -Wmissing-field-initializers -pedantic -Wno-long-long -Wcovered-switch-default -Wnon-virtual-dtor -std=c++11 -fcolor-diagnostics -ffunction-sections -fdata-sections -O2 -g -DNDEBUG -fPIC -Ilib/Support -I../lib/Support -Iinclude -I../include -fno-exceptions -MMD -MT lib/Support/CMakeFiles/LLVMSupport.dir/Allocator.cpp.o -MF lib/Support/CMakeFiles/LLVMSupport.dir/Allocator.cpp.o.d -o lib/Support/CMakeFiles/LLVMS...

...bin/clang++-3.9 -fPIC -Wpedantic -fPIC -fvisibility-inlines-hidden -Werror=date-time -std=c++11 -Wall -W -Wno-unused-parameter -Wwrite-strings -Wcast-qual -Wmissing-field-initializers -pedantic -Wno-long-long -Wcovered-switch-default -Wnon-virtual-dtor -Wdelete-non-virtual-dtor -Wstring-conversion -fcolor-diagnostics -ffunction-sections -fdata-sections -O3 -Wl,-z,defs -fuse-ld=gold -Wl,-rpath-link,/usr/local/google/home/dberris/xray/llvm-build/./lib -Wl,-O3 -Wl,--gc-sections -shared -Wl,-soname,liblldCommon.so.6 -o lib/liblldCommon.so.6.0.0svn tools/lld/Common/CMakeFiles/lldCommon.dir/Reproduce....

...SEGV=1 -D_GNU_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -fPIC -fvisibility-inlines-hidden -Wall -W -Wno-unused-parameter -Wwrite-strings -Wcast-qual -Wmissing-field-initializers -pedantic -Wno-long-long -Wcovered-switch-default -Wnon-virtual-dtor -std=c++11 -fcolor-diagnostics -ffunction-sections -fdata-sections -Wall -std=c++11 -O3 -DNDEBUG -Iprojects/compiler-rt/lib/sanitizer_common -I/home/ben/development/llvm/trunk/llvm/projects/compiler-rt/lib/sanitizer_common -Iinclude -I/home/ben/development/llvm/trunk/llvm/include -fPIC -fvisibility-inlines-h...

...gt; " "-fno-use-cxa-atexit" "-fms-extensions" "-fms-compatibility" >> "-fms-compatibili >> ty-version=19.11" "-fdelayed-template-parsing" "-fobjc-runtime=gcc" >> "-fdiagnosti >> cs-show-option" "-fcolor-diagnostics" "-faddrsig" "-o" "crash.o" "-x" "c" >> "crash >> .c" >> "C:\\Program Files\\LLVM\\bin\\clang.exe" "-cc1" "-triple" >> "x86_64-pc-windows-m >> svc19.11.0&qu...

...cc.o FAILED: /usr/bin/CC -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -fPIC -fvisibility-inlines-hidden -Wall -W -Wno-unused-parameter -Wwrite-strings -Wcast-qual -Wmissing-field-initializers -pedantic -Wno-long-long -Wcovered-switch-default -Wnon-virtual-dtor -std=c++11 -fcolor-diagnostics -Wall -std=c++11 -g -Iprojects/compiler-rt/lib/tsan -I/home/sbruno/clang/llvm/projects/compiler-rt/lib/tsan -Iinclude -I/home/sbruno/clang/llvm/include -I/usr/local/include -I/home/sbruno/clang/llvm/projects/compiler-rt/lib/tsan/.. -m64 -fPIC -fno-builtin -fno-exceptions -fomit-fram...

...ker-version 2.21.53.20110810 -resource-dir /home/ali/llvm-3.3.src/Release+Asserts/bin/../lib/clang/3.3 -fdebug-compilation-dir /home/ali/Code/ReyMRE/vm/tools/ReyVM -ferror-limit 19 -fmessage-length 113 -mstackrealign -fobjc-runtime=gcc -fobjc-default-synthesize-properties -fdiagnostics-show-option -fcolor-diagnostics -backend-option -vectorize-loops -o /tmp/OutOfMemoryError-NgX1wV.o -x ir /home/ali/Code/ReyMRE/test/bin/rey/lang/somefile.bc 1. Code generation What should I do to resolve this issue? -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.l...

...STANT_MACROS >> -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -stdlib=libc++ -fPIC >> -fvisibility-inlines-hidden -Wall -W -Wno-unused-parameter -Wwrite-strings >> -Wmissing-field-initializers -pedantic -Wno-long-long >> -Wcovered-switch-default -Wnon-virtual-dtor -std=c++11 -fcolor-diagnostics >> -ffunction-sections -fdata-sections -O2 -g -DNDEBUG -fPIC -Ilib/Support >> -I../lib/Support -Iinclude -I../include -fno-exceptions -MMD -MT >> lib/Support/CMakeFiles/LLVMSupport.dir/Allocator.cpp.o -MF >> lib/Support/CMakeFiles/LLVMSupport.dir/Allocator.cpp...

..." "-fms-extensions" "-fms-compatibility" >> >> "-fms-compatibili >> >> ty-version=19.11" "-fdelayed-template-parsing" "-fobjc-runtime=gcc" >> >> "-fdiagnosti >> >> cs-show-option" "-fcolor-diagnostics" "-faddrsig" "-o" "crash.o" "-x" >> "c" >> >> "crash >> >> .c" >> >> "C:\\Program Files\\LLVM\\bin\\clang.exe" "-cc1" "-triple" >> >> &qu...

On 8 February 2013 14:28, David Given <dg at cowlark.com> wrote: > Debian's clang packages are totally broken on armhf --- the compiler > emits a confused warning about the platform being unrecognised, and then > generates softfloat code --- so I was wondering about LLVM itself. I'm using Ubuntu on Pandas and Chromebooks and LLVM itself behaves well, with the right set of

...piler-rt/lib/sanitizer_common/.. -fPIC -fvisibility-inlines-hidden -Werror=date-time -std=c++11 -Wall -W -Wno-unused-parameter -Wwrite-strings -Wcast-qual -Wmissing-field-initializers -pedantic -Wno-long-long -Wcovered-switch-default -Wnon-virtual-dtor -Wdelete-non-virtual-dtor -Wstring-conversion -fcolor-diagnostics -Wall -std=c++11 -Wno-unused-parameter -g -fPIC -fvisibility-inlines-hidden -Werror=date-time -std=c++11 -Wall -W -Wno-unused-parameter -Wwrite-strings -Wcast-qual -Wmissing-field-initializers -pedantic -Wno-long-long -Wcovered-switch-default -Wnon-virtual-dtor -Wdelete-non-virtual-...

...; wrote: > Hi Perry, > > On Mon, Mar 30, 2015 at 11:16 AM, Perry Hung <perry at leaflabs.com> wrote: > > I'm using the official 3.6 release binaries for x64 Linux. When compiling > > with warnings, I don't see any color diagnostics. Explicitly enabling > > -fcolor-diagnostics works fine. I have TERM set to xterm-256color. Any > idea > > why? > > Which of the release binaries are you using? 3.6 has x86_64 binaries > for Ubuntu, OpenSuSE and Fedora, and they were built by difference > people. > > From your ldd dump, it seems the bina...

...tem /usr/arm-linux-gnueabi/usr/include -fno-dwarf-directory-asm -fdebug-compilation-dir /home/jedd10-04/TOOC/clang-samples -ferror-limit 19 -fmessage-length 132 -mstackrealign -fno-signed-char -fgnu-runtime -fobjc-runtime-has-arc -fobjc-runtime-has-weak -fobjc-fragile-abi -fdiagnostics-show-option -fcolor-diagnostics -o hello.i -x c hello.c clang -cc1 version 3.1 based upon LLVM 3.1 default target x86_64-unknown-linux-gnu ignoring nonexistent directory "/usr/arm-linux-gnueabi/usr/local/include" ignoring nonexistent directory "/usr/arm-linux-gnueabi/usr/include" #include "......