Displaying 20 results from an estimated 2000 matches similar to: "[LLVMdev] LLVM Austin Social"
2012 Aug 29
0
[LLVMdev] LLVM Austin Social
We probably should not spam the list... but I am in :)
Anshu, maybe we can reply directly to you, and at the end you can simply
announce the head count?
Sergei
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum.
> -----Original Message-----
> From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu]
> On Behalf Of Anshuman Dasgupta
> Sent:
2012 Oct 08
1
[LLVMdev] Austin LLVM Social this week
The October Austin LLVM Social will be held this Thursday, October
11.Since some folks from UT are interested in attending, it'll be held
closerto campus this time. The Social will be at the Crown & Anchor Pub
at 2911 SanJacinto Blvd. on October 11 starting at 5:30 pm. Please email
me directly if you plan to attend. Hope to see you there!
-Anshu
---
Qualcomm Innovation Center, Inc.
2012 Jun 26
4
[LLVMdev] [llvm-commits] [PATCH] Refactoring the DFA generator
Hi Anshu,
I don't have commit access. It applies correctly on trunk, I've just
checked it. Could you please commit it?
Ivan
On 26/06/2012 04:44, adasgupt at codeaurora.org wrote:
> Hi Ivan,
>
> Sorry, I should have been more explicit in my last email. The patch looks
> good to me. Please check that it applies on trunk and go ahead and commit.
>
> Thanks
> -Anshu
2012 Jun 25
2
[LLVMdev] [llvm-commits] [PATCH] Refactoring the DFA generator
Hi Anshu,
Just in case you have forgotten this thread ;-). Is this patch ok to
commit or does it not apply to trunk properly ?
I can fix it if that's the problem.
Ivan
On 20/06/2012 19:33, Anshuman Dasgupta wrote:
>
> > Thanks for reviewing this. I added a top comment for AddInsnClass
> and I fixed the violation of column numbers.
>
> Great. Looks good to me.
>
>
2012 Jun 27
0
[LLVMdev] [llvm-commits] [PATCH] Refactoring the DFA generator
Committed in r159281.
-Anshu
On 6/26/2012 3:04 AM, Ivan Llopard wrote:
> Hi Anshu,
>
> I don't have commit access. It applies correctly on trunk, I've just
> checked it. Could you please commit it?
>
> Ivan
>
> On 26/06/2012 04:44, adasgupt at codeaurora.org wrote:
>> Hi Ivan,
>>
>> Sorry, I should have been more explicit in my last email. The
2012 Aug 25
3
[LLVMdev] [llvm-commits] [PATCH] Refactoring the DFA generator
Hi Anshu,
Thanks again for your feedbacks.
On 24/08/2012 17:01, Anshuman Dasgupta wrote:
> Hi Ivan,
>
>> I missed last 2 commits made by Alexey. Following his advices, I
>> updated the patch. It should be ok now.
>> Thanks Anshu!
>>
>> I've recently added more functional units to our Schedule.td and the
>> generation time became painfully long. In
2012 Dec 10
2
[LLVMdev] Possible bug in DFAPacketizer::ReadTable
Hi Anshu,
no, I did not fill a bug report. It is not so easy to make the code fail
noticeably; during Hexagon CodeGen tests it happens silently and tests
pass. I am working on another VLIW backend which uses DFAPacketizer and
compiling llvm with gcc-4.4 makes it segfault, but with gcc-4.7 the bug
gets hidden again (it still happens, but values after DFAStateEntryTable in
memory are such that
2012 Nov 15
3
[LLVMdev] Code Ownership - Hexagon backend
Chris,
I'd like to take code ownership of the Hexagon backend.
Thanks
-Anshu
---
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation
2013 Feb 12
2
[LLVMdev] DFAPacketizer
Hi Jonas,
> It is interesting to find this in the ARM backend, considering your
answer.
The ARM backend doesn't use the DFA packetizer. It's only used by
Hexagon. At this point, there is no plan to address thisin the DFA
packetizer since none of the supported targets needthe functionality.
Thanks
-Anshu
---
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
2012 Jun 28
3
[LLVMdev] [llvm-commits] [PATCH] Refactoring the DFA generator
I missed last 2 commits made by Alexey. Following his advices, I updated
the patch. It should be ok now.
Ivan
On 27/06/2012 21:42, Anshuman Dasgupta wrote:
> Committed in r159281.
>
> -Anshu
>
>
> On 6/26/2012 3:04 AM, Ivan Llopard wrote:
>> Hi Anshu,
>>
>> I don't have commit access. It applies correctly on trunk, I've just
>> checked it.
2012 Dec 11
2
[LLVMdev] Possible bug in DFAPacketizer::ReadTable
Hi Anshu,
I got a testbench which fails (and segfaults) consistently with an
environment (gcc + os) conveniently preserved in a virtual machine. I will
confirm that it is gone there and report.
Thanks for the fix :)
Carlos
2012/12/10 Anshuman Dasgupta <adasgupt at codeaurora.org>
> Carlos,
>
> I committed a fix in r169783. Thanks for catching this.
>
> However, I could
2012 Dec 11
2
[LLVMdev] Possible bug in DFAPacketizer::ReadTable
Great! Can you please check in that test case or better still, a reduced
version of that test.
Thanks
-Anshu
---
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation
On 12/11/2012 5:47 AM, Carlos Sánchez de La Lama wrote:
> Hi again,
>
> I can confirm r169783 fixes the problem. My testbench segfaulted in
> r169782 but works after your
2012 Aug 29
1
[LLVMdev] [llvm-commits] [PATCH] Refactoring the DFA generator
On 28/08/2012 00:21, Anshuman Dasgupta wrote:
> Ivan,
>
> Thanks for working on the patch. It looks good to me except for the
> removal of the Transition class:
>
> > (1) Should I completely remove Transition and create a map structure
> in State (input, state) to replace them?
>
> Yes, please remove the Transition class and create a map structure in
> State
2012 Dec 10
0
[LLVMdev] Possible bug in DFAPacketizer::ReadTable
Carlos,
I committed a fix in r169783. Thanks for catching this.
However, I could not reproduce an invalid read or a segfault even with
fadd.ll. Is there a test case you can check in that reproduces this bug?
Even if the segfault occurs intermittently, that's better than no test
case at all.
Thanks
-Anshu
---
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by
2012 Nov 15
0
[LLVMdev] Code Ownership - Hexagon backend
On Nov 15, 2012, at 11:10 AM, Anshuman Dasgupta <adasgupt at codeaurora.org> wrote:
> Chris,
>
> I'd like to take code ownership of the Hexagon backend.
Sounds fine to me, assuming your other colleagues are ok with that.
-Chris
2015 Dec 02
3
Code owner for Hexagon backend
Hello all,
I’m planning to transition the code ownership of the Hexagon backend to
Krzysztof Parzyszek. Krzysztof has done an excellent job of updating the
Hexagon backend and engaging in community discussions (on the Hexagon
backend and on other topics). He has a number of improvements planned
for the Hexagon compiler and is an obvious choice for owning the Hexagon
target.
If there are no
2012 Jun 26
0
[LLVMdev] [llvm-commits] [PATCH] Refactoring the DFA generator
Hi Ivan,
Sorry, I should have been more explicit in my last email. The patch looks
good to me. Please check that it applies on trunk and go ahead and commit.
Thanks
-Anshu
> Hi Anshu,
>
> Just in case you have forgotten this thread ;-). Is this patch ok to
> commit or does it not apply to trunk properly ?
> I can fix it if that's the problem.
>
> Ivan
>
> On
2013 Mar 14
2
[LLVMdev] Hexagon: removing support for Hexagon-v2 and Hexagon-v3
I wanted to give everybody a heads-up on upcoming commits for the
Hexagon backend. We will be removing support for older versions of the
Hexagon architecture - specifically Hexagon-v2 and Hexagon-v3. These are
no longer being used by compiler users. Matthew Curtis has committed the
first clang patch to remove driver support for these versions. There
will be follow-up patches on the LLVM side
2012 Jun 18
2
[LLVMdev] [llvm-commits] [PATCH] Refactoring the DFA generator
Hi Anshu,
Thanks for reviewing this. I added a top comment for AddInsnClass and I
fixed the violation of column numbers.
On 15/06/2012 21:31, Anshuman Dasgupta wrote:
> Hi Ivan,
>
> The patch looks good to me. I have a couple of minor comments:
>
> +void State::AddInsnClass(unsigned InsnClass,
> Add a top level comment describing the function
>
> + std::map<State*,
2012 Aug 27
0
[LLVMdev] [llvm-commits] [PATCH] Refactoring the DFA generator
Ivan,
Thanks for working on the patch. It looks good to me except for the
removal of the Transition class:
> (1) Should I completely remove Transition and create a map structure
in State (input, state) to replace them?
Yes, please remove the Transition class and create a map structure in
State instead of TransitionSet.
Thanks
-Anshu
On 8/25/2012 6:42 AM, Ivan Llopard wrote:
> Hi