Displaying 20 results from an estimated 5000 matches similar to: "[LLVMdev] new warnings"
2009 Jan 02
2
[LLVMdev] new warnings in -r61596
2 new warnings in llvm:
/Volumes/mrs5/net/llvm/llvm/lib/AsmParser/LLParser.cpp: In member
function 'bool llvm::LLParser::ParseGlobal(const std::string&, const
char*, unsigned int, bool, unsigned int)':
/Volumes/mrs5/net/llvm/llvm/lib/AsmParser/LLParser.cpp:446: warning:
'IsConstant' may be used uninitialized in this function
2009 Jan 08
1
[LLVMdev] Build failure on x86_64
Hello!
I see the following build failure of the sources at the top of the trunk, on
x86_64.
make[2]: Entering directory `<llvm-root>/build/llvm/lib/AsmParser'
llvm[2]: Compiling LLLexer.cpp for Release build
llvm[2]: Compiling LLParser.cpp for Release build
<llvm-root>/src/llvm/lib/AsmParser/LLParser.cpp: In member function 'bool
llvm::LLParser::ParseGlobal(const
2009 Feb 09
0
[LLVMdev] 2.5 Pre-release1 available for testing
Hi Tanya, I see the following warnings when building. I'm not sure
how to fix any of them. The last one looks like it might be serious
(seems like a job for Chris).
llvm[1]: Compiling Path.cpp for Release build
In file included from Path.cpp:270:
Unix/Path.inc: In member function ‘bool llvm::sys::Path::eraseFromDisk(bool, std::string*) const’:
Unix/Path.inc:661: warning: ignoring return
2010 Nov 09
1
[LLVMdev] uninitialized value warnings: LLVMParser.cpp
These warnings started appearing recently when building LLVM:
llvm[2]: Compiling LLParser.cpp for Release build
/Volumes/Data/Users/kremenek/llvm/lib/AsmParser/LLParser.cpp: In member function ‘bool llvm::LLParser::ParseBr(llvm::Instruction*&, llvm::LLParser::PerFunctionState&)’:
/Volumes/Data/Users/kremenek/llvm/lib/AsmParser/LLParser.cpp:3195: warning: ‘Op1’ may be used uninitialized in
2007 Dec 15
4
[LLVMdev] fix warning with newer g++ compilers
Newer g++ compilers can emit:
/Volumes/mrs5/net/llvm/llvm/llvm/lib/AsmParser/LLLexer.cpp: In member
function 'int llvm::LLLexer::LexAt()':
/Volumes/mrs5/net/llvm/llvm/llvm/lib/AsmParser/LLLexer.cpp:287:
warning: suggest a space before ';' or explicit braces around empty
body in 'for' statement
/Volumes/mrs5/net/llvm/llvm/llvm/lib/AsmParser/LLLexer.cpp: In member
2016 Jun 02
6
-Wmisleading-indentation violations
Hi,
I was building LLVM with gcc 6.1.1 recently and it was spitting out
some warnings relating to misleading indention that caught my eye.
This wasn't a fresh build so I may have missed some. I've CC'ed the
authors of the potentially misleading lines so they can decide what do
about the warnings (if anything).
I'm wondering if clang-format is making some inappropriate choices
2016 May 26
1
Potential ambiguity in the grammar of LLVM IR assembly
Hello Tim,
Thank you for getting back to me.
The language grammar as defined by the LLVM Language Reference Manual
[1] does not include the details of the LLVM IR parser reference
implementation.
The following extract from "lib/AsmParser/LLParser.cpp" illustrates that
unnamed globals are allowed [2].
> /// ParseUnnamedGlobal:
> /// OptionalVisibility (ALIAS | IFUNC) ...
2014 Nov 27
2
[LLVMdev] Fast-math flags in constant expressions
Hi,
I'm wondering why lib/AsmParser/LLParser handles fast-math flags in the
following IR:
...
%val = fmul nnan double 1.0, 1.0
...
but doesn't allow any flags if "fmul" is inside "phi":
...
%val = phi double [ fmul (double 1.0, double 1.0), %cond.true ],
[ fmul (double 1.0, double 1.0), %cond.false ]
...
2017 Jan 26
2
Question about versioning of LVVM IR
Hello,
It is likely that I missing something however I have to ask.
We are working on Mull project https://github.com/mull-project which deals
with
LLVM IR in the first place so it is often that we encounter errors like
the following one when we do things like parseAssemblyString(IR, Err,
GlobalCtx);`:
```
test: <string>:7237:187: error: invalid field 'variable'
!1526 = distinct
2019 Jul 16
4
Scalable Vector Types in IR - Next Steps?
Hi Alex,
We've only recently managed to get the core scalable vector IR type into the codebase (so it will be present in 9.0); that allows you to write IR with scalable vector types, but there's no backend able to generate code for it yet, and as you mention no support for stepvector (or vscale). Arm will start upstreaming those soon.
-Graham
> On 13 Jul 2019, at 14:32, Alex Susu via
2016 Oct 07
2
Is extern_weak a legal linkage for function definitions?
Hi,
The LLVM language reference doesn't say that extern_weak is illegal for
function definitions, but it seems this restriction is enforced in the
code in some places:
https://github.com/llvm-mirror/llvm/blob/master/lib/AsmParser/LLParser.cpp#L4591
https://github.com/llvm-mirror/llvm/blob/master/lib/CodeGen/AsmPrinter/AsmPrinter.cpp#L327
However it is possible to create a bitcode file
2014 Dec 02
2
[LLVMdev] Fast-math flags in constant expressions
Out of curiosity, how would you envision fast-math flags interacting with constant expressions? Off the top of my head, I can’t think of any flags that would be relevant if the expression can just be constant-folded away at full precision anyways.
> On Nov 28, 2014, at 4:56 AM, Sergey Dmitrouk <sdmitrouk at accesssoftek.com> wrote:
>
> Doesn't look like a bug, more like a
2012 May 07
6
[LLVMdev] Metadata for Argument, BasicBlock
Hi Duncan,
On 5/6/12 6:12 PM, Duncan Sands wrote:
> Hi Ralf,
>
>> Is there a clean way to attach metadata nodes to Arguments and/or
>> BasicBlocks?
>
> not at the moment. Feel free to work on adding this functionality!
I am looking into that now.
I decided to temporarily go for the following syntax for BasicBlock
metadata (subject to discussion):
entry:
2015 Sep 17
2
[PATCH] D12923: Add support for function attribute "notail"
+llvm-dev
Can you give a bit of background on what you're trying to address here?
After reading through the discussion and seeing that this is a best
effort flag, I'm not sure that a function attribute is the best way to
describe this. I'm open to being convinced it is, but I'd like to hear
a bit more about the use case and get broader visibility on the proposal
first.
2012 May 07
0
[LLVMdev] Metadata for Argument, BasicBlock
On May 7, 2012, at 7:21 AM, Ralf Karrenberg <Chareos at gmx.de> wrote:
> Hi Duncan,
>
> On 5/6/12 6:12 PM, Duncan Sands wrote:
>> Hi Ralf,
>>
>>> Is there a clean way to attach metadata nodes to Arguments and/or
>>> BasicBlocks?
>>
>> not at the moment. Feel free to work on adding this functionality!
>
> I am looking into that
2013 Nov 27
0
[LLVMdev] Bug in Language Reference? %0 versus %1 as starting index.
(gah, this turned into a huge digression, sorry)
The implicit numbering of BB's seems to be a pretty frequent issue for
people. Surprisingly, the issue boils down to simply changing the IR asm
(.ll file) syntax so that it can have "unnamed BB's" in a recognizable way
that fits in with how unnamed values work (the asmprinter makes an effort
to print a comment with the BB number,
2008 Sep 26
4
[LLVMdev] build failure in Attributes.h
I'm seeing a build failure...
In file included from /Volumes/mrs5/net/llvm/llvm/lib/VMCore/
Attributes.cpp:14:
/Volumes/mrs5/net/llvm/llvm/include/llvm/Attributes.h: In member
function 'llvm::Attributes
llvm::AttrListPtr::getParamAttributes(unsigned int) const':
/Volumes/mrs5/net/llvm/llvm/include/llvm/Attributes.h:152: error:
'assert' was not declared in this scope
2013 Nov 27
2
[LLVMdev] Bug in Language Reference? %0 versus %1 as starting index.
Thanks for the lecture :) But I was not planning on changing a single line
in LLVM/Clang. I stick to the documentation until I've learned to swim,
perhaps even forever. Ah, now I see. You thought I meant "should I modify
the code to do this or that." I only meant to change the documentation.
Please refer to the patch I've sent on LLVM-commits. That's about what I
had
2014 Oct 24
8
[LLVMdev] First-class debug info IR: MDLocation
I've attached a preliminary patch for `MDLocation` as a follow-up to the
RFC [1] last week. It's not commit-ready -- in particular, it squashes
a bunch of commits together and doesn't pass `make check` -- but I think
it's close enough to indicate the direction and work toward consensus.
[1]: http://lists.cs.uiuc.edu/pipermail/llvmdev/2014-October/077715.html
IMO, the files to
2012 May 08
2
[LLVMdev] Metadata for Argument, BasicBlock
If we were to implement the #unroll pragma, we would want to add metadata to loop headers. But, it's not a big deal since we can simply add this metadata to block terminators.
-----Original Message-----
From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] On Behalf Of Dan Gohman
Sent: Tuesday, May 08, 2012 00:58
To: Ralf Karrenberg
Cc: llvmdev at cs.uiuc.edu List