search for: fdiagnostic

...lability-new -Wall -Wextra -Wno-unused-parameter > -Wwrite-strings -Wcast-qual -Wmissing-field-initializers -pedantic > -Wno-long-long -Wimplicit-fallthrough -Wcovered-switch-default > -Wno-noexcept-type -Wnon-virtual-dtor -Wdelete-non-virtual-dtor > -Wstring-conversion -fdiagnostics-color -ffunction-sections > -fdata-sections -fno-common -Woverloaded-virtual -Wno-nested-anon-types > -O3 -DNDEBUG  -Wl,-allow-shlib-undefined > -Wl,-rpath-link,/home/laguest/src/mine-new/llvm/llvm-project/build/./lib >  -Wl,-O3 -Wl,--gc-sections > tools/clang/to...

...ror=date-time -Werror=unguarded-availability-new -Wall -Wextra -Wno-unused-parameter -Wwrite-strings -Wcast-qual -Wmissing-field-initializers -pedantic -Wno-long-long -Wimplicit-fallthrough -Wcovered-switch-default -Wno-noexcept-type -Wnon-virtual-dtor -Wdelete-non-virtual-dtor -Wstring-conversion -fdiagnostics-color -ffunction-sections -fdata-sections -fno-common -Woverloaded-virtual -Wno-nested-anon-types -O3 -DNDEBUG -Wl,-allow-shlib-undefined -Wl,-rpath-link,/home/laguest/src/mine-new/llvm/llvm-project/build/./lib -Wl,-O3 -Wl,--gc-sections tools/clang/tools/extra/clang-change-namespace/tool/CMakeFi...

...ers/joan/LLVM-9/llvm-project/build/Debug/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&quot...

...r=unguarded-availability-new -Wall -Wextra -Wno-unused-parameter > -Wwrite-strings -Wcast-qual -Wmissing-field-initializers -pedantic > -Wno-long-long -Wimplicit-fallthrough -Wcovered-switch-default > -Wno-noexcept-type -Wnon-virtual-dtor -Wdelete-non-virtual-dtor > -Wstring-conversion -fdiagnostics-color -ffunction-sections > -fdata-sections -fno-common -Woverloaded-virtual -Wno-nested-anon-types > -O3 -DNDEBUG -std=c++14 -MD -MT > > tools/clang/utils/TableGen/CMakeFiles/clang-tblgen.dir/ClangASTNodesEmitter.cpp.o > -MF > > tools/clang/utils/TableGen/CMakeFiles/clang...

...ch I am compiling using a sampling profile generated via perf and AutoFDO. I'd like to use this profile in order to show the hotness of each code path that is displayed in the new optimization remarks viewer tool ( https://www.youtube.com/watch?v=qq0q1hfzidg). It seems, however, that the '-fdiagnostics-show-hotness' option emits a warning when used with '-fprofile-sample-use': "warning: argument '-fdiagnostics-show-hotness' requires profile-guided optimization information". Looking at the code in Clang that generates the warning, it appears that the warning is emit...

...ers/joan/LLVM-9/llvm-project/build/Debug/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...

...ers/joan/LLVM-9/llvm-project/build/Debug/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...

...agnostics.vcxproj" -- FAILED. ========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ========== ## Proposed Solution We propose the addition of an option to output diagnostics that fully conform to [1]. There is currently an option in clang that enables VS compatible output, '-fdiagnostics-format=msvc' [3] [4]. This will enable visual studio to parse the full diagnostic. This will result in clickable links so that the IDE can display the source from which the error or warning originates, as well as adding errors and warnings to the error list. A visual studio conformant diagnos...

...ers/joan/LLVM-9/llvm-project/build/Debug/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/D...

...t -I../../src/lib-settings -I../../src/lib-ssl-iostream -DPKG_RUNDIR=\""/var/run/dovecot"\" -DPKG_STATEDIR=\""/var/lib/dovecot"\" -DSYSCONFDIR=\""/etc/dovecot"\" -DBINDIR=\""/usr/bin"\" -I/usr/local/include -std=gnu99 -fdiagnostics-color -Wl,-rpath=/usr/local/llvm40/lib -O2 -pipe -march=native -fno-strict-aliasing -fstack-protector-strong -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -Wno-duplicate-decl-specifier -Ws...

