search for: cmdoptions

Hi, Since I've migrated to a newer linux distro I can't build docs-clang-html. 1. get LLVM 2. cmake -GNinja -DLLVM_ENABLE_SPHINX=YES -DSPHINX_OUTPUT_HTML=YES -DLLVM_BUILD_DOCS=YES ~/llvm 3. ninja docs-clang-html ======================= [1/2] Generating html Sphinx documentation for clang into "/tmp/LLVM/tools/clang/docs/html" FAILED:

On 13 December 2016 at 17:45, Zachary Turner via llvm-dev <llvm-dev at lists.llvm.org> wrote: > Over a month ago I submitted some patches to begin documenting PDB file > format. These files are in llvm/docs/PDB. When I view the docs online > though, they appear stale. Many of the pages are blank, containing only a > file header. This matches up with my initial commit of the

RFC: lld- Add visual studio compatible diagnostics output to lld Hello all, We have a proposal to extend the diagnostics output capabilities of lld. ## Problem MS Visual Studio expects the diagnostic output of build tools to conform to a specific format, described here: [1] and [2] . Currently lld cannot emit warnings and errors in this format. lld prefixes diagnostic output with args[0],

Hi, I understand that making lld's error message compatible with MSVC makes it easy to use in IDEs. But at the same time I personally prefer the current style of lld's error message because it's easier to read particularly when filenames or symbol names are long (which is a norm in modern projects). I'd start with experimenting your idea with a small change. I guess that the

Hi, We would like to see that change, too, especially for lld/ELF. Chris, do you have a patch or just looking for help? Best Regards, Igor Kudrin C++ Developer, Access Softek, Inc. ________________________________ From: llvm-dev <llvm-dev-bounces at lists.llvm.org> on behalf of Rui Ueyama via llvm-dev <llvm-dev at lists.llvm.org> Sent: Friday, February 23, 2018 6:37 AM To: Chris

Hi Tanya, Last time I noticed a problem with clang-tools-extra docs you could help solving them. If someone else is taking care of this part of the infrastructure now, please redirect appropriately. It looks like docs generated from rst (for LLVM, Clang and clang-tools-extra) don't get updated at the moment. They stopped updating somewhere between r353327

http://llvm.org/docs/CommandGuide/FileCheck.html says FileCheck ignores white spaces/tabs by default unless you use "--strict-whitespace" option. 2013/3/15 Shawn <shaolin.xie at ia.ac.cn>: > Hi all: > I'm writing testcase for the MC layer regression in llvm, the > disassembled string is a bit complicate, for example: > "IALU.T0 (I0) = BIU0.DM ; REPEAT

"--strict-whitespace By default, FileCheck canonicalizes input horizontal whitespace (spaces and tabs) which causes it to ignore these differences (a space will match a tab). The/--strict-whitespace/ <http://llvm.org/docs/CommandGuide/FileCheck.html#cmdoption--strict-whitespace>argument disables this behavior. End-of-line sequences are canonicalized to UNIX-style ‘n’ in all

Hi all: I'm writing testcase for the MC layer regression in llvm, the disassembled string is a bit complicate, for example: "IALU.T0 (I0) = BIU0.DM ; REPEAT AT ( 2 ) ;;" The spaces in the disassembled string is error-prone. Is there any option to tell the FileCheck utility to ignore the spaces ? Kind Regards. Shawn.

Yes when I first committed the docs were fine upstream. I think I even got 1 or 2 additional commits that I could see the changes of reflected on the website. At some point though, it just stopped updating (I don't know which exact CL). I can find a date range of when things stopped being update if that would be helpful. If I look at the PDB documentation now (which is rooted here

Over a month ago I submitted some patches to begin documenting PDB file format. These files are in llvm/docs/PDB. When I view the docs online though, they appear stale. Many of the pages are blank, containing only a file header. This matches up with my initial commit of the documentation, as I initially just created stub pages, but as I continued to improve the documentation, the website never

...un sys.exit(dispatch(sys.argv[1:])) File "/usr/lib64/python2.3/site-packages/mercurial/commands.py", line 1571, in dispatch return d() File "/usr/lib64/python2.3/site-packages/mercurial/commands.py", line 1556, in <lambda> d = lambda: func(u, repo, *args, **cmdoptions) File "/usr/lib64/python2.3/site-packages/mercurial/commands.py", line 938, in pull r = repo.pull(other) File "/usr/lib64/python2.3/site-packages/mercurial/hg.py", line 1404, in pull return self.addchangegroup(cg) File "/usr/lib64/python2.3/site-packages/mercu...

Hi Devs, going by this link https://llvm.org/docs/LangRef.html#floatenv it says that floating point operation does not have side effects by defaults. but when compile a test case i.e. cat a.c float foo(float a, float b) { return a+b; } $clang a.c -O2 -S -emit-llvm emit ir like: $cat a.ll --------------------------------------- ; ModuleID = 'a.c' source_filename = "a.c" target