search for: fcolors

Displaying 20 results from an estimated 194 matches for "fcolors".

Did you mean: colors
2007 Oct 15
1
Error: X11 cannot allocate additional graphics colours.
...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) } Now...
2019 Nov 04
4
Debugging clang with debugger breakpoints ?
Hi David, Thank you for your patience but I still don’t get it: I don’t see how that is a “command”, as it’s just a list of strings that state command options. I know how to use the debugger, this is what I attempt to debug: clang --target=msp430 -emit-llvm -c -S -Oz main.c The debugger works fine, but only on the main thread. However breakpoints do not work with the code that was invoked
2019 Nov 04
2
Debugging clang with debugger breakpoints ?
Hi David, I understand what you say, but have you actually read my messages? I don’t think so, Anyway, I will repost the question in case someone else can help. Thanks John > On 4 Nov 2019, at 22:18, Zachary Turner <zturner at roblox.com> wrote: > > > > On Mon, Nov 4, 2019 at 1:11 PM Joan Lluch via llvm-dev <llvm-dev at lists.llvm.org <mailto:llvm-dev at
2019 Nov 04
2
Debugging clang with debugger breakpoints ?
Hi David, Thank you for your help. Please, can you elaborate on this?. The command line that I get with -### starts with this: clang version 9.0.1 (https://github.com/llvm/llvm-project.git 6e38ee067b8fa08792f551fb565bbb8ada4864b1) Target: msp430 Thread model: posix InstalledDir: /Users/joan/LLVM-9/llvm-project/build/Debug/bin "/Users/joan/LLVM-9/llvm-project/build/Debug/bin/clang"
2015 Mar 30
4
[LLVMdev] Color diagnostics
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
2019 Nov 04
2
Debugging clang with debugger breakpoints ?
Sorry Zach, my apologies. I understood now what you mean. I tried and it works!. But now I found that LLVM_DEBUG statements and other output to the console doesn’t show. How do I get that back?. Thanks John > On 4 Nov 2019, at 22:26, Zachary Turner <zturner at roblox.com> wrote: > > You hit Reply on my email but then addressed David. So I want to make sure you saw my
2004 Apr 10
4
(offtopic) I need two sets of 5 different color scales
...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 zipp...
2020 Aug 23
3
Apropos "shouting": PLEASE ATTACH THE FOLLOWING FILES TO THE BUG REPORT
Who's "shouting" here? Even in complete lines, 9 consecutive words! PLEASE ATTACH THE FOLLOWING FILES TO THE BUG REPORT: Preprocessed source(s) and associated run script(s) are located at: clang: note: diagnostic msg: C:\Windows\Temp\crash-74a40f.c clang: note: diagnostic msg: C:\Windows\Temp\crash-74a40f.sh clang: note: diagnostic msg: ******************** --- crash-74a40f.c ---
2014 May 09
2
[LLVMdev] Build failure with libcxx
Hi, Recently my libcxx enabled llvm/clang builds has started to fail in stage2. I must admit I am stomped because I cannot make sense of the error: [ 723s] FAILED: /home/abuild/rpmbuild/BUILD/llvm/stage1/bin/clang++ -DLLVMSupport_EXPORTS -DNDEBUG -D_GNU_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -stdlib=libc++ -fPIC -fvisibility-inlines-hidden -Wall -W
2017 Oct 17
2
liblldCommon is broken at head
ninja all check-xray [0/981] Building libLLVMTableGen for native TableGen... ninja: no work to do. [673/979] Linking CXX shared library lib/liblldCommon.so.6.0.0svn FAILED: lib/liblldCommon.so.6.0.0svn : && /usr/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
2015 Mar 09
5
[LLVMdev] Build failure with compiler-rt on trunk under linux
I've been building clang on linux for a couple of years now, contributing to the testing on Ubuntu, but this one has me stumped: fatal error: 'asm/socket.h' file not found #include <asm/socket.h> [1556/4006] Building CXX object projects/compiler-rt/lib/sanitizer_common/CMakeFiles/RTSanitizerCommon.i386.dir/sanitizer_platform_limits_posix.cc.o FAILED:
2020 Aug 23
2
Apropos "shouting": PLEASE ATTACH THE FOLLOWING FILES TO THE BUG REPORT
"David Blaikie" <dblaikie at gmail.com> wrote: > Context is everything. I'm willing to accept your humble apologies. > Spotting the relevant details in long build output > can be tricky & some emphasis (caps, the *** borders, etc) can be useful. So you dare to "shout" at your users/customers, but mock when someone (me) uses the same sort of emphasis,
2015 Dec 08
3
compiler-rt fails to find <stdarg.h> on FreeBSD
I'm unsure why this is failing this week, but when I build for FreeBSD HEAD, I now get a failure to find <stdarg.h>. Very strange. Maybe its missing a -I /usr/include somewhere? [1950/2811] Building CXX object projects/compiler-rt/lib/tsan/CMakeFiles/clang_rt.tsan-x86_64.dir/rtl/tsan_interceptors.cc.o FAILED: /usr/bin/CC -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS
2013 Oct 12
1
[LLVMdev] Fwd: unsupported gc: vmkit
when I execute clang on llvm bitcode files, I get the following error: clang: error: unable to execute command: Aborted unsupported GC: vmkit UNREACHABLE executed at GCMetadata.cpp:87! 0 clang 0x09e9d5d9 llvm::sys::PrintStackTrace(_IO_FILE*) + 41 Stack dump: 0. Program arguments: /home/ali/llvm-3.3.src/Release+Asserts/bin/clang -cc1 -triple i386-pc-linux-gnu -emit-obj -mrelax-all
2014 May 12
2
[LLVMdev] Build failure with libcxx
Ok looks like r207606 regressed this. CC'ing Niko. Niko, please see the messages below. This is on openSUSE 13.1 both on i586 and x86-64. Reverting r207606 fixes the second stage bootstrap. On Sun, May 11, 2014 at 10:19 PM, İsmail Dönmez <ismail at donmez.ws> wrote: > I did a diff -u broken.ii working.ii and the difference explains the > problem: > > @@ -36617,7 +36628,7
2020 Aug 23
2
Apropos "shouting": PLEASE ATTACH THE FOLLOWING FILES TO THE BUG REPORT
Hi Stefan, You can find the contribution guidelines here : https://llvm.org/docs/Contributing.html LLVM also have code of conduct : https://llvm.org/docs/CodeOfConduct.html On Sun, 23 Aug 2020 at 23:28, David Blaikie via llvm-dev < llvm-dev at lists.llvm.org> wrote: > > > On Sun, Aug 23, 2020 at 10:54 AM Stefan Kanthak <stefan.kanthak at nexgo.de> > wrote: > >>
2013 Feb 08
0
[LLVMdev] JIT on armhf
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
2018 Mar 20
0
r327904 / 5c4cd77db3a08587c6ac82a8e2c92cd4be0bc200 broke compiler-rt master
Hi, It seems that r327904 / 5c4cd77db3a08587c6ac82a8e2c92cd4be0bc200 broke master on FreeBSD: A direct revert fixes the issue. I'd also be happy with an ifdef though it seems unnecessary. $uname -rms FreeBSD 12.0-CURRENT amd64 $ninja ... /srv/src/llvm/llvm/projects/compiler-rt/lib/sanitizer_common/sanitizer_linux.cc:504:25: error: no member named 'environ' in the global namespace;
2015 Mar 30
2
[LLVMdev] Color diagnostics
Hi Hans, I used the official Ubuntu binary: http://llvm.org/releases/3.6.0/clang+llvm-3.6.0-x86_64-linux-gnu-ubuntu-14.04.tar.xz Seems to me that it should be an optional dependency. If the target system has tinfo or ncurses, it should use it, otherwise fallback to no color. On Mon, Mar 30, 2015 at 6:02 PM, Hans Wennborg <hans at chromium.org> wrote: > Hi Perry, > > On Mon, Mar
2012 Aug 29
0
[LLVMdev] Is cross-compiling for ARM on x86 with llvm/Clang possible?
Hi Journeyer First, thank you so much for your updates on your experiments. I am currently following your steps but have found myself stuck with the following error: /usr/lib/gcc/arm-linux-gnueabi/4.6/../../../../arm-linux-gnueabi/bin/ld: this linker was not configured to use sysroots clang: error: linker command failed with exit code 1 (use -v to see invocation) I used the command string you