...nternal-isystem /path/to/musl/usr/local/include -internal-isystem /path/to/musl/lib/clang/4.0.0/include -internal-externc-isystem /path/to/musl/include -internal-externc-isystem /path/to/musl/usr/include -fdebug-compilation-dir /path/to/hello -ferror-limit 19 -fmessage-length 80 -fobjc-runtime=gcc -fdiagnostics-show-option -o hello.o -x c hello.c /path/to/musl/lib/ld-musl-x86_64.so.1: cannot load -cc1: No such file or directory As you can see it is trying to execute a compilation command with omitted clang binary path. So I thought that it would work in chroot with nothing but musl and clang in it....

...t; ========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ========== > > > ## Proposed Solution > > We propose the addition of an option to output diagnostics that fully > conform to [1]. There is currently an option in clang that enables VS > compatible output, '-fdiagnostics-format=msvc' [3] [4]. This will enable > visual studio to parse the full diagnostic. This will > result in clickable links so that the IDE can display the source from > which the error or warning originates, as well as adding errors and > warnings to the error list. > > A vis...

....sh SANDY /usr/local/bin/svnversion cc -c -O2 -frename-registers -pipe -fno-strict-aliasing -std=c99 -g -Wall -Wred undant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointe r-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wm issing-include-dirs -fdiagnostics-show-option -nostdinc -I. -I/usr/src/sys -I /usr/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_gl obal.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param la rge-function-growth=1000 -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mno-mmx...

On Tue, Jun 3, 2014 at 7:59 AM, Nancy <nancydreaming at gmail.com> wrote: >> First, you could switch to ld.gold instead of ld.bfd. It uses much > $ln -s `which gold` /usr/local/bin/ld > >> the idea. I think for autoconf you need ".../configure >> --enable-split-dwarf" to use this. >> > $.../configure --enable-targets=x86 --enable-split-dwarf >

...t-cpu pentium4 -target-linker-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... UR...

Hi, for filing a GCC v8.2.0 bug in Debian/buster AMD64 the Debian/GCC mainatiners want two things... [ FULL CMAKE LINE ] How do I configure this in the LLVM/Clang build? Can I set an option of cmake? [ PREPROCESSED SOURCE FILES ] How and where do I get the preprocessed source? Do I need to set options for this in my build-script? My build-script is attached. Thanks in advance. Regards, -

...c/llvm-toolchain/llvm/include -fPIC -fvisibility-inlines-hidden -Werror=date-time -std=c++11 -Wall -Wextra -Wno-unused-parameter -Wwrite-strings -Wcast-qual -Wno-missing-field-initializers -pedantic -Wno-long-long -Wno-maybe-uninitialized -Wno-class-memaccess -Wdelete-non-virtual-dtor -Wno-comment -fdiagnostics-color -ffunction-sections -fdata-sections -O3 -UNDEBUG -fno-exceptions -fno-rtti -MD -MT lib/Bitcode/Reader/CMakeFiles/LLVMBitReader.dir/MetadataLoader.cpp.o -MF lib/Bitcode/Reader/CMakeFiles/LLVMBitReader.dir/MetadataLoader.cpp.o.d -o lib/Bitcode/Reader/CMakeFiles/LLVMBitReader.dir/MetadataLo...

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

...ttings > -I../../src/lib-ssl-iostream -DPKG_RUNDIR=\""/var/run/dovecot"\" > -DPKG_STATEDIR=\""/var/lib/dovecot"\" -DSYSCONFDIR=\""/etc/dovecot"\" > -DBINDIR=\""/usr/bin"\" -I/usr/local/include -std=gnu99 > -fdiagnostics-color -Wl,-rpath=/usr/local/llvm40/lib -O2 -pipe > -march=native -fno-strict-aliasing -fstack-protector-strong > -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -Wall -W -Wmissing-prototypes > -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 > -Wbad-function-cast -Wno-duplicat...

...Wextra >>>>>> -Wno-unused-parameter -Wwrite-strings -Wcast-qual >>>>>> -Wno-missing-field-initializers -pedantic -Wno-long-long >>>>>> -Wno-maybe-uninitialized -Wno-class-memaccess >>>>>> -Wdelete-non-virtual-dtor -Wno-comment -fdiagnostics-color >>>>>> -ffunction-sections -fdata-sections -O3 -UNDEBUG -fno-exceptions >>>>>> -fno-rtti -MD -MT >>>>>> lib/Bitcode/Reader/CMakeFiles/LLVMBitReader.dir/MetadataLoader.cpp.o >>>>>> -MF lib/Bitcode/Reader/CMakeFiles/LL...