similar to: [LLVMdev] A question, About how to reading the historical mailling-?

Displaying 20 results from an estimated 10000 matches similar to: "[LLVMdev] A question, About how to reading the historical mailling-?"

2008 Sep 25
0
[LLVMdev] A question, About how to reading the historical mailling-?
Hi anonymous, > I want to know this. Is this possible? Thanks I assume you mean you want to read the archives of the mailinglist? There is an "archives" link on top of each list info page, e.g. http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev (similar for the other mailing list). Hope this helps, Matthijs -------------- next part -------------- A non-text attachment was
2008 Sep 25
1
[LLVMdev] A question, About how to reading the historical mailling-?
Matthijs Kooijman wrote: > I assume you mean you want to read the archives of the mailinglist? There is > an "archives" link on top of each list info page, e.g. > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev On a related note, is there a way to search the archives? They do not seem to be visible to Google, at least Google searches do not find stuff in the archives. For
2010 Feb 22
1
[LLVMdev] Is there any method to fetch all the historical Mailling List archive to my email.
I found no idea, sad.
2010 Feb 22
0
[LLVMdev] Is there any method to fetch all the historical Mailling List archive to my email.
I want to search it in my gmail. And even I want to access it offline. But I don't know how to retrieve all the historical email to my gmail. Thanks:) -- 此致 礼 罗勇刚 Yours sincerely, Yonggang Luo
2008 Jul 30
3
[LLVMdev] llvm-gcc builds on 32 bit linux broken
Hi all, I'm having some trouble building llvm-gcc as of today, with and without bootstrap. The error I get is: /home/kooijman/src/llvm-gcc/obj/./gcc/xgcc -B/home/kooijman/src/llvm-gcc/obj/./gcc/ -B/home/kooijman/src/llvm-gcc/obj/../install/i686-pc-linux-gnu/bin/ -B/home/kooijman/src/llvm-gcc/obj/../install/i686-pc-linux-gnu/lib/ -isystem
2016 Oct 04
8
[Bug 2621] New: ControlMaster started by scp (non-ssh?) doesn't forward agent
https://bugzilla.mindrot.org/show_bug.cgi?id=2621 Bug ID: 2621 Summary: ControlMaster started by scp (non-ssh?) doesn't forward agent Product: Portable OpenSSH Version: 7.3p1 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 Component: Miscellaneous
2009 Jan 22
3
[LLVMdev] Leaving LLVM
Hi all, about a month ago, I've started working on my master's thesis. Since I want to focus on just that work, I've stopped my LLVM work for now. It is unclear whether I will continue my work after graduation, but it seems unlikely. I'll still keep track of LLVM from a personal interest (mostly watching the IRC channel), but I won't have the time to track any mailing lists.
2008 Jun 05
4
[LLVMdev] Adding DenseMap::FindAndConstruct with a default value
Hi All, I've been fiddling around with a DenseMap to store cached copies of some result. In short, I'm doing the following: It = Map.find(Key) if (It != Map.end() && It->second != Unknown) Return It->second; // do_stuff return Map[Key] = Result; However, I this requires two lookups in the hash table, which is not so nice. Currently, there is no way to write this down so
2008 Dec 01
2
[LLVMdev] TargetISelLowering
Hi All, when looking through all the existing targets, I see that each of them defines <Target>ISelLowering.{cpp,h} files. However, they define a class called "<Target>TargetLowering" (though the comments in [at least some of] those files stay the define "<Target>ISelLowering". I suspect that this class was renamed at some time (which makes sense, since I
2008 May 07
4
[LLVMdev] Missing passes
Hi, I was evaluating all transformation passes and noticed a few things. In particular, I found three passes in the documentation that I can't seem to find any code for. Where these removed? Lower GC intrinsics, for GCless code generators (-lowergc) Correlated Expression Elimination (-cee) Lower select instructions to branches (-lowerselect) Additionally, I found the following passes for
2008 May 21
4
[LLVMdev] MultiSource/Applications/lemon slow in JIT
Hi, I've been toying around with the testsuite for a bit, and after recompiling llvm-gcc a bunch of times and fixing a nasty bashism bug, I actually got it to run and pass most tests. When running, I noticed a very long runtime on the lemon test. At first I suspected an infinite loop, but it turned out the test simply needed around 1000 seconds to run. Some investigation turned out that the
2008 May 08
3
[LLVMdev] Vector code
Hi Nicolas (at least, I suspect your signing of your mail with "Anton" was not intentional :-p), > I assume that's the same as the online demo's "Show LLVM C++ API code" > option (http://llvm.org/demo/)? I've tried that with a structure containing > four floating-point components but it also appears to add them individually > using extract/insert. Maybe
2008 Jul 21
0
[LLVMdev] Structs as first class values.
Hi Rich, > I was thinking about my problem and thought that there might be a good > interim solution. I would like not to clutter my front end with stuff > that will go away. How about a pass that runs before code generation > that changes functions returning structs to void functions with the > return pointer first parameter? On this topic, you should look at the
2008 Jul 08
3
[LLVMdev] Inreg firstclass structs
Hi all, I've been discussing parameter attributes and their impact on first-class struct parameters. Duncan and I came to the conclusion that the only attribute that could be applied to structs currently, is the inreg attribute. However, since there is no support anywhere for that currently (transformation passes and backends?), it might be better to disallow the inreg attribute for struct
2008 Jul 10
3
[LLVMdev] (GEP) Index validity
Hi Evan, > I don't think this is right. According to llvm documentation: > > The index types specified for the 'getelementptr' instruction depend on the > pointer type that is being indexed into. Pointer and array types can use a > 32-bit or 64-bit integer type but the value will always be sign extended to > 64-bits. Structure and packed structure types require
2008 Jul 21
3
[LLVMdev] Structs as first class values.
Chris Lattner wrote: > On Jul 20, 2008, at 10:59 AM, Richard Pennington wrote: > I'm sure the implementation will take the same approach, but it won't > necessarily be ABI compatible. I don't know enough to say at this > point... it may end up being ABI compatible or not depending on > implementation details. Hi Chris, I was thinking about my problem and thought
2008 May 13
2
[LLVMdev] [PATCH] Split LoopUnroll pass into mechanism and policy
Hi Dan, please find an updated patch attached (don't forget to run the svn cp command I posted earlier, before applying this patch). I've incorporated all the changes we've discussed. Gr. Matthijs -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: Digital signature URL:
2008 Jul 10
2
[LLVMdev] Including svn version number in --version output
> I suppose to be annoyingly pedantic about it you could require a > network connection for the build, check svn info and svn status and > then set the version string based on whether or not there are local > patches applied to the checkout - but that would probably fall under > neurotic :) Using svnversion (as the original patch does) does exactly this. It outputs the rev
2009 Apr 27
2
[PATCH] Clarify rawlog example
# HG changeset patch # User matthijs at stdin.nl # Date 1240845142 -7200 # Branch HEAD # Node ID 19f4b6167b426c36b7b3b38db4397f2723dc75c2 # Parent c8de2237478fc01ee46e6ec8cda41e8d3cecb68c Clarify rawlog example. diff -r c8de2237478f -r 19f4b6167b42 dovecot-example.conf --- a/dovecot-example.conf Thu Apr 23 12:01:40 2009 -0400 +++ b/dovecot-example.conf Mon Apr 27 17:12:22 2009 +0200 @@ -543,6
2008 Jul 08
4
[LLVMdev] Optimization passes and debug info
Hi all, I've been fiddling around with debug info generated by clang, with the goal of propagating line number info to our custom backend (which is not an llvm backend, but does use llvm IR as its input). I've created a small pass which strips all debug info except for stop points, which are currently the only things we're interested in. Leaving only stop points in actually works