Displaying 20 results from an estimated 1200 matches similar to: "[LLVMdev] How to not zeroinitialize array"
2015 Feb 27
2
[LLVMdev] [3.6 Release] Release Candidate 2 available
On Mon, Feb 9, 2015 at 9:47 PM, Anton Korobeynikov
<anton at korobeynikov.info> wrote:
> Hans,
>
>>> I see a Git branch "release_36", but what has v3.6.0rc2 for a
>>> commit-id, can you tags that?
>>> No, there are no tags at all @ github.
>>
>> Anton, is it possible to translate the svn tags to git tags?
> In the past we had problems
2015 Feb 07
5
[LLVMdev] mesa-10.4.4: BROKEN TLS support in GLX with llvm-toolchain v3.6.0rc2
[ Please CC me I am not subscribed to mesa-dev and llvmdev MLs ]
Hi,
I already reported this when playing 1st time with my llvm-toolchain
v3.6.0rc2 and mesa v10.3.7 [1].
The issue still remains in mesa v10.4.4.
So, this is a field test to see if LLVM/Clang v3.6.0rc2 fits my needs.
I see the following build-error...
...
make[4]: Entering directory
2015 Feb 09
2
[LLVMdev] mesa-10.4.4: BROKEN TLS support in GLX with llvm-toolchain v3.6.0rc2
On 09/02/15 17:44, Emil Velikov wrote:
> Hi Sedat,
>
> On 07/02/15 22:42, Sedat Dilek wrote:
>> [ Please CC me I am not subscribed to mesa-dev and llvmdev MLs ]
>>
>> Hi,
>>
>> I already reported this when playing 1st time with my llvm-toolchain
>> v3.6.0rc2 and mesa v10.3.7 [1].
>> The issue still remains in mesa v10.4.4.
>>
>> So,
2015 Dec 30
2
Substitute instruction with a jump to a library code
I'm trying to find a way to emulate a floating point instruction, say a
floating point add. My understanding is that in order to do that I need to
execute
setOperationAction(ISD::FADD, (MVT::f32, Expand);
setOperationAction(ISD::FADD, (MVT::f64, Expand);
in MyTargetISelLowering.cpp, MyTargetLowering::MyTargetLowering(...).
However for some reason I'm still seeing a floating point add in
2015 May 22
2
[LLVMdev] GCC compatibility code coverage issue .
Hi Justin ,
Thank you for the confirmation and we would like to know that ,going
forward the clang has the support the gcc gcov format or use the
-fprofile-instr-generate -fcoverage-mapping and get ride of gcov
format .
We are planing to customize the clang code coverage for embedded world
,before we start tweaking the gcov / -fprofile-instr-generate
code-base ,we would like to take feedback
2015 Feb 27
0
[LLVMdev] [3.6 Release] Release Candidate 2 available
> In conclusion:
> Why are people using Git disadvantaged?
Short answer: because of git-svn and differences between what is a tag
in git and svn.
Long answer: git-svn never created proper git tags. Instead, it
converted svn tags to branches (because technically branches and tags
are same in svn). These branches were orphan and not usable for bunch
of things (I believe Takumi can provide a
2015 Jul 06
2
[LLVMdev] Customizing module compilation in ORC JITs
Hi Lang,
I'm looking at extending the compilation passes used in the LLILC JIT and it seems like the simplest thing is to make a copy of the SimpleCompiler functor into the LLILC code and then modify it for the phases I want to run. But I was wondering if this was the best approach. Do you expect different clients to create their own compiler functors or do you imagine that SimpleCompiler
2015 May 27
0
[LLVMdev] GCC compatibility code coverage issue .
Umesh Kalappa <umesh.kalappa0 at gmail.com> writes:
> Hi Justin ,
>
> Thank you for the confirmation and we would like to know that ,going
> forward the clang has the support the gcc gcov format or use the
> -fprofile-instr-generate -fcoverage-mapping and get ride of gcov
> format .
Going forward, the -fprofile-instr-generate -fcoverage-mapping (which
I'll refer to as
2015 Jul 30
1
[LLVMdev] A few folks in the SF Bay area are planning to get together to discuss GC statepoints
That might work. I'm actually particularly interested in your perspective
here, so even if it doesn't, I had already planned to specifically email
you to make sure I got your thoughts here.
But maybe a conference call would work. By far the easiest is for us to do
a Google hangout, which would give video and audio. Would that work on your
end?
On Thu, Jul 30, 2015, 08:50 Russell Hadley
2015 May 13
4
[LLVMdev] Extending AsmPrinterHandler
(background) The CoreCLR expects a JIT to produce a MSIL bytecode offset to code offset mapping annotated with a few extra bits denoting if it’s prolog/epilog, or it’s a call, or if there’s operands remaining on the MSIL virtual stack in some cases. Our initial prototype has the MSIL offset stashed in the line number field. We could stash the extra bits in the column info but that’s starting to
2015 Apr 15
2
[LLVMdev] MS fork
Chandler has it right. Our intent is to upstream everything. The MS fork will be used as a staging area for LLVM changes as we work to get them upstreamed. Tactically we're merging the MS fork everyday with mainline to try and stay close.
We're still ramping up right now, and trying to figure out how best to work day to day, but our over arching goal is to enable (mainline) LLVM to be
2015 Apr 16
2
[LLVMdev] MS fork
The LLILC project does not require direct interaction with the PDB, so it’s not part of our plans.
The JIT uses a special reporting format to communicate debug info (frame info and machine->IL mappings) back to the CoreCLR EE. The debugger joins this with the frontend-produced debug information (IL->source and logical frame offset->local, which is in a PDB) to complete the picture.
2004 Jul 13
1
[LLVMdev] Global data order
Hello,
given
%TestArrayPtr = global %struct.test* getelementptr (
[10 x %struct.test]* %TestArray, ..........
%TestArray = weak global [10 x %struct.test] zeroinitialize
my backend produce data declaration in the same order, so TestArrayPtr refers
to TestArray before TestArray itself is defined.
Is there a standard way to get the right ordering. I wrote my own code, but
2016 Nov 25
3
Translation of custom attribute (defined for variables) from clang to llvm
Hi Asit,
thanks for the reply.
But I guess I was not clear in my question. Actually, i dont want to use
__ATTRIBUTE__((ANNOTATE("MOVIATTR"))), since in documentation it is
stated that "This intrinsic allows annotation of local variables with
arbitrary strings. This can be useful for special purpose optimizations
that want to look for these annotations. These have no other
2015 Aug 27
4
RFC: alloca -- specify address space for allocation
Inline.
From: Philip Reames [mailto:listmail at philipreames.com]
Sent: Thursday, August 27, 2015 11:01 AM
To: Swaroop Sridhar <Swaroop.Sridhar at microsoft.com>; llvm-dev <llvm-dev at lists.llvm.org>; Sanjoy Das <sanjoy at playingwithpointers.com>
Cc: Joseph Tremoulet <jotrem at microsoft.com>; Andy Ayers <andya at microsoft.com>; Russell Hadley <rhadley at
2015 Apr 28
4
[LLVMdev] GCC compatibility code coverage issue .
Hi All,
We trying to use clang+llvm to generate the gcc coverage format as
clang version 3.6.0
$clang --coverage -Xclang -coverage-cfg-checksum -Xclang
-coverage-no-function-names-in-data -Xclang -coverage-version='407*'
test.c
$a.out
$llvm-cov gcov test.gcda
Unexpected version: *704.
Invalid .gcno File!
Debugging the above cause ,But any hints from experts here ,will help a lot
2006 Jun 14
1
Having problems with ov_read
Ok here is the breakdown. I am trying to impliment streaming into our game
using openAL and ogg-vorbis. In the non-streaming function when I call
ov_read on the file I should be streaming the buffer gets filled with the
correct data. However, when I run ov_read on the same OggVorbis_File when I
read the buffer gets filled with 0's. The buffer has not been zero'd and
starts filled
2016 Nov 28
2
Translation of custom attribute (defined for variables) from clang to llvm
Hi John,
I have looked into the EmitAutoVarAlloca() in CGDecl.cpp. However, I
could not figure out how to employ my custom attribute for code
generation. For example, my custom attribute is visible in CGDecl.cpp
but how can I generate based on my custom attribute
if (D.hasAttr<myCustomAttri>())
{
//What to do here?
}
What I wan in IR is something like below.
Without Custom Attribute:
2015 Aug 27
3
RFC: alloca -- specify address space for allocation
Philip: I think there are two separate issues:
1) Handling GC pointers stored in stack locations -- tracking their liveness, reporting them to the GC. etc.
2) Treating pointers to stack locations as GC-pointers.
I think the two options that you presented here are for solving (1).
I'm trying to solve issue (2) using alloca in addrspace(1).
Basically, we want to create a pointer to a stack
2015 Aug 29
5
RFC: alloca -- specify address space for allocation
> -----Original Message-----
> From: Philip Reames [mailto:listmail at philipreames.com]
> Sent: Friday, August 28, 2015 9:38 AM
> To: Swaroop Sridhar <Swaroop.Sridhar at microsoft.com>; llvm-dev <llvm-
> dev at lists.llvm.org>; Sanjoy Das <sanjoy at playingwithpointers.com>
> Cc: Joseph Tremoulet <jotrem at microsoft.com>; Andy Ayers
> <andya